In this tutorial, we introduce the XML data exchange format and discuss the structure of an XML document, and the syntax rules for .XML XML documents should be readable and reasonably clear. This document is a W3C recommendation. This fifth edition is not a new version of XML. For the convenience of readers, it includes changes dictated by accumulated errata (available at www.w3.org/XML/xml-V10-4e-errata) from the fourth edition of XML 1.0 dated August 16, 2006. In particular, erratum [E09] alleviates restrictions on element and attribute names, providing the greatest benefit to the end user in XML 1.0 that can currently only be obtained using XML 1.1. As a result, many possible documents that were not well formed according to previous editions of this specification are now well formed, and previously invalid documents that use newly allowed name characters in, for example, ID attributes are now valid. Select this method if an item can be identified by a unique ID. This is very useful for aligning XML documents or improving the accuracy of translation reuse. This document is also available in the following non-normative formats: XML and XHTML with color-coded revision indicators. References typically allow you to add or include additional text or markup in an XML document.
References always begin with the symbol „&”, which is a reserved character, and end with the symbol „;”. XML has two types of references: [definition: violation of the rules of this specification; The results are not defined. Unless otherwise stated, failure to comply with any provision of this specification that is REQUIRED, SHALL NOT and SHALL NOT be specified with any of the keywords is an error. Compliant software CAN detect, report and potentially recover a bug.] Attributes with tokenized types where the attribute appears in the document with a value that results in normalization to a value other than that which would have been generated without the declaration, or If the document contains an XML declaration, this must be the first statement in the XML document. Examples of such elements would be bold or underlined tags. This is often used when translating paragraph-based text segments into XML documents. To be precise, this document is well trained. XML documents are described as well-formed and valid (we define these terms in a minute). This XML document is not legal at all: One important point: the XML 1.0 specification makes it clear that if an XML parser finds an XML document that violates the rules, it must throw and stop an exception.
The parser should not guess what the document structure should look like. This specification avoids recreating the HTML world where many ugly documents are still rendered by the average browser. The XML prologue is optional. If it exists, it should appear first in the document. The following diagram illustrates the syntax rules for writing different types of markup and text in an XML document. Note that non-validating processors are not required to read and process entity declarations that occur in parameter entities or in the outer subset. For such documents, the rule that an entity must be declared is a well-formed constraint only if standalone=`yes`. The first element of your XML document must contain the entire document. This first element is called a document element or root element. If the document contains multiple document elements, the XML parser throws an exception.
This XML document is completely legal: although the VersionNum production matches any version number of the form „1.x”, XML 1.0 documents must NOT specify a version number other than „1.0”. XML documents that conform to the above syntax rules are called „well-formed” XML documents. In the following example, you want to parse the contents of the column element as localizable only if the translation set attribute with the value „yes” exists. Use XPath rules to specify the condition under which @translate is an attribute in the selected element column and the required value is „yes” and uses = sign. XML documents must contain a root element that is greater than all other elements: To simplify application tasks, the XML processor MUST behave as if it normalizes all line breaks in external parsed entities (including the document entity) when typed before d#xD #xA be parsed by both the two-digit sequence and all #xD that are not followed by #xA. translated into one #xA characters. When an XML 1.0 processor encounters a document that specifies a 1.x version number other than „1.0”, it is treated as a 1.0 document. This means that an XML 1.0 processor accepts 1.x documents as long as they do not use non-1.0 features. Note that it is possible to create a well-formed document that contains a doctypedecl that does not reference an outer subset or contains an internal subset. When an XML document is inserted into Alchemy CATALYST, markup and content are processed, but it is not displayed in the workspace unless an element/attribute is selected for localization.