no way to compare when less than two revisions

Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+====== General Specifications ======
+===== Version validity and downward compatibility =====
+This is the current version 6.10.1. Minor changes ensuring downward compatibility are indicated in the third position of the release number. For example, the release number is changed from 6.5.1 to 6.5.2 when a new data field is entered into a table without changing existing fields. Changes to the format which require minor changes to the various software packages are indicated in the second position of the release number, e.g. 6.5.5. is changed to 6.6.0. A new structure and format definition (e.g. XML) will be defined in release 7.0.0.
+===== Delimiters and data set length =====
+The character set used in the text files described below is ISO 8859-x (value x is defined in the Head.Dat file).
+(Also see "[[http://de.wikipedia.org/wiki/ISO_8859-1]]“)
+The various sets are separated by the characters CR (ASCII 13) abd LF (ASCII 10). In the interest of better downward compatibility, a fixed set length has not been defined. In a new version of the file format, newly defined data fields are simply attached to the existing structure. Software products not yet matched to the current file format can therefore import the new file format nonetheless.
+The sets themselves consist of fields with a fixed length without delimiter.
+===== Field specifications =====
+**Text fields** (type T) are saved in the data sets in left-aligned form, followed by a BLANK (ASCII 32).
+**Numeric values** (type 9 or B) are right-aligned with leading zeros without decimal delimiter. BLANK is interpreted as "0". (Exceptions: price fields in LensPrice.Dat and OptionsPrice.Dat, where a blank for an EK price field (EK = purchase price) is interpreted as "price on request" and indicates for a VK (= selling price) field that no selling price has been recommended and must be calculated by the eyecare professionals themselves).
+**Date fields** (type D) are displayed in the year, month and day format (4 digits, 2 digits, 2 digits). Optional fields can be filled with a BLANK. (Format: YYYYMMDD)
+**Boolean fields** are defined as 0=No and 1=Yes. BLANK is interpreted as "0". Other definitions are determined as comments in the table structure.
+In files with a primary key, the fields making up this key are marked with an asterisk (*). A primary key must not occur several times in one file. Furthermore, it is required that the sets are arranged according to the primary key.
+===== Product definition in the GPL standard, orderability =====
+A product is something that is identified by a defined and clear manufacturer's order code. A difference is made between base lens products and extras products (coatings). It is assumed that products defined in this way, supplemented with diameters and dioptric powers, enable orders to be transferred to the manufacturer's order system.
+===== Consistency requirements =====
+The primary key feature must be observed. Several sets with the same primary key must not occur in any file.
+All base lens codes appearing in LensPrice.Dat, Combination.Dat, LensRange.Dat, LensGeo.Dat, Information.Dat, OrderOptions.Dat, ProductGroup.dat, CodeSubstitution.Dat and OeCodes.Dat must have been defined in the LensType.Dat file.
+All extras codes appearing in OptionsColor.Dat, OptionsPrice.Dat, Combination.Dat, LensRange.Dat, Information.Dat, OrderOptions.Dat, ProductGroup.Dat, CodeSubstitution.Dat  and OeCodes.Dat must have been defined in the Options.Dat file.
+All extras indices used in the OptionsPrice.Dat file must have been defined in the LensType.Dat file.
+All delivery range indices used in the LensPrice.Dat file must have been defined in the LensRange.Dat file.
+The product designations specified in the LensType.Dat, Options.Dat and OptionsColor.Dat files must be unambiguous in each file, although they are not contained in the primary key.