Subscribe: XML - Revision history
http://en.wikipedia.org/w/index.php?title=XML&curid=34138&action=history&feed=rss
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
based  data  document  internet  iso iec  language  markup language  markup  ref  revision  standard  web  xml  {{cite web 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: XML - Revision history

XML - Revision history



Revision history for this page on the wiki



Last Build Date: Wed, 20 Sep 2017 11:26:20 GMT

 



TAnthony: Correct unknown or deprecated {{Reflist}} parameters and genfixes using AWB

Wed, 20 Sep 2017 03:35:34 GMT

Correct unknown or deprecated {{Reflist}} parameters and genfixes using AWB ← Previous revision Revision as of 03:35, 20 September 2017 Line 41: Line 41:       ==Applications of XML==   ==Applications of XML== − The essence of why extensible markup languages are necessary is explained at ''[[Markup language]]'' (for example, see ''[[Markup language#XML|Markup language § XML]]'') and at ''[[Standard Generalized Markup Language]]''. + The essence of why extensible markup languages are necessary is explained at ''[[Markup language]]'' (for example, see ''[[Markup language#XML|Markup language § XML]]'') and at ''[[Standard Generalized Markup Language]]''.     − Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}} + Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}}       XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] [[:RFC:3023]], now superseded by [[:RFC:7303]], gave rules for the construction of [[Internet media type|Internet Media Types]] for use when sending XML. It also defines the media types application/xml and text/xml, which say only that the data is in XML, and nothing about its [[semantics]]. The use of text/xml has been criticized{{efn-lr|Murata, Kohn & Lilley (2009), in their draft RFC to update RFC 3023 (2001) that introduced text/xml, and advocated its formal deprecation. However [[:RFC:7203]] (2014) did not do this.}} as a potential source of encoding problems and it has been suggested that it should be deprecated.   XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] [[:RFC:3023]], now superseded by [[:RFC:7303[...]



Andy Dingley: rv taxonomic folksonomy aspirations, sourced to W3Schools Undid revision 797075197 by 213.179.208.70 (talk)

Tue, 19 Sep 2017 14:36:17 GMT

rv taxonomic folksonomy aspirations, sourced to W3Schools Undid revision 797075197 by 213.179.208.70 (talk) ← Previous revision Revision as of 14:36, 19 September 2017 Line 34: Line 34:   }} }}   }} }}     − In [[computing]], '''Extensible Markup Language''' ('''XML''') is a [[markup language]] that defines a set of rules for encoding [[electronic document|document]]s in a [[file format|format]] that is both [[Human-readable medium|human-readable]] and [[Machine-readable data|machine-readable]] through use of [[tag (metadata)|tags]] that can be created and defined by users. Much like [[natural language]] is [[wikt:extensible#Adjective|extensible]] (that is, can grow) when speakers create new words and agree on what they mean, XML is a markup language that can grow when users create new elements and agree on what they mean. This makes XML able to capture intent in a way much broader than a nonextensible markup language such as [[HTML]]. For example, XML can mark up machine-readably that apples and bananas are types of fruit, which is semantically deeper than the purpose of HTML.[https://www.w3schools.com/xml/xml_whatis.asp XML is Extensible] However, HTML is useful for display of content; often HTML is used to display XML content after transformation with [[XSL]].[https://www.w3schools.com/xml/xml_whatis.asp The Difference Between XML and HTML] + In [[computing]], '''Extensible Markup Language''' ('''XML''') is a [[markup language]] that defines a set of rules for encoding [[electronic document|document]]s in a [[file format|format]] that is both [[Human-readable medium|human-readable]] and [[Machine-readable data|machine-readable]]. The [[World Wide Web Consortium|W3C]]'s XML 1.0 Specification{{cite web |url=http://www.w3.org/TR/REC-xml |title=XML 1.0 Specification |publisher=World Wide Web Consortium |accessdate=22 August 2010}} and several other related specifications{{cite web |url=http://www.dblab.ntua.gr/~bikakis/XML%20and%20Semantic%20Web%20W3C%20Standards%20Timeline-History.pdf |format=PDF |title=XML and Semantic Web W3C Standards Timeline |accessdate=14 August 2016}}—all of them free [[open standard]]s—define XML.{{cite web |title=W3C DOCUMENT LICENSE |url=http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231}} −   − The [[World Wide Web Consortium|W3C]]'s XML 1.0 Specification{{cite web |url=http://www.w3.org/TR/REC-xml |title=XML 1.0 Specification |publisher=World Wide Web Consortium |accessdate=22 August 2010}} and several other related specifications{{cite web |url=http://www.dblab.ntua.gr/~bikakis/XML%20and%20Semantic%20Web%20W3C%20Standards%20Timeline-History.pdf |format=PDF |title=XML and Semantic Web W3C Standards Timeline |accessdate=14 August 2016}}—all of them free [[open standard]]s—define XML.{{cite web |title=W3C DOCUMENT LICENSE |url=http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231}}         The design goals of XML emphasize simplicity, generality, and usability across the [[Internet]].{{cite web |title=XML 1.0 Origin and Goals |url=http://www.w3.org/TR/REC-xml/#sec-origin-goals |accessdate=14 August 2016}} It is a textual data format with strong support via [[Unicode]] for different [[Language|human languages]]. Although the design of XML focuses on documents, the language is widely used for the representation of arbitrary [[data structure]]s{{cite journal |title=Extremes of XML |first=Philip |last=Fennell |date=June 2013 |journal=XML London 2013 |doi=10.14337/XMLLondon13.Fennell01 |url=http://xmllondon.com/2013/presentations/fennell/ |pages=80–86 |isbn=978-0-9926471-0-0}} such as those used in [[web service]]s. [...]



Andy Dingley: Yes, it's already in the source given. Undid revision 801406743 by Oiyarbepsy (talk)

Tue, 19 Sep 2017 14:35:08 GMT

Yes, it's already in the source given. Undid revision 801406743 by Oiyarbepsy (talk) ← Previous revision Revision as of 14:35, 19 September 2017 Line 45: Line 45:   The essence of why extensible markup languages are necessary is explained at ''[[Markup language]]'' (for example, see ''[[Markup language#XML|Markup language § XML]]'') and at ''[[Standard Generalized Markup Language]]''.   The essence of why extensible markup languages are necessary is explained at ''[[Markup language]]'' (for example, see ''[[Markup language#XML|Markup language § XML]]'') and at ''[[Standard Generalized Markup Language]]''.     − Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}} + Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}}     − XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] RFC 7303 gives rules for the construction of [[Internet media type|Internet Media Types]] for use when sending XML. It also defines the media types ''application/xml'' and ''text/xml'', which say only that the data is in XML, and nothing about its [[semantics]]. The use of ''text/xml'' has been criticized{{by whom|date=July 2016}} as a potential source of encoding problems and it has been suggested that it should be deprecated.{{Failed verification|date=September 2017}} + XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] [[:RFC:3023]], now superseded by [[:RFC:7303]], gave rules for the construction of [[Internet media type|Internet Media Types]] for use when sending XML. It also defines the media types application/xml and text/xml, which say only that the data is in XML, and nothing about its [[semantics]]. The use of [...]



Oiyarbepsy: /* Applications of XML */ The given source does not say that XML should be deprecated

Tue, 19 Sep 2017 13:45:17 GMT

‎Applications of XML: The given source does not say that XML should be deprecated ← Previous revision Revision as of 13:45, 19 September 2017 Line 47: Line 47:   Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}}   Hundreds of document formats using XML syntax have been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], [[SVG]], and [[XHTML]]. XML-based formats have become the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]{{Citation needed|reason= No source for the information.|date=May 2017}}. XML has also provided the base language for [[communication protocol]]s such as [[Extensible Messaging and Presence Protocol|XMPP]]. Applications for the [[Microsoft]] [[.NET Framework]] use XML files for configuration. Apple has an implementation of a registry based on XML.{{cite web|url= http://www.appleexaminer.com/MacsAndOS/Analysis/PLIST/PLIST.html|title= appleexaminer.com: "PLIST files"|publisher= The Apple Examiner}}     − XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] RFC 7303 gives rules for the construction of [[Internet media type|Internet Media Types]] for use when sending XML. It also defines the media types ''application/xml'' and ''text/xml'', which say only that the data is in XML, and nothing about its [[semantics]]. The use of ''text/xml'' has been criticized{{by whom|date=July 2016}} as a potential source of encoding problems and it has been suggested that it should be deprecated. + XML has come into common use for the interchange of data over the Internet. [[History of the Internet#Internet Engineering Task Force|IETF]] RFC 7303 gives rules for the construction of [[Internet media type|Internet Media Types]] for use when sending XML. It also defines the media types ''application/xml'' and ''text/xml'', which say only that the data is in XML, and nothing about its [[semantics]]. The use of ''text/xml'' has been criticized{{by whom|date=July 2016}} as a potential source of encoding problems and it has been suggested that it should be deprecated.{{Failed verification|date=September 2017}}       RFC 7303 also recommends that XML-based languages be given media types ending in ''+xml''; for example ''image/svg+xml'' for [[SVG]].   RFC 7303 also recommends that XML-based languages be given media types ending in ''+xml''; for example ''image/svg+xml'' for [[SVG]]. [...]



Mhkay: /* Programming interfaces */ Add "syntax extensions" as another category

Sat, 16 Sep 2017 18:51:23 GMT

‎Programming interfaces: Add "syntax extensions" as another category ← Previous revision Revision as of 18:51, 16 September 2017 Line 218: Line 218:   * [[XML data binding]], which provides an automated translation between an XML document and programming-language objects.   * [[XML data binding]], which provides an automated translation between an XML document and programming-language objects.   * Declarative transformation languages such as [[XSLT]] and [[XQuery]].   * Declarative transformation languages such as [[XSLT]] and [[XQuery]].   + * Syntax extensions to general-purpose programming languages, for example [[LINQ]] and [[Scala (programming language)|Scala]].       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.   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. [...]



Mhkay: /* Data binding */ Suitable for fixed stable schemas (only)

Sat, 16 Sep 2017 18:47:13 GMT

‎Data binding: Suitable for fixed stable schemas (only) ← Previous revision Revision as of 18:47, 16 September 2017 Line 237: Line 237:       ===Data binding===   ===Data binding=== − [[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), XML Serialization in [[.NET Framework]].{{cite web|url=http://msdn.microsoft.com/en-us/library/ms950721.aspx|title=XML Serialization in the .NET Framework|publisher=Msdn.microsoft.com|accessdate=31 July 2009}} and XML serialization in [[gSOAP]]. + [[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. It is suitable for applications where the document structure is known and fixed at the time the application is written. Example data binding systems include the [[Java Architecture for XML Binding]] (JAXB), XML Serialization in [[.NET Framework]].{{cite web|url=http://msdn.microsoft.com/en-us/library/ms950721.aspx|title=XML Serialization in the .NET Framework|publisher=Msdn.microsoft.com|accessdate=31 July 2009}} and XML serialization in [[gSOAP]].       ===XML as data type===   ===XML as data type=== [...]



Ross Lamont: Clarified and normalised references to pars of DSDL

Fri, 15 Sep 2017 08:28:11 GMT

Clarified and normalised references to pars of DSDL ← Previous revision Revision as of 08:28, 15 September 2017 Line 187: Line 187:       ===Schematron===   ===Schematron=== − [[Schematron]] is a language for making [[Assertion (computing)|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 (ISO/IEC 19757 Part 3: ''Rule-based validation'' ). + [[Schematron]] is a language for making [[Assertion (computing)|assertions]] about the presence or absence of patterns in an XML document. It typically uses [[XPath]] expressions. Schematron is now a standard (Part 3: ''Rule-based validation'' of [[DSDL|ISO/IEC 19757 - DSDL]]).       ===DSDL and other schema languages===   ===DSDL and other schema languages=== Line 206: Line 206:   * [[XML Signature]] defines syntax and processing rules for creating [[digital signature]]s on XML content.   * [[XML Signature]] defines syntax and processing rules for creating [[digital signature]]s on XML content.   * [[XML Encryption]] defines syntax and processing rules for [[encryption|encrypting]] XML content.   * [[XML Encryption]] defines syntax and processing rules for [[encryption|encrypting]] XML content. − * [[xml-model]] defines a means of associating any xml document with any of the schema types mentioned [[#Schemas and validation|above]]. + * [[xml-model]] (Part 11: ''Schema Association'' of [[DSDL|ISO/IEC 19757 - DSDL]]) defines a means of associating any xml document with any of the schema types mentioned [[#Schemas and validation|above]].       Some other specifications conceived as part of the "XML Core" have failed to find wide adoption, including [[XInclude]], [[XLink]], and [[XPointer]].   Some other specifications conceived as part of the "XML Core" have failed to find wide adoption, including [[XInclude]], [[XLink]], and [[XPointer]]. [...]



Ross Lamont: Relatively minor - mostly a tidy up of the wording around "standard", now embedding the actual standard number in the link to DSDL

Fri, 15 Sep 2017 08:01:38 GMT

Relatively minor - mostly a tidy up of the wording around "standard", now embedding the actual standard number in the link to DSDL ← Previous revision Revision as of 08:01, 15 September 2017 Line 184: Line 184:       ===RELAX NG===   ===RELAX NG=== − [[RELAX NG]] (Regular Language for XML Next Generation) was initially specified by [[OASIS (organization)|OASIS]] and is now also an ISO/IEC standard (ISO/IEC 19757 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 (programmer)|James Clark]]'s conversion tool—[http://www.thaiopensource.com/relaxng/trang.html 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-in (computing)|plug-ins]]; a RELAX NG schema author, for example, can require values in an XML document to conform to definitions in XML Schema Datatypes. + [[RELAX NG]] (Regular Language for XML Next Generation) was initially specified by [[OASIS (organization)|OASIS]] and is now a standard (Part 2: ''Regular-grammar-based validation'' of [[DSDL|ISO/IEC 19757 - 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 (programmer)|James Clark]]'s conversion tool—[http://www.thaiopensource.com/relaxng/trang.html 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-in (computing)|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===   ===Schematron=== [...]



Ross Lamont: /* Schematron */

Fri, 15 Sep 2017 07:46:18 GMT

‎Schematron ← Previous revision Revision as of 07:46, 15 September 2017 Line 187: Line 187:       ===Schematron===   ===Schematron=== − [[Schematron]] is a language for making [[Assertion (computing)|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). + [[Schematron]] is a language for making [[Assertion (computing)|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 (ISO/IEC 19757 Part 3: ''Rule-based validation'' ).       ===DSDL and other schema languages===   ===DSDL and other schema languages=== [...]



Ross Lamont: /* RELAX NG */

Fri, 15 Sep 2017 07:45:35 GMT

‎RELAX NG ← Previous revision Revision as of 07:45, 15 September 2017 Line 184: Line 184:       ===RELAX NG===   ===RELAX NG=== − [[RELAX NG]] (Regular Language for XML Next Generation) was initially specified by [[OASIS (organization)|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 (programmer)|James Clark]]'s conversion tool—[http://www.thaiopensource.com/relaxng/trang.html 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-in (computing)|plug-ins]]; a RELAX NG schema author, for example, can require values in an XML document to conform to definitions in XML Schema Datatypes. + [[RELAX NG]] (Regular Language for XML Next Generation) was initially specified by [[OASIS (organization)|OASIS]] and is now also an ISO/IEC standard (ISO/IEC 19757 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 (programmer)|James Clark]]'s conversion tool—[http://www.thaiopensource.com/relaxng/trang.html 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-in (computing)|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===   ===Schematron=== [...]