XML is a technical standard defined by W3C (World Wide Web Standardization Association), which can be used to describe GB/T 27926 standardized messages (ie syntax). However, XML has great flexibility in describing specific objects (for example, GB/T 27926 standardized messages), so it is not enough to say that GB/T 27926 standardized messages are defined using XML, we must know how to use XML to define it. This part contains a set of XML design rules, which we call GB/T 27926 XML. Design rules stipulate how standardized messages are described as XML documents that comply with the GB/T 27926 standard. The standardized message is described by the message definition described by UML (Unified Modeling Language) according to the modeling guidelines in GB/T 27926.3. According to the definition of W3C, any XML document that contains an associated description and conforms to the corresponding restrictions in the description can be called a valid XML document (hereinafter referred to as "XML instance" or "instance"). The association description here comes from the original message definition, which is described by UML. This section also describes how to convert UML message (partial) definitions into W3C XML Schema. Through XML Schema, we can use the verification function of XML Schema parser to automatically check whether a given instance conforms to the constraints described in the message definition (or a subset thereof). DTD (Document Type Definition) can also be used to check the partial consistency between an XML instance and the corresponding message definition. But because the verification function provided by DTD has certain limitations, this part does not involve the content of XML DTD. Note that this section only explains how to map message definition graphs to XML. It is useless to explain how to generate a message definition diagram. For information on this aspect, see GB/T 27926.3 Modeling Guidelines.