See more XML articles on AOD.

Powered by
Share this page on
Article provided by Wikipedia

Main article: "Valid characters in XML

Unicode code points in the following ranges are valid in XML 1.0 documents:[10]

XML 1.1[11] extends the set of allowed characters to include all the above, plus the remaining characters in the range U+0001–U+001F. At the same time, however, it restricts the use of C0 and "C1 control characters other than U+0009 (Horizontal Tab), U+000A (Line Feed), U+000D (Carriage Return), and U+0085 (Next Line) by requiring them to be written in escaped form (for example U+0001 must be written as  or its equivalent). In the case of C1 characters, this restriction is a backwards incompatibility; it was introduced to allow common encoding errors to be detected.

The code point "U+0000 (Null) is the only character that is not permitted in any XML 1.0 or 1.1 document.

Encoding detection[edit]

The Unicode character set can be encoded into bytes for storage or transmission in a variety of different ways, called "encodings". Unicode itself defines encodings that cover the entire repertoire; well-known ones include "UTF-8 and "UTF-16.[12] There are many other text encodings that predate Unicode, such as "ASCII and "ISO/IEC 8859; their character repertoires in almost every case are subsets of the Unicode character set.

XML allows the use of any of the Unicode-defined encodings, and any other encodings whose characters also appear in Unicode. XML also provides a mechanism whereby an XML processor can reliably, without any prior knowledge, determine which encoding is being used.[13] Encodings other than UTF-8 and UTF-16 are not necessarily recognized by every XML parser.


XML provides "escape facilities for including characters that are problematic to include directly. For example:

There are five "predefined entities:

All permitted Unicode characters may be represented with a "numeric character reference. Consider the Chinese character "中", whose numeric code in Unicode is hexadecimal 4E2D, or decimal 20,013. A user whose keyboard offers no method for entering this character could still insert it in an XML document encoded either as &#20013; or &#x4e2d;. Similarly, the string "I <3 Jörg" could be encoded for inclusion in an XML document as I &lt;3 J&#xF6;rg.

&#0; is not permitted, however, because the "null character is one of the control characters excluded from XML, even when using a numeric character reference.[15] An alternative encoding mechanism such as "Base64 is needed to represent such characters.


Comments may appear anywhere in a document outside other markup. Comments cannot appear before the XML declaration. Comments begin with <!-- and end with -->. For compatibility with "SGML, the string "--" (double-hyphen) is not allowed inside comments;[16] this means comments cannot be nested. The ampersand has no special significance within comments, so entity and character references are not recognized as such, and there is no way to represent characters outside the character set of the document encoding.

An example of a valid comment: <!--no need to escape <code> & such in comments-->

International use[edit]

XML 1.0 (Fifth Edition) and XML 1.1 support the direct use of almost any "Unicode character in element names, attributes, comments, character data, and processing instructions (other than the ones that have special symbolic meaning in XML itself, such as the less-than sign, "<"). The following is a well-formed XML document including "Chinese, "Armenian and "Cyrillic characters:

<?xml version="1.0" encoding="UTF-8"?>
<俄语 լեզու="ռուսերեն">данные</俄语>

Well-formedness and error-handling[edit]

Well-formed document

The XML specification defines an XML document as a "well-formed text, meaning that it satisfies a list of syntax rules provided in the specification. Some key points in the fairly lengthy list include:

The definition of an XML document excludes texts that contain violations of well-formedness rules; they are simply not XML. An XML processor that encounters such a violation is required to report such errors and to cease normal processing. This policy, occasionally referred to as ""draconian error handling," stands in notable contrast to the behavior of programs that process "HTML, which are designed to produce a reasonable result even in the presence of severe markup errors.[17] XML's policy in this area has been criticized as a violation of "Postel's law ("Be conservative in what you send; be liberal in what you accept").[18]

The XML specification defines a "valid XML document as a "well-formed XML document which also conforms to the rules of a "Document Type Definition (DTD).[19][20]

Schemas and validation[edit]

In addition to being well-formed, an XML document may be valid. This means that it contains a reference to a "Document Type Definition (DTD), and that its elements and attributes are declared in that DTD and follow the grammatical rules for them that the DTD specifies.

XML processors are classified as validating or non-validating depending on whether or not they check XML documents for validity. A processor that discovers a validity error must be able to report it, but may continue normal processing.

A DTD is an example of a "schema or grammar. Since the initial publication of XML 1.0, there has been substantial work in the area of schema languages for XML. Such schema languages typically constrain the set of elements that may be used in a document, which attributes may be applied to them, the order in which they may appear, and the allowable parent/child relationships.

Document Type Definition[edit]

Document Type Definition

The oldest schema language for XML is the "Document Type Definition (DTD), inherited from "SGML.

DTDs have the following benefits:

DTDs have the following limitations:

Two peculiar features that distinguish DTDs from other schema types are the syntactic support for embedding a DTD within XML documents and for defining entities, which are arbitrary fragments of text and/or markup that the XML processor inserts in the DTD itself and in the XML document wherever they are referenced, like character escapes.

DTD technology is still used in many applications because of its ubiquity.

XML Schema[edit]

XML Schema (W3C)

A newer schema language, described by the W3C as the successor of DTDs, is "XML Schema, often referred to by the "initialism for XML Schema instances, XSD (XML Schema Definition). XSDs are far more powerful than DTDs in describing XML languages. They use a rich "datatyping system and allow for more detailed constraints on an XML document's logical structure. XSDs also use an XML-based format, which makes it possible to use ordinary XML tools to help process them.

xs:schema element that defines a schema:

<?xml version="1.0" encoding="ISO-8859-1" ?>
<xs:schema xmlns:xs=""></xs:schema>

RELAX NG[edit]

"RELAX NG (Regular Language for XML Next Generation) was initially specified by "OASIS and is now also an ISO/IEC standard (Part 2: Regular-grammar-based validation of the ISO/IEC standard "DSDL). RELAX NG schemas may be written in either an XML based syntax or a more compact non-XML syntax; the two syntaxes are "isomorphic and "James Clark's conversion tool—Trang—can convert between them without loss of information. RELAX NG has a simpler definition and validation framework than XML Schema, making it easier to use and implement. It also has the ability to use "datatype framework "plug-ins; a RELAX NG schema author, for example, can require values in an XML document to conform to definitions in XML Schema Datatypes.


"Schematron is a language for making "assertions about the presence or absence of patterns in an XML document. It typically uses "XPath expressions. Schematron is now also an ISO/IEC standard (Part 3: Rule-based validation of the ISO/IEC standard DSDL).

DSDL and other schema languages[edit]

"DSDL (Document Schema Definition Languages) is a multi-part ISO/IEC standard (ISO/IEC 19757) that brings together a comprehensive set of small schema languages, each targeted at specific problems. DSDL includes "RELAX NG full and compact syntax, "Schematron assertion language, and languages for defining datatypes, character repertoire constraints, renaming and entity expansion, and namespace-based "routing of document fragments to different validators. DSDL schema languages do not have the vendor support of XML Schemas yet, and are to some extent a grassroots reaction of industrial publishers to the lack of utility of XML Schemas for "publishing.

Some schema languages not only describe the structure of a particular XML format but also offer limited facilities to influence processing of individual XML files that conform to this format. DTDs and XSDs both have this ability; they can for instance provide the "infoset augmentation facility and attribute defaults. RELAX NG and Schematron intentionally do not provide these.

Related specifications[edit]

A cluster of specifications closely related to XML have been developed, starting soon after the initial publication of XML 1.0. It is frequently the case that the term "XML" is used to refer to XML together with one or more of these other technologies that have come to be seen as part of the XML core.

  • "XML namespaces enable the same document to contain XML elements and attributes taken from different vocabularies, without any "naming collisions occurring. Although XML Namespaces are not part of the XML specification itself, virtually all XML software also supports XML Namespaces.
  • "XML Base defines the xml:base attribute, which may be used to set the base for resolution of relative URI references within the scope of a single XML element.
  • "XML Information Set or XML Infoset is an abstract data model for XML documents in terms of information items. The infoset is commonly used in the specifications of XML languages, for convenience in describing constraints on the XML constructs those languages allow.
  • "XSL (Extensible Stylesheet Language) is a family of languages used to transform and render XML documents, split into three parts:
  • "XSLT (XSL Transformations), an XML language for transforming XML documents into other XML documents or other formats such as HTML, plain text, or XSL-FO. XSLT is very tightly coupled with XPath, which it uses to address components of the input XML document, mainly elements and attributes.
  • "XSL-FO (XSL Formatting Objects), an XML language for rendering XML documents, often used to generate PDFs.
  • "XPath (XML Path Language), a non-XML language for addressing the components (elements, attributes, and so on) of an XML document. XPath is widely used in other core-XML specifications and in programming libraries for accessing XML-encoded data.
  • "XQuery (XML Query) is an XML query language strongly rooted in XPath and XML Schema. It provides methods to access, manipulate and return XML, and is mainly conceived as a query language for "XML databases.
  • "XML Signature defines syntax and processing rules for creating "digital signatures on XML content.
  • "XML Encryption defines syntax and processing rules for "encrypting XML content.

Some other specifications conceived as part of the "XML Core" have failed to find wide adoption, including "XInclude, "XLink, and "XPointer.

Programming interfaces[edit]

The design goals of XML include, "It shall be easy to write programs which process XML documents."[5] Despite this, the XML specification contains almost no information about how programmers might go about doing such processing. The "XML Infoset specification provides a vocabulary to refer to the constructs within an XML document, but also does not provide any guidance on how to access this information. A variety of "APIs for accessing XML have been developed and used, and some have been standardized.

Existing APIs for XML processing tend to fall into these categories:

  • Stream-oriented APIs accessible from a programming language, for example "SAX and "StAX.
  • Tree-traversal APIs accessible from a programming language, for example "DOM.
  • "XML data binding, which provides an automated translation between an XML document and programming-language objects.
  • Declarative transformation languages such as "XSLT and "XQuery.

Stream-oriented facilities require less memory and, for certain tasks based on a linear traversal of an XML document, are faster and simpler than other alternatives. Tree-traversal and data-binding APIs typically require the use of much more memory, but are often found more convenient for use by programmers; some include declarative retrieval of document components via the use of XPath expressions.

XSLT is designed for declarative description of XML document transformations, and has been widely implemented both in server-side packages and Web browsers. XQuery overlaps XSLT in its functionality, but is designed more for searching of large "XML databases.

Simple API for XML[edit]

Simple API for XML

"Simple API for XML (SAX) is a "lexical, "event-driven API in which a document is read serially and its contents are reported as "callbacks to various "methods on a "handler object of the user's design. SAX is fast and efficient to implement, but difficult to use for extracting information at random from the XML, since it tends to burden the application author with keeping track of what part of the document is being processed. It is better suited to situations in which certain types of information are always handled the same way, no matter where they occur in the document.

Pull parsing[edit]

Pull parsing[21] treats the document as a series of items read in sequence using the "iterator design pattern. This allows for writing of "recursive descent parsers in which the structure of the code performing the parsing mirrors the structure of the XML being parsed, and intermediate parsed results can be used and accessed as local variables within the methods performing the parsing, or passed down (as method parameters) into lower-level methods, or returned (as method return values) to higher-level methods. Examples of pull parsers include "StAX in the "Java programming language, XMLPullParser in "Smalltalk, XMLReader in "PHP, ElementTree.iterparse in "Python, System.Xml.XmlReader in the ".NET Framework, and the DOM traversal API (NodeIterator and TreeWalker).

A pull parser creates an iterator that sequentially visits the various elements, attributes, and data in an XML document. Code that uses this iterator can test the current item (to tell, for example, whether it is a start-tag or end-tag, or text), and inspect its attributes (local name, "namespace, values of XML attributes, value of text, etc.), and can also move the iterator to the next item. The code can thus extract information from the document as it traverses it. The recursive-descent approach tends to lend itself to keeping data as typed local variables in the code doing the parsing, while SAX, for instance, typically requires a parser to manually maintain intermediate data within a stack of elements that are parent elements of the element being parsed. Pull-parsing code can be more straightforward to understand and maintain than SAX parsing code.

Document Object Model[edit]

Document Object Model

"Document Object Model (DOM) is an API that allows for navigation of the entire document as if it were a tree of "node "objects representing the document's contents. A DOM document can be created by a parser, or can be generated manually by users (with limitations). Data types in DOM nodes are abstract; implementations provide their own programming language-specific "bindings. DOM implementations tend to be "memory intensive, as they generally require the entire document to be loaded into memory and constructed as a tree of objects before access is allowed.

Data binding[edit]

"XML data binding is the binding of XML documents to a hierarchy of custom and strongly typed objects, in contrast to the generic objects created by a DOM parser. This approach simplifies code development, and in many cases allows problems to be identified at compile time rather than run-time. Example data binding systems include the "Java Architecture for XML Binding (JAXB) and XML Serialization in ".NET Framework.[22]

XML as data type[edit]

XML has appeared as a "first-class data type in other languages. The "ECMAScript for XML (E4X) extension to the "ECMAScript/JavaScript language explicitly defines two specific objects (XML and XMLList) for JavaScript, which support XML document nodes and XML node lists as distinct objects and use a dot-notation specifying parent-child relationships.[23] E4X is supported by the "Mozilla 2.5+ browsers (though now deprecated) and Adobe "Actionscript, but has not been adopted more universally. Similar notations are used in Microsoft's "LINQ implementation for Microsoft .NET 3.5 and above, and in "Scala (which uses the Java VM). The open-source xmlsh application, which provides a Linux-like shell with special features for XML manipulation, similarly treats XML as a data type, using the <[ ]> notation.[24] The "Resource Description Framework defines a data type rdf:XMLLiteral to hold wrapped, "canonical XML.[25] Facebook has produced extensions to the "PHP and "JavaScript languages that add XML to the core syntax in a similar fashion to E4X, namely "XHP and "JSX respectively.


XML is an application profile of "SGML (ISO 8879).[26]

The versatility of "SGML for dynamic information display was understood by early digital media publishers in the late 1980s prior to the rise of the Internet.[27][28] By the mid-1990s some practitioners of SGML had gained experience with the then-new "World Wide Web, and believed that SGML offered solutions to some of the problems the Web was likely to face as it grew. "Dan Connolly added SGML to the list of W3C's activities when he joined the staff in 1995; work began in mid-1996 when "Sun Microsystems engineer "Jon Bosak developed a charter and recruited collaborators. Bosak was well connected in the small community of people who had experience both in SGML and the Web.[29]

XML was compiled by a "working group of eleven members,[30] supported by a (roughly) 150-member Interest Group. Technical debate took place on the Interest Group mailing list and issues were resolved by consensus or, when that failed, majority vote of the Working Group. A record of design decisions and their rationales was compiled by "Michael Sperberg-McQueen on December 4, 1997.[31] "James Clark served as Technical Lead of the Working Group, notably contributing the empty-element "<empty />" syntax and the name "XML". Other names that had been put forward for consideration included "MAGMA" (Minimal Architecture for Generalized Markup Applications), "SLIM" (Structured Language for Internet Markup) and "MGML" (Minimal Generalized Markup Language). The co-editors of the specification were originally "Tim Bray and "Michael Sperberg-McQueen. Halfway through the project Bray accepted a consulting engagement with "Netscape, provoking vociferous protests from Microsoft. Bray was temporarily asked to resign the editorship. This led to intense dispute in the Working Group, eventually solved by the appointment of Microsoft's "Jean Paoli as a third co-editor.

The XML Working Group never met face-to-face; the design was accomplished using a combination of email and weekly teleconferences. The major design decisions were reached in a short burst of intense work between August and November 1996,[32] when the first Working Draft of an XML specification was published.[33] Further design work continued through 1997, and XML 1.0 became a "W3C Recommendation on February 10, 1998.


XML is a profile of an ISO standard "SGML, and most of XML comes from SGML unchanged. From SGML comes the separation of logical and physical structures (elements and entities), the availability of grammar-based validation (DTDs), the separation of data and metadata (elements and attributes), mixed content, the separation of processing from representation ("processing instructions), and the default angle-bracket syntax. Removed were the SGML declaration (XML has a fixed delimiter set and adopts "Unicode as the document "character set).

Other sources of technology for XML were the "TEI (Text Encoding Initiative), which defined a profile of SGML for use as a "transfer syntax"; and "HTML, in which elements were synchronous with their resource, document character sets were separate from resource encoding, the xml:lang attribute was invented, and (like "HTTP) metadata accompanied the resource rather than being needed at the declaration of a link. The ERCS(Extended Reference Concrete Syntax) project of the SPREAD (Standardization Project Regarding East Asian Documents) project of the ISO-related China/Japan/Korea Document Processing expert group was the basis of XML 1.0's naming rules; SPREAD also introduced hexadecimal numeric character references and the concept of references to make available all Unicode characters. To support ERCS, XML and HTML better, the SGML standard IS 8879 was revised in 1996 and 1998 with WebSGML Adaptations. The XML header followed that of ISO "HyTime.

Ideas that developed during discussion that are novel in XML included the algorithm for encoding detection and the encoding header, the processing instruction target, the xml:space attribute, and the new close delimiter for empty-element tags. The notion of well-formedness as opposed to validity (which enables parsing without a schema) was first formalized in XML, although it had been implemented successfully in the Electronic Book Technology "Dynatext" software;[34] the software from the University of Waterloo New Oxford English Dictionary Project; the RISP LISP SGML text processor at Uniscope, Tokyo; the US Army Missile Command IADS hypertext system; Mentor Graphics Context; Interleaf and Xerox Publishing System.


There are two current versions of XML. The first (XML 1.0) was initially defined in 1998. It has undergone minor revisions since then, without being given a new version number, and is currently in its fifth edition, as published on November 26, 2008. It is widely implemented and still recommended for general use.

The second (XML 1.1) was initially published on February 4, 2004, the same day as XML 1.0 Third Edition,[35] and is currently in its second edition, as published on August 16, 2006. It contains features (some contentious) that are intended to make XML easier to use in certain cases.[36] The main changes are to enable the use of line-ending characters used on "EBCDIC platforms, and the use of scripts and characters absent from Unicode 3.2. XML 1.1 is not very widely implemented and is recommended for use only by those who need its unique features.[37]

Prior to its fifth edition release, XML 1.0 differed from XML 1.1 in having stricter requirements for characters available for use in element and attribute names and unique identifiers: in the first four editions of XML 1.0 the characters were exclusively enumerated using a specific version of the "Unicode standard (Unicode 2.0 to Unicode 3.2.) The fifth edition substitutes the mechanism of XML 1.1, which is more future-proof but reduces "redundancy. The approach taken in the fifth edition of XML 1.0 and in all editions of XML 1.1 is that only certain characters are forbidden in names, and everything else is allowed to accommodate suitable name characters in future Unicode versions. In the fifth edition, XML names may contain characters in the "Balinese, "Cham, or "Phoenician scripts among many others added to Unicode since Unicode 3.2.[36]

Almost any Unicode code point can be used in the character data and attribute values of an XML 1.0 or 1.1 document, even if the character corresponding to the code point is not defined in the current version of Unicode. In character data and attribute values, XML 1.1 allows the use of more "control characters than XML 1.0, but, for "robustness", most of the control characters introduced in XML 1.1 must be expressed as numeric character references (and #x7F through #x9F, which had been allowed in XML 1.0, are in XML 1.1 even required to be expressed as numeric character references[38]). Among the supported control characters in XML 1.1 are two line break codes that must be treated as whitespace. Whitespace characters are the only control codes that can be written directly.

There has been discussion of an XML 2.0, although no organization has announced plans for work on such a project. XML-SW (SW for "skunkworks), written by one of the original developers of XML,[39] contains some proposals for what an XML 2.0 might look like: elimination of DTDs from syntax, integration of "namespaces, "XML Base and "XML Information Set into the base standard.

The World Wide Web Consortium also has an XML Binary Characterization Working Group doing preliminary research into use cases and properties for a binary encoding of XML Information Set. The working group is not chartered to produce any official standards. Since XML is by definition text-based, ITU-T and ISO are using the name "Fast Infoset for their own binary infoset to avoid confusion (see ITU-T Rec. X.891 and ISO/IEC 24824-1).


XML and its extensions have regularly been criticized for verbosity and complexity.[40] Mapping the basic tree model of XML to "type systems of programming languages or databases can be difficult, especially when XML is used for exchanging highly structured data between applications, which was not its primary design goal. Other criticisms attempt to refute the claim that XML is a "self-describing language[41] (though the XML specification itself makes no such claim). "JSON, "YAML, and "S-Expressions are frequently proposed as alternatives (see "Comparison of data serialization formats);[42] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content.


3dm is or was a tool for performing three-way merging and differencing of XML files. Unlike line-based tools, such as "diff and "diff3, 3dm is aware of the tree structure of the input documents. 3dm detects and merges subtree update, insert, delete, and move operations. The tool is not reliant on edit histories; the only input needed are the XML files.[43][44]

See also[edit]


  1. ^ i.e., embedded quote characters would be a problem
  2. ^ A common example of this is "CSS class or identifier names.


  1. ^ "XML Media Types, RFC 7303". Internet Engineering Task Force. July 2014. 
  2. ^ "XML 1.0 Specification". World Wide Web Consortium. Retrieved 22 August 2010. 
  3. ^ "XML and Semantic Web W3C Standards Timeline" (PDF). Retrieved 14 August 2016. 
  5. ^ a b "XML 1.0 Origin and Goals". Retrieved 14 August 2016. 
  6. ^ Fennell, Philip (June 2013). "Extremes of XML". XML London 2013: 80–86. "doi:10.14337/XMLLondon13.Fennell01. "ISBN "978-0-9926471-0-0. 
  7. ^ "XML Applications and Initiatives". 
  8. ^ " "PLIST files"". The Apple Examiner. 
  9. ^ M. Murata; D. Kohn & C. Lilley (24 September 2009). "Internet Drafts: XML Media Types". Internet Engineering Task Force. Retrieved 29 February 2012. 
  10. ^ "Extensible Markup Language (XML) 1.0 (Fifth Edition)". World Wide Web Consortium. 2008-11-26. Retrieved 23 November 2012. 
  11. ^ "Extensible Markup Language (XML) 1.1 (Second Edition)". World Wide Web Consortium. Retrieved 22 August 2010. 
  12. ^ "Characters vs. Bytes". 
  13. ^ "Autodetection of Character Encodings". 
  14. ^ It is allowed, but not recommended, to use "<" in XML entity values: Extensible Markup Language (XML) 1.0 (Fifth Edition): EntityValue definition
  15. ^ "W3C I18N FAQ: HTML, XHTML, XML and Control Codes". 
  16. ^ "Extensible Markup Language (XML)". W3C.  Section "Comments"
  17. ^ Pilgrim, Mark (2004). "The history of draconian error handling in XML". Archived from the original on 2011-07-26. Retrieved 18 July 2013. 
  18. ^ "There are no exceptions to Postel's Law [dive into mark]". Archived from the original on 2011-05-14. Retrieved 22 April 2013. 
  19. ^ "XML Notepad". 
  20. ^ "XML Notepad 2007". 
  21. ^ Push, Pull, Next! by Bob DuCharme, at
  22. ^ "XML Serialization in the .NET Framework". Retrieved 31 July 2009. 
  23. ^ "Processing XML with E4X". Mozilla Developer Center. Mozilla Foundation. 
  24. ^ "XML Shell: Core Syntax". xmlsh. 2010-05-13. Retrieved 22 August 2010. 
  25. ^ "Resource Description Framework (RDF): Concepts and Abstract Syntax". Retrieved 22 August 2010. 
  26. ^ "ISO/IEC 19757-3". "ISO/"IEC. 1 June 2006: vi. 
  27. ^ Bray, Tim (February 2005). "A conversation with Tim Bray: Searching for ways to tame the world's vast stores of information". Association for Computing Machinery's "Queue site". Retrieved 16 April 2006. 
  28. ^ edited by Sueann Ambron; Kristina Hooper & foreword by John Sculley. (1988). "Publishers, multimedia, and interactivity". Interactive multimedia. Cobb Group. "ISBN "1-55615-124-1. 
  29. ^ Eliot Kimber (2006). "XML is 10". 
  30. ^ The working group was originally called the "Editorial Review Board." The original members and seven who were added before the first edition was complete, are listed at the end of the first edition of the XML Recommendation, at
  31. ^ "Reports From the W3C SGML ERB to the SGML WG And from the W3C XML ERB to the XML SIG". Retrieved 31 July 2009. 
  32. ^ Jon Bosak: The Birth of XML
  33. ^ "Extensible Markup Language (XML)". 1996-11-14. Retrieved 31 July 2009. 
  34. ^ Jon Bosak; Sun Microsystems (2006-12-07). "Closing Keynote, XML 2006". Archived from the original on 2007-07-11. Retrieved 31 July 2009. 
  35. ^ "Extensible Markup Language (XML) 1.0 (Third Edition)". Retrieved 22 August 2010. 
  36. ^ a b "Extensible Markup Language (XML) 1.1 (Second Edition) , Rationale and list of changes for XML 1.1". W3C. Retrieved 20 January 2012. 
  37. ^ Harold, Elliotte Rusty (2004). Effective XML. Addison-Wesley. pp. 10–19. "ISBN "0-321-15040-6. 
  38. ^ "Extensible Markup Language (XML) 1.1 (Second Edition)". Retrieved 22 August 2010. 
  39. ^ Tim Bray: Extensible Markup Language, SW (XML-SW). 2002-02-10
  40. ^ Jeff Atwood (2009): XML: The Angle Bracket Tax
  41. ^ "The Myth of Self-Describing XML" (PDF). September 2003. 
  42. ^ Stackoverflow: What usable alternatives to XML syntax do you know?
  43. ^ Tancred Lindholm (2004). "A Three-way Merge for XML Documents". ACM Symposium on Document Engineering. [1]
  44. ^ - The homepage of 3dm

Further reading[edit]

External links[edit]

) )