GB/T 27926.4-2011 Financial services—Universal financial industry message scheme—Part 4:XML design rules
GB/T 27926.4-2011 Financial services—Universal financial industry message scheme—Part 4:XML design rules
Basic Information
Scope
XML is a technical standard defined by the W3C (World Wide Web Consortium) that can be used to describe GB/T 27926 standardized messages (i.e., the grammar). However, XML has great flexibility in describing specific objects (for example, GB/T 27926 standardized messages), so it's not enough to simply state that GB/T 27926 standardized messages are defined using XML. We need to know how to use XML to define them.
This section includes a set of XML design rules, which we call GB/T 27926 XML. The design rules specify how to describe standardized messages as XML documents that comply with the GB/T 27926 standard. These standardized messages are described according to the messaging definitions described in GB/T 27926.3 using the modeling guidelines of UML1 (Unified Modeling Language).
According to the W3C definition, any XML document that contains associated descriptions and complies with the corresponding restrictions in the description can be called a valid XML document (hereinafter referred to as an "XML instance" or "instance"). Here, the associated descriptions come from the original message definition and are described by UML.
This section also describes how to convert UML message (partial) definitions into W3C XML Schemas. Using XML Schemas, we can use the validation function of XML Schema parsers to automatically check whether a given instance complies with the constraints (or a subset thereof) described in the message definition.
DTD (Document Type Definition) can also be used to check the partial consistency of XML instances with the corresponding message definitions. However, since the validation function provided by DTD has certain limitations, this section does not cover the content of XML DTD.
Note that this section only explains how to map message definition diagrams to XML. It does not explain how to generate a message definition diagram. For information on this aspect, see the GB/T 27926.3 modeling guidelines.