Concise Logically Organized Data (CLOD) is a human readable, machine processable data syntax set in a clear text stream. Unlike some other common data syntaxes that have their roots in programming languages, processing or storage paradigms, CLOD attempts to only describe the data, ignoring how it might be consumed, processed or transmitted. This disconnection of the data from the software takes its roots from the ASC X12 and UN/EDIFACT syntaxes which have been in use for several decades for data exchange. Unlike those, however, CLOD does not try to define beforehand what data can be exchanged or how it is to be transmitted. CLOD leaves these decisions to the end user.
A CLOD document follows three layers of rules and definitions in a bootstrapping manner. They are Base, Type and Schema.
All CLOD documents will adhere to some basic rules about its structure, character encoding and so forth. Not following any of these will cause the CLOD document to be considered invalid by all validity checking and parsing tools.
All CLOD documents will be of a specified Type. The Type defines the more advanced structure and rules used to build and read a CLOD document for the further processing of the data it contains. All Types must be approved by and registered with Omega Tower Design Partners. A CLOD document will be considered invalid by all validity checking and parsing tools if the data in or structure of the CLOD document does not conform to all the requirements and specifications of its Type. The use of a non-registered Type will also cause the CLOD document to be considered invalid by all validity checking and parsing tools.
All data being described by a CLOD document will adhere to a Schema (explicitly or implicitly). The Schema defines the data types and rules used to read and interpret the data contained in a CLOD document. If a Schema file is identified, then a CLOD document will be considered invalid by all validity checking and parsing tools if the data in the CLOD document does not conform to all the requirements and specifications of that Schema file.