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:
binding  data binding  data  highly structured  highly  line  ref  revision  serialization  structured  syntax  xml data  xml 
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: Tue, 27 Jun 2017 07:26:55 GMT

 



Ross Lamont: Created internal link to earlier in the page

Tue, 27 Jun 2017 01:02:37 GMT

Created internal link to earlier in the page ← Previous revision Revision as of 01:02, 27 June 2017 Line 202: Line 202:   * [[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 above. + * [[xml-model]] 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: Added a place-holder to a page about xml-model processing instruction.

Mon, 26 Jun 2017 01:04:56 GMT

Added a place-holder to a page about xml-model processing instruction. ← Previous revision Revision as of 01:04, 26 June 2017 Line 202: Line 202:   * [[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 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]]. [...]



Andy Dingley: /* Criticism */ dab

Tue, 20 Jun 2017 17:24:15 GMT

‎Criticism: dab ← Previous revision Revision as of 17:24, 20 June 2017 Line 267: Line 267:       ==Criticism==   ==Criticism== − XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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. However, [[XML data binding]] systems allow applications to access XML data directly from objects representing a [[data structure]] of the data in the programming language used, which ensures [[type safety]], rather than using the [[DOM]]{{dn|date=June 2017}} or [[SAX]]{{dn|date=June 2017}} to retrieve data from a direct representation of the XML itself. This is accomplished by automatically creating a mapping between elements of the XML schema [[XSD]] of the document and members of a class to be represented in memory. Other criticisms attempt to refute the claim that XML is a [[self-describing]] language{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as simpler alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. However, W3C standardized XML schema specifications offer a broader range of structured [[XSD]] data types compared to simpler serialization formats and offer modularity and reuse through [[XML namespace]]. + XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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. However, [[XML data binding]] systems allow applications to access XML data directly from objects representing a [[data structure]] of the data in the programming language used, which ensures [[type safety]], rather than using the [[Document Object Model|DOM]] or [[Simple API for XML|SAX]] to retrieve data from a direct representation of the XML itself. This is accomplished by automatically creating a mapping between elements of the XML schema [[XSD]] of the document and members of a class to be represented in memory. Other criticisms attempt to refute the claim that XML is a [[self-describing]] language{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as simpler alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. Ho[...]



Narky Blert: 2x DN tags

Tue, 20 Jun 2017 16:51:14 GMT

2x DN tags ← Previous revision Revision as of 16:51, 20 June 2017 Line 267: Line 267:       ==Criticism==   ==Criticism== − XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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. However, [[XML data binding]] systems allow applications to access XML data directly from objects representing a [[data structure]] of the data in the programming language used, which ensures [[type safety]], rather than using the [[DOM]] or [[SAX]] to retrieve data from a direct representation of the XML itself. This is accomplished by automatically creating a mapping between elements of the XML schema [[XSD]] of the document and members of a class to be represented in memory. Other criticisms attempt to refute the claim that XML is a [[self-describing]] language{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as simpler alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. However, W3C standardized XML schema specifications offer a broader range of structured [[XSD]] data types compared to simpler serialization formats and offer modularity and reuse through [[XML namespace]]. + XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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. However, [[XML data binding]] systems allow applications to access XML data directly from objects representing a [[data structure]] of the data in the programming language used, which ensures [[type safety]], rather than using the [[DOM]]{{dn|date=June 2017}} or [[SAX]]{{dn|date=June 2017}} to retrieve data from a direct representation of the XML itself. This is accomplished by automatically creating a mapping between elements of the XML schema [[XSD]] of the document and members of a class to be represented in memory. Other criticisms attempt to refute the claim that XML is a [[self-describing]] language{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as simpler alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. However, W3C standardize[...]



Andy Dingley: Undid revision 786446462 by 114.121.231.175 (talk)

Mon, 19 Jun 2017 15:01:03 GMT

Undid revision 786446462 by 114.121.231.175 (talk) ← Previous revision Revision as of 15:01, 19 June 2017 Line 31: Line 31:   | abbreviation = XML   | abbreviation = XML   | domain = [[Serialization|Data serialization]]   | domain = [[Serialization|Data serialization]] − | website = [/http://www.rumah.com/listing-properti/13286993/rec-xml XML 1.0] + | website = [http://www.w3.org/TR/rec-xml XML 1.0]   }} }}   }} }}     [...]



114.121.231.175 at 14:49, 19 June 2017

Mon, 19 Jun 2017 14:49:06 GMT

← Previous revision Revision as of 14:49, 19 June 2017 Line 31: Line 31:   | abbreviation = XML   | abbreviation = XML   | domain = [[Serialization|Data serialization]]   | domain = [[Serialization|Data serialization]] − | website = [http://www.w3.org/TR/rec-xml XML 1.0] + | website = [/http://www.rumah.com/listing-properti/13286993/rec-xml XML 1.0]   }} }}   }} }}     [...]



203.91.213.177 at 07:17, 14 June 2017

Wed, 14 Jun 2017 07:17:58 GMT

← Previous revision Revision as of 07:17, 14 June 2017 Line 14: Line 14:   | container_for = | contained_by =   | container_for = | contained_by =   | extended_from = [[Standard Generalized Markup Language|SGML]]   | extended_from = [[Standard Generalized Markup Language|SGML]] − | extended_to = {{hlist|list_style=line-height:1.35em; |[[List of XML markup languages|Numerous languages]], including [[XHTML]] |[[RSS]] |[[Atom (standard)|Atom]] |[[KMLSHIVA]]}} + | extended_to = {{hlist|list_style=line-height:1.35em; |[[List of XML markup languages|Numerous languages]], including [[XHTML]] |[[RSS]] |[[Atom (standard)|Atom]] |[[KML]]}}   | standard =   | standard =   {{Unbulleted list |item_style=padding:0.1em 0;line-height:1.2em;   {{Unbulleted list |item_style=padding:0.1em 0;line-height:1.2em; [...]



203.91.213.177 at 07:17, 14 June 2017

Wed, 14 Jun 2017 07:17:00 GMT

← Previous revision Revision as of 07:17, 14 June 2017 Line 14: Line 14:   | container_for = | contained_by =   | container_for = | contained_by =   | extended_from = [[Standard Generalized Markup Language|SGML]]   | extended_from = [[Standard Generalized Markup Language|SGML]] − | extended_to = {{hlist|list_style=line-height:1.35em; |[[List of XML markup languages|Numerous languages]], including [[XHTML]] |[[RSS]] |[[Atom (standard)|Atom]] |[[KML]]}} + | extended_to = {{hlist|list_style=line-height:1.35em; |[[List of XML markup languages|Numerous languages]], including [[XHTML]] |[[RSS]] |[[Atom (standard)|Atom]] |[[KMLSHIVA]]}}   | standard =   | standard =   {{Unbulleted list |item_style=padding:0.1em 0;line-height:1.2em;   {{Unbulleted list |item_style=padding:0.1em 0;line-height:1.2em; [...]



Robert van Engelen: /* Data binding */ minor correction/clarification

Sat, 10 Jun 2017 15:38:09 GMT

‎Data binding: minor correction/clarification ← Previous revision Revision as of 15:38, 10 June 2017 Line 232: Line 232:       ===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 the [[gSOAP]] toolkit. + [[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 as data type===   ===XML as data type=== [...]



Robert van Engelen: /* Criticism */ added reference to XML data binding systems -- alleviates the concerns with the difficulty of mapping the "tree model" to type systems, which is settled for years (see links)

Sat, 10 Jun 2017 15:34:14 GMT

‎Criticism: added reference to XML data binding systems -- alleviates the concerns with the difficulty of mapping the "tree model" to type systems, which is settled for years (see links) ← Previous revision Revision as of 15:34, 10 June 2017 Line 267: Line 267:       ==Criticism==   ==Criticism== − XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. + XML and its extensions have regularly been criticized for verbosity and complexity.Jeff Atwood (2009): [http://www.codinghorror.com/blog/2008/05/xml-the-angle-bracket-tax.html XML: The Angle Bracket Tax] Mapping the basic tree model of XML to [[type system]]s 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. However, [[XML data binding]] systems allow applications to access XML data directly from objects representing a [[data structure]] of the data in the programming language used, which ensures [[type safety]], rather than using the [[DOM]] or [[SAX]] to retrieve data from a direct representation of the XML itself. This is accomplished by automatically creating a mapping between elements of the XML schema [[XSD]] of the document and members of a class to be represented in memory. Other criticisms attempt to refute the claim that XML is a [[self-describing]] language{{cite web|url=http://workflow.healthbase.info/monographs/XML_myths_Browne.pdf|format=PDF|title=The Myth of Self-Describing XML|date=September 2003}} (though the XML specification itself makes no such claim). [[JSON]], [[YAML]], and [[S-expression|S-Expressions]] are frequently proposed as simpler alternatives (see [[Comparison of data serialization formats]]);Stackoverflow: [https://stackoverflow.com/questions/51492/what-usable-alternatives-to-xml-syntax-do-you-know What usable alternatives to XML syntax do you know?] that focus on representing highly structured data rather than documents, which may contain both highly structured and relatively unstructured content. However, W3C standardized XML schema specifications offer a broader range of structured [[XSD]] data types compared to simpler serialization formats and offer modularity and reuse through [[XML namespace]].       ==3dm==   ==3dm== [...]