ECLASS does not use special characters such as <;> or <">, which are interpreted by some systems as a control or separation character. The unit 0173- 1#07-AAA683#002 "angular_second" however, was incorrectly abbreviated as the quotation mark <"> (U+0022). Therefore interpretation of the unit table might result in difficulties at this point.
- The error was corrected in ECLASS 8.0, where the quotation mark (U+0022) was replaced by the double prime (U+2033).
In ECLASS 7.0 and 7.1 values were not included in value lists, but only in templates. Therefore, not only values that are used in the BASIC version were included in the export of the file eClass7_0_PR_en.csv (also in German and also in 7.1: eClass7_1_PR_de.csv), but all values used in all of ECLASS, including the ADVANCED version. Values that cannot be found in the files eClass7_0_PR_VA.csv or eClass7_0_suggested_values.csv are only used in the ADVANCED version.
- In ECLASS 8.0, values are part of value lists again. Therefore, only values that are used in the BASIC version, are part of the BASIC version.
Please ignore those values in ECLASS 7.0 and 7.1 that are not used in any other table.
The following notes are copied from the read me file, but do not include errors.
- Note 1 on valency: The attribute "valency" was removed as ECLASS does not restrict, whether exactly one value or multiple values may be valid. This is defined by the users in their data exchange. For systems that require an indication of the valency, ECLASS recommends to interpret all properties as multivalent, except of BOOLEAN properties (= univalent). (univalent= exactly one value is valid; multivalent=an undefined number of values can be valid).
- Note 2 on data types: ECLASS has introduced with release 7.0 many new data types that might not be interpretable by every system. In this case, ECLASS recommends to distinguish between at least BOOLEAN, REAL, INTEGER (including count, measure and currency) and STRING properties. ECLASS sees STRING as a suitable substitute for all other data types that are not interpretable by a system (STRING_TRANSLATABLE, URL, DATE, TIME, TIMESTAMP, RATIONAL, RATIONAL_MEASURE). Until release 6.0 there was a different valid format (attribute "format" with X..10, NR1..1, NR2..2.2, V, etc.). In releases 6.1 and 6.2 the new form of describing the format (data type plus any further data-type-specific information) was already published additionally to the old format. Starting from ECLASS 7.0 exclusively the new form is published, as the new data types are no longer compatible with the old format.
- Note 3 on format specifications: Before 7.0 the indication of both digits before and after comma for REAL and INTEGER properties, as well as the indication of the number of characters of STRING properties had been mandatory. Starting from ECLASS release 7.0, these attributes are no longer mandatory, i.e. the fields must not be filled.
- Note 1: Prior to 7.0 ECLASS interpreted its value lists as open, i.e. as suggestions that were never intended to be comprehensive. As the ISO defines value lists as restrictive and exclusive, i.e. only those values of a value list are valid for a property and no others ECLASS had to change its structure to be ISO-compliant. Therefore ECLASS distinguishes now between value lists (in the ISO-sense, see 3.1.5) and proposal lists (proposed "open" lists that are not exclusive nor exhaustive in the context of the class, see 3.1.6).
- Data Types
- Note 1 on data types: ECLASS has introduced with release 7.0 many new data types that might not be interpretable by every system. In this case, ECLASS recommends to distinguish between at least BOOLEAN, REAL, INTEGER (including count, measure and currency) and STRING properties. ECLASS sees STRING as a suitable substitute for all other data types that are not interpretable by a system (STRING_TRANSLATABLE, URL, DATE, TIME, TIMESTAMP, RATIONAL, RATIONAL_MEASURE).
Note: please note that this version may contain properties of type "Boolean" which are multivalent.