<element>01</element> <element>1515151515 </element> . . . </segment> C6.5.3.2. XML is self-validating. Each DLMS XML transaction has an XSD (XML Schema Definition) file. The XSD defines the data types (e.g., string, numeric, binary) and detailed constraints (e.g., size, optional/required, enumeration value (lookup table), and format). The process of checking to see if an XML transaction conforms to a schema is called validation, which is separate from XML’s core concept of being syntactically well formed. All XML transactions must be well formed or they cannot be parsed. The schema ensures the transaction conforms to the process rules. Validation of an instance transaction against a schema can be regarded as a conceptually separate operation from XML parsing. In practice, the schema validation is integrated within the XML parser.
<element>01</element> <element>1515151515 </element> . . . </segment> C6.5.3.2. XML is self-validating. Each DLMS XML transaction has an XSD (XML Schema Definition) file. The XSD defines the data types (e.g., string, numeric, binary) and detailed constraints (e.g., size, optional/required, enumeration value (lookup table), and format). The process of checking to see if an XML transaction conforms to a schema is called validation, which is separate from XML’s core concept of being syntactically well formed. All XML transactions must be well formed or they cannot be parsed. The schema ensures the transaction conforms to the process rules. Validation of an instance transaction against a schema can be regarded as a conceptually separate operation from XML parsing. In practice, the schema validation is integrated within the XML parser.
0106-V1c6.docx