When a document contains elements generated by more than one author, XML namespaces prevent collisions. For example, order information from the Accounting and Fulfillment departments can be distinguished by "acct:order" and "ful:order," respectively.
To avoid having namespace prefixes for every element and attribute name , the XML namespace syntax allows authors to set the default namespace with the reserved "xmlns" attribute.
XPath enables developers to address particular element nodes within a document tree, while XPointer enables authors to address content within and across element nodes.
When developers have two different DTDs or schemas that govern the same logical content, they can easily transform documents between the two formats using XSLT.
Developers can use XSLT to transform XML content directly into tag-oriented display formats such as HTML,WML, and VoiceXML.
XSL allows authors to create paginated output from XML content for one or more audiences.
XLink allows authors to link one XML document to another XML document or even to many other XML documents.
XML Schema is superior to DTDs for data-oriented applications because it uses XML syntax, enforces precise datatype restrictions, and has more flexibility for reuse and extension.
Technical standards like Infoset and XML Fragment Interchange improve the processing of XML documents and reduce ambiguities that could lead to misinterpretations.
Infrastructure standards like XHTML and XML Signatures ensure that common operations on XML documents remain uniform across applications.
