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:
abiolotemple gmail  code  data  document  internet  language  line  org  ref {{cite  ref  revision  web  xml  {{cite web  {{cite   
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, 22 Feb 2017 02:38:21 GMT

 



Nigelj: /* Applications of XML */ Why link this discussion to some random date in the past? The cited ref does not.

Wed, 08 Feb 2017 20:43:25 GMT

‎Applications of XML: Why link this discussion to some random date in the past? The cited ref does not. ← Previous revision Revision as of 20:43, 8 February 2017 Line 41: Line 41:       ==Applications of XML==   ==Applications of XML== − {{As of|2009}}, 100 document formats using XML syntax had 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 became the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]. 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]]. 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. [...]



83.145.206.39: /* Applications of XML */ SVG is a major XML-derived technology

Wed, 08 Feb 2017 20:25:07 GMT

‎Applications of XML: SVG is a major XML-derived technology ← Previous revision Revision as of 20:25, 8 February 2017 Line 41: Line 41:       ==Applications of XML==   ==Applications of XML== − {{As of|2009}}, 100 document formats using XML syntax had been developed,{{cite web|url= http://xml.coverpages.org/xmlApplications.html|title= XML Applications and Initiatives}} including [[RSS]], [[Atom (standard)|Atom]], [[SOAP]], and [[XHTML]]. XML-based formats became the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]. 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}} + {{As of|2009}}, 100 document formats using XML syntax had 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 became the default for many office-productivity tools, including [[Microsoft Office]] ([[Office Open XML]]), [[OpenOffice.org]] and [[LibreOffice]] ([[OpenDocument]]), and [[Apple Computer|Apple]]'s [[iWork]]. 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. [...]



JohnSawyer: /* Key terminology */ spelling or grammar? NOBODY KNOWS

Wed, 08 Feb 2017 10:51:19 GMT

‎Key terminology: spelling or grammar? NOBODY KNOWS ← Previous revision Revision as of 10:51, 8 February 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 name 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 "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 [...]



BG19bot: WP:CHECKWIKI error fix for #48. Remove link to the title inside the text. Do general fixes if a problem exists. - using AWB

Mon, 06 Feb 2017 07:55:34 GMT

WP:CHECKWIKI error fix for #48. Remove link to the title inside the text. Do general fixes if a problem exists. - using AWB ← Previous revision Revision as of 07:55, 6 February 2017 Line 26: Line 26:   | status = Published   | status = Published   | year_started = {{Start date and age|1996}}   | year_started = {{Start date and age|1996}} − | editors = {{ublist|class=nowrap |[[Tim Bray]] |[[Jean Paoli]] |[[Michael Sperberg-McQueen | C. M. Sperberg-McQueen]] |Eve Maler |François Yergeau |[[John W. Cowan | John Cowan]]}} + | editors = {{ublist|class=nowrap |[[Tim Bray]] |[[Jean Paoli]] |[[Michael Sperberg-McQueen|C. M. Sperberg-McQueen]] |Eve Maler |François Yergeau |[[John W. Cowan|John Cowan]]}}   | base_standards =   | base_standards =   | related_standards = [[W3C XML Schema|XML Schema]]   | related_standards = [[W3C XML Schema|XML Schema]] 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]]. 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}} + 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 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.   The design goals of XML emphasize simplicity, generality, and usa[...]



Anthony Appleyard: /* See also */ 3dm

Sun, 05 Feb 2017 06:47:56 GMT

‎See also: 3dm ← Previous revision Revision as of 06:47, 5 February 2017 Line 269: Line 269:   ==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. 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.   +   + ==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       ==See also==   ==See also== [...]



212.200.212.178: /* Comments */

Tue, 31 Jan 2017 12:03:54 GMT

‎Comments ← Previous revision Revision as of 12:03, 31 January 2017 Line 115: Line 115:       ===Comments===   ===Comments=== − 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;{{cite web|url=http://www.w3.org/TR/REC-xml/#sec-comments|title=Extensible Markup Language (XML)|publisher=W3C}} Section "Comments" 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. + 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;{{cite web|url=http://www.w3.org/TR/REC-xml/#sec-comments|title=Extensible Markup Language (XML)|publisher=W3C}} Section "Comments" 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:   An example of a valid comment: [...]



212.200.212.178: /* Further reading */ pdf not available at website, so I put web.archive.org link instead

Tue, 31 Jan 2017 11:16:17 GMT

‎Further reading: pdf not available at website, so I put web.archive.org link instead ← Previous revision Revision as of 11:16, 31 January 2017 Line 296: Line 296:   * {{cite web|url=http://www.oreillynet.com/xml/blog/2003/02/five_years_later_xml.html|title=Five years later, XML..|last=St. Laurent|first=Simon|date=February 12, 2003|work=O'Reilly XML Blog|publisher=[[O'Reilly Media]]|accessdate=26 October 2010}}   * {{cite web|url=http://www.oreillynet.com/xml/blog/2003/02/five_years_later_xml.html|title=Five years later, XML..|last=St. Laurent|first=Simon|date=February 12, 2003|work=O'Reilly XML Blog|publisher=[[O'Reilly Media]]|accessdate=26 October 2010}}   * {{cite web|url=http://www.w3.org/2008/02/xml10-pressrelease|title=W3C XML is Ten!|date=12 February 2008|publisher=[[World Wide Web Consortium]]|accessdate=26 October 2010}}   * {{cite web|url=http://www.w3.org/2008/02/xml10-pressrelease|title=W3C XML is Ten!|date=12 February 2008|publisher=[[World Wide Web Consortium]]|accessdate=26 October 2010}} − * {{cite web|url=http://wam.inrialpes.fr/courses/PG-MoSIG12/xml.pdf|title=Introduction to XML|date=October 2012|work=Course Slides|publisher=[[Pierre Geneves]]}} + * {{cite web|url=https://web.archive.org/web/20151016053704/http://wam.inrialpes.fr/courses/PG-MoSIG12/xml.pdf|title=Introduction to XML|date=October 2012|work=Course Slides|publisher=[[Pierre Geneves]]}}       ==External links==   ==External links== [...]



Gilliam: Reverted edits by 197.211.59.115 (talk) to last version by 116.193.130.231

Wed, 18 Jan 2017 15:55:30 GMT

Reverted edits by 197.211.59.115 (talk) to last version by 116.193.130.231 ← Previous revision Revision as of 15:55, 18 January 2017 Line 281: Line 281:   * [[XML Protocol]]   * [[XML Protocol]]     − Hi my name is morgan richi ,am from new York, am 30 years + ==Notes== − old, i got married at the age of 23 i have only one child and i + {{Reflist|group=note|liststyle=lower-roman}} − was living happily .After one year of my marriage my   − husband behavior became so strange and i don’t really   − understand what was going on, he packed out of the house   − to another woman i love him so much that i never dream’s   − of losing him, i try my possible best to make sure that my   − husband get back to me but all to no avail, i cry and cry   − seeking for help, i discussed it with my best friend sariah and   − she promise to help me. She told me of a man called   − abiolo, she told me he is a very great man and a real   − man that can be trusted and there is nothing concerning   − love issues he cannot solve and she told me how he has   − help countless number of people in restoring their   − relationship. I was really convince, I quickly contacted his   − email address at abiolotemple@gmail.com (abiolotemple@gmail.com> I   − explain all my problem to him, he told me that i should not   − worry that all my problems will be solved immediately. He   − told me what to do to get my husband back and i did, he   − said after 2days my husband will come back to me and start   − begging, and it really happen as he said, i was very surprise,   − this is so amazing. To God be the glory our relationship is   − now very tight and we both live happily again. If you having   − similar problem, Contact him now abiolotemple@gmail.com   − or   − what's app him +2348110033346 and get your problem solve once and   − for all. i am a living testimony to it. (1) If you want your ex   − back. (2) if you always have bad dreams or enlarge your penis or virgenal. (3) You want to be   − promoted in your office. (4) You want women/men to run   − after you. (5) If you want a child. (6) You want to tie your   − husband/wife to be yours forever. (7) If you need financial   − assistance. (8) How you been scammed and you want to   − recover you lost money. (9)if you want to stop your divorce.   − (10)if you want to divorce your husband. (11)if you want   − your wishes to be granted(12)if you need a cure for HIV/AIDS or harbs cure. once again   − the email address is abiolotemple@gmail.com and   − contact his   − what's app number +2348110033346 contact him   − immediately with this +2348110033346.....he is ever ready!!!!         ==References==   ==References== [...]



197.211.59.115: about a great spellcaster, how he help me

Wed, 18 Jan 2017 15:52:46 GMT

about a great spellcaster, how he help me ← Previous revision Revision as of 15:52, 18 January 2017 Line 281: Line 281:   * [[XML Protocol]]   * [[XML Protocol]]     − ==Notes== + Hi my name is morgan richi ,am from new York, am 30 years − {{Reflist|group=note|liststyle=lower-roman}} + old, i got married at the age of 23 i have only one child and i   + was living happily .After one year of my marriage my   + husband behavior became so strange and i don’t really   + understand what was going on, he packed out of the house   + to another woman i love him so much that i never dream’s   + of losing him, i try my possible best to make sure that my   + husband get back to me but all to no avail, i cry and cry   + seeking for help, i discussed it with my best friend sariah and   + she promise to help me. She told me of a man called   + abiolo, she told me he is a very great man and a real   + man that can be trusted and there is nothing concerning   + love issues he cannot solve and she told me how he has   + help countless number of people in restoring their   + relationship. I was really convince, I quickly contacted his   + email address at abiolotemple@gmail.com (abiolotemple@gmail.com> I   + explain all my problem to him, he told me that i should not   + worry that all my problems will be solved immediately. He   + told me what to do to get my husband back and i did, he   + said after 2days my husband will come back to me and start   + begging, and it really happen as he said, i was very surprise,   + this is so amazing. To God be the glory our relationship is   + now very tight and we both live happily again. If you having   + similar problem, Contact him now abiolotemple@gmail.com   + or   + what's app him +2348110033346 and get your problem solve once and   + for all. i am a living testimony to it. (1) If you want your ex   + back. (2) if you always have bad dreams or enlarge your penis or virgenal. (3) You want to be   + promoted in your office. (4) You want women/men to run   + after you. (5) If you want a child. (6) You want to tie your   + husband/wife to be yours forever. (7) If you need financial   + assistance. (8) How you been scammed and you want to   + recover you lost money. (9)if you want to stop your divorce.   + (10)if you want to divorce your husband. (11)if you want   + your wishes to be granted(12)if you need a cure for HIV/AIDS or harbs cure. once again   + the email address is abiolotemple@gmail.com and   + contact his   + what's app number +2348110033346 contact him   + immediately with this +2348110033346.....he is ever ready!!!!       ==References==   ==References== [...]



116.193.130.231: /* Pull parsing */

Fri, 06 Jan 2017 22:46:20 GMT

‎Pull parsing ← Previous revision Revision as of 22:46, 6 January 2017 Line 224: Line 224:       ===Pull parsing===   ===Pull parsing=== − Pull parsing[http://www.xml.com/pub/a/2005/07/06/tr.html Push, Pull, Next!] by Bob DuCharme, at XML.com treats the document as a series of items read in sequence using the [[Iterator pattern|iterator design pattern]]. This allows for writing of [[recursive descent parser]]s 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)|Java]] programming language, XMLPullParser in [[Smalltalk]], XMLReader in [[PHP]], ElementTree.iterparse in [[Python (programming language)|Python]], System.Xml.XmlReader in the [[.NET Framework]], and the DOM traversal APk (NodeIterator and TreeWalker). + Pull parsing[http://www.xml.com/pub/a/2005/07/06/tr.html Push, Pull, Next!] by Bob DuCharme, at XML.com treats the document as a series of items read in sequence using the [[Iterator pattern|iterator design pattern]]. This allows for writing of [[recursive descent parser]]s 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)|Java]] programming language, XMLPullParser in [[Smalltalk]], XMLReader in [[PHP]], ElementTree.iterparse in [[Python (programming language)|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, [[XML namespace|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.   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, [[XML namespace|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 wit[...]