Subscribe: XML - Revision history
http://en.wikipedia.org/w/index.php?title=XML&action=history&feed=rss
Added By: Feedage Forager Feedage Grade B rated
Language: English
Tags:
attribute  code attribute  code  defines  document  inner greeting  language  line  org  ref {{cite  ref  revision  web  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: Thu, 27 Apr 2017 01:26:09 GMT

 



70.184.214.35: Alphabetized the categories.

Fri, 21 Apr 2017 01:38:14 GMT

Alphabetized the categories. ← Previous revision Revision as of 01:38, 21 April 2017 Line 140: Line 140:   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 "[[Draco (lawgiver)|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.{{cite web|url=http://diveintomark.org/archives/2004/01/16/draconianism|archiveurl=https://web.archive.org/web/20110726002036/http://diveintomark.org/archives/2004/01/16/draconianism|archivedate=2011-07-26|title=The history of draconian error handling in XML|year=2004|accessdate=18 July 2013|first=Mark|last=Pilgrim}} 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").{{cite web|url=http://diveintomark.org/archives/2004/01/08/postels-law|archiveurl=https://web.archive.org/web/20110514120305/http://diveintomark.org/archives/2004/01/08/postels-law|archivedate=2011-05-14|title=There are no exceptions to Postel's Law [dive into mark]|publisher=Web.archive.org|accessdate=22 April 2013}}   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 "[[Draco (lawgiver)|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.{{cite web|url=http://diveintomark.org/archives/2004/01/16/draconianism|archiveurl=https://web.archive.org/web/20110726002036/http://diveintomark.org/archives/2004/01/16/draconianism|archivedate=2011-07-26|title=The history of draconian error handling in XML|year=2004|accessdate=18 July 2013|first=Mark|last=Pilgrim}} 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").{{cite web|url=http://diveintomark.org/archives/2004/01/08/postels-law|archiveurl=https://web.archive.org/web/20110514120305/http://diveintomark.org/archives/2004/01/08/postels-law|archivedate=2011-05-14|title=There are no exceptions to Postel's Law [dive into mark]|publisher=Web.archive.org|accessdate=22 April 2013}}     − The XML specification defines a [[XML validation|valid XML document]] as a [[well-formed XML document]] which also conforms to the rules of a [[Document Type Definition]] (DTD).{{cite web|url=https://xmlnotepad.codeplex.com/|title=XML Notepad|publisher=}} + The XML specification defines a [[XML validation|valid XML document]] as a [[well-formed XML document]] which also conforms to the rules of a [[Document Type Definition]] (DTD).{{cite web|url=https://xmlnotepad.codeplex.com/|title=XML Notepad|publisher=}}{{cite web|url=https://www.microsoft.com/en-us/download/details.aspx?id=7973|title=XML Notepad 2007|publisher=}}{{cite web|url=https://www.microsoft.com/en-us/download/details.aspx?id=7973|title=XML Notepad 2007|publisher=}}         ==Schemas and validation==   ==Schemas and validation== Line 329: Line 329:   {{DEFAULTSORT:Xml}}   {{DEFAULTSORT:Xml}}   [[Category:Application layer protocols]]   [[Category:Application layer protocols]]   + [[Category:Articl[...]



MrOllie: Reverted 1 edit by Nathan Russell (talk): Rm non reference. (TW)

Thu, 13 Apr 2017 14:59:08 GMT

Reverted 1 edit by Nathan Russell (talk): Rm non reference. (TW) ← Previous revision Revision as of 14:59, 13 April 2017 Line 200: Line 200:   :* [[XSL-FO]] (XSL Formatting Objects), an XML language for rendering XML documents, often used to generate PDFs.   :* [[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.   :* [[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{{cite web|url=http://codingsight.com/xml-performance-tips/|title=XML performance tips}}, and is mainly conceived as a query language for [[XML database]]s. + * [[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 database]]s.   * [[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. [...]



Nathan Russell: Added a useful reference for the article about the methods for access, manipulate, return XML and etc.

Thu, 13 Apr 2017 14:57:28 GMT

Added a useful reference for the article about the methods for access, manipulate, return XML and etc. ← Previous revision Revision as of 14:57, 13 April 2017 Line 200: Line 200:   :* [[XSL-FO]] (XSL Formatting Objects), an XML language for rendering XML documents, often used to generate PDFs.   :* [[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.   :* [[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 database]]s. + * [[XQuery]] (XML Query) is an XML query language strongly rooted in XPath and XML Schema. It provides methods to access, manipulate and return XML{{cite web|url=http://codingsight.com/xml-performance-tips/|title=XML performance tips}}, and is mainly conceived as a query language for [[XML database]]s.   * [[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. [...]



TimBray: Undid erroneous revision

Tue, 11 Apr 2017 04:40:27 GMT

Undid erroneous revision ← Previous revision Revision as of 04:40, 11 April 2017 Line 71: Line 71:       ; Attribute   ; Attribute − : An ''attribute'' is a markup construct consisting of a name–value pair that exists within a start-tag or empty-element tag. An example is <img src="madonna.jpg" alt="Madonna" />, where the names of the attributes are "src" and "alt", and their values are "madonna.jpg" and "Madonna" respectively. Another example is <step number="3">Connect A to B.</step>, where the name of the attribute is "step number" and its value is "3". An XML attribute can only have a single value and each attribute can appear at most once on each element. In the common situation where a list of multiple values is desired, this must be done by encoding the list into a well-formed XML attributei.e., embedded quote characters would be a problem with some format beyond what XML defines itself. Usually this is either a comma or semi-colon delimited list or, if the individual values are known not to contain spaces,A common example of this is [[CSS]] class or identifier names. a space-delimited list can be used. <div class="inner greeting-box">Welcome!</div>, where the attribute "class" has both the value "inner greeting-box" and also indicates the two [[CSS]] class names "inner" and "greeting-box". + : An ''attribute'' is a markup construct consisting of a name–value pair that exists within a start-tag or empty-element tag. An example is <img src="madonna.jpg" alt="Madonna" />, where the names of the attributes are "src" and "alt", and their values are "madonna.jpg" and "Madonna" respectively. Another example is <step number="3">Connect A to B.</step>, where the name of the attribute is "number" and its value is "3". An XML attribute can only have a single value and each attribute can appear at most once on each element. In the common situation where a list of multiple values is desired, this must be done by encoding the list into a well-formed XML attributei.e., embedded quote characters would be a problem with some format beyond what XML defines itself. Usually this is either a comma or semi-colon delimited list or, if the individual values are known not to contain spaces,A common example of this is [[CSS]] class or identifier names. a space-delimited list can be used. <div class="inner greeting-box">Welcome!</div>, where the attribute "class" has both the value "inner greeting-box" and also indicates the two [[CSS]] class names "inner" and "greeting-box".       ; XML declaration   ; XML declaration [...]



47.208.72.241: /* Key terminology */

Sun, 09 Apr 2017 10:08:16 GMT

‎Key terminology ← Previous revision Revision as of 10:08, 9 April 2017 Line 71: Line 71:       ; Attribute   ; Attribute − : An ''attribute'' is a markup construct consisting of a name–value pair that exists within a start-tag or empty-element tag. An example is <img src="madonna.jpg" alt="Madonna" />, where the names of the attributes are "src" and "alt", and their values are "madonna.jpg" and "Madonna" respectively. Another example is <step number="3">Connect A to B.</step>, where the name of the attribute is "number" and its value is "3". An XML attribute can only have a single value and each attribute can appear at most once on each element. In the common situation where a list of multiple values is desired, this must be done by encoding the list into a well-formed XML attributei.e., embedded quote characters would be a problem with some format beyond what XML defines itself. Usually this is either a comma or semi-colon delimited list or, if the individual values are known not to contain spaces,A common example of this is [[CSS]] class or identifier names. a space-delimited list can be used. <div class="inner greeting-box">Welcome!</div>, where the attribute "class" has both the value "inner greeting-box" and also indicates the two [[CSS]] class names "inner" and "greeting-box". + : An ''attribute'' is a markup construct consisting of a name–value pair that exists within a start-tag or empty-element tag. An example is <img src="madonna.jpg" alt="Madonna" />, where the names of the attributes are "src" and "alt", and their values are "madonna.jpg" and "Madonna" respectively. Another example is <step number="3">Connect A to B.</step>, where the name of the attribute is "step number" and its value is "3". An XML attribute can only have a single value and each attribute can appear at most once on each element. In the common situation where a list of multiple values is desired, this must be done by encoding the list into a well-formed XML attributei.e., embedded quote characters would be a problem with some format beyond what XML defines itself. Usually this is either a comma or semi-colon delimited list or, if the individual values are known not to contain spaces,A common example of this is [[CSS]] class or identifier names. a space-delimited list can be used. <div class="inner greeting-box">Welcome!</div>, where the attribute "class" has both the value "inner greeting-box" and also indicates the two [[CSS]] class names "inner" and "greeting-box".       ; XML declaration   ; XML declaration [...]



TimBray: Undid revision 774367749 ; it was more idiomatic before

Sat, 08 Apr 2017 00:52:47 GMT

Undid revision 774367749 ; it was more idiomatic before ← Previous revision Revision as of 00:52, 8 April 2017 Line 192: Line 192:       ==Related specifications==   ==Related specifications== − 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 known as part of the XML core. + 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 namespace]]s enable the same document to contain XML elements and attributes taken from different vocabularies, without any [[naming collision]]s occurring. Although XML Namespaces are not part of the XML specification itself, virtually all XML software also supports XML Namespaces.   * [[XML namespace]]s enable the same document to contain XML elements and attributes taken from different vocabularies, without any [[naming collision]]s 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 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. [...]



Skirden: Fixed grammar, punctuation, etc. for article.

Fri, 07 Apr 2017 23:23:46 GMT

Fixed grammar, punctuation, etc. for article. ← Previous revision Revision as of 23:23, 7 April 2017 Line 192: Line 192:       ==Related specifications==   ==Related specifications== − 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. + 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 known as part of the XML core.   * [[XML namespace]]s enable the same document to contain XML elements and attributes taken from different vocabularies, without any [[naming collision]]s occurring. Although XML Namespaces are not part of the XML specification itself, virtually all XML software also supports XML Namespaces.   * [[XML namespace]]s enable the same document to contain XML elements and attributes taken from different vocabularies, without any [[naming collision]]s 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 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. [...]



2601:541:4305:C70:2D27:6A1C:AAED:4E82: fix link

Fri, 07 Apr 2017 19:07:38 GMT

fix link ← Previous revision Revision as of 19:07, 7 April 2017 Line 221: Line 221:   ===Simple API for XML===   ===Simple API for XML===   {{main|Simple API for XML}}   {{main|Simple API for XML}} − [[Simple API for XML]] (SAX) is a [[Lexical analysis|lexical]], [[Event-driven programming|event-driven]] API in which a document is read serially and its contents are reported as [[Callback (computer science)|callbacks]] to various [[Method (computer science)|methods]] on a [[Event handler|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. + [[Simple API for XML]] (SAX) is a [[Lexical analysis|lexical]], [[Event-driven programming|event-driven]] API in which a document is read serially and its contents are reported as [[Callback (computer programming)|callbacks]] to various [[Method (computer science)|methods]] on a [[Event handler|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===   ===Pull parsing=== [...]



Andy Dingley: Unencyclopedic and very poorly written addition. Undid revision 769730047 by 210.212.249.118 (talk)

Sat, 11 Mar 2017 10:11:40 GMT

Unencyclopedic and very poorly written addition. Undid revision 769730047 by 210.212.249.118 (talk) ← Previous revision Revision as of 10:11, 11 March 2017 Line 272: Line 272:   ==3dm==   ==3dm==   '''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.{{cite journal|author=Tancred Lindholm|title=A Three-way Merge for XML Documents|journal=ACM Symposium on Document Engineering|year=2004}}[http://doi.acm.org/10.1145/1030397.1030399]http://tdm.berlios.de/ - The homepage of 3dm   '''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.{{cite journal|author=Tancred Lindholm|title=A Three-way Merge for XML Documents|journal=ACM Symposium on Document Engineering|year=2004}}[http://doi.acm.org/10.1145/1030397.1030399]http://tdm.berlios.de/ - The homepage of 3dm −   − == Data-centric XML Datasets ==   − For Data-centric XML Datasets, the unique and distinct keyword search method, namely, XDMA{{Cite journal|last=Selvaganesan|first=S.|last2=Haw|first2=Su-Cheng|last3=Soon|first3=Lay-Ki|title=XDMA: A Dual Indexing and Mutual Summation Based Keyword Search Algorithm for XML Databases|url=http://www.worldscientific.com/doi/pdf/10.1142/S0218194014500223|journal=International Journal of Software Engineering and Knowledge Engineering|language=en-US|volume=24|issue=04|pages=591–615|doi=10.1142/s0218194014500223}} for XML databases is designed and developed based dual indexing and mutual summation.         ==See also==   ==See also== [...]



210.212.249.118: adding additional relevant content and citation

Sat, 11 Mar 2017 08:54:51 GMT

adding additional relevant content and citation ← Previous revision Revision as of 08:54, 11 March 2017 Line 272: Line 272:   ==3dm==   ==3dm==   '''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.{{cite journal|author=Tancred Lindholm|title=A Three-way Merge for XML Documents|journal=ACM Symposium on Document Engineering|year=2004}}[http://doi.acm.org/10.1145/1030397.1030399]http://tdm.berlios.de/ - The homepage of 3dm   '''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.{{cite journal|author=Tancred Lindholm|title=A Three-way Merge for XML Documents|journal=ACM Symposium on Document Engineering|year=2004}}[http://doi.acm.org/10.1145/1030397.1030399]http://tdm.berlios.de/ - The homepage of 3dm   +   + == Data-centric XML Datasets ==   + For Data-centric XML Datasets, the unique and distinct keyword search method, namely, XDMA{{Cite journal|last=Selvaganesan|first=S.|last2=Haw|first2=Su-Cheng|last3=Soon|first3=Lay-Ki|title=XDMA: A Dual Indexing and Mutual Summation Based Keyword Search Algorithm for XML Databases|url=http://www.worldscientific.com/doi/pdf/10.1142/S0218194014500223|journal=International Journal of Software Engineering and Knowledge Engineering|language=en-US|volume=24|issue=04|pages=591–615|doi=10.1142/s0218194014500223}} for XML databases is designed and developed based dual indexing and mutual summation.       ==See also==   ==See also== [...]