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:
code  document  line line  line  org  previous revision  processor  ref  revision revision  revision  rfc  xml document  xml  ← previous 
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, 18 Oct 2017 15:10:54 GMT

 



TimBray: Undid revision 804914386; "valid" specifically refers to presence of, and agreement with, a DTD.

Sat, 14 Oct 2017 03:47:46 GMT

Undid revision 804914386; "valid" specifically refers to presence of, and agreement with, a DTD. ← Previous revision Revision as of 03:47, 14 October 2017 Line 145: Line 145:       ==Schemas and validation==   ==Schemas and validation== − In addition to being well-formed, an XML document may be ''valid''. This means that it contains a reference to a [[Document Type Definition]] (DTD) or [[XML schema]] defining the allowable content, and that its elements and attributes are declared in the definition and follow the grammatical rules for them that the definition specifies. + In addition to being well-formed, an XML document may be ''valid''. This means that it contains a reference to a [[Document Type Definition]] (DTD), and that its elements and attributes are declared in that DTD and follow the grammatical rules for them that the DTD specifies.       XML processors are classified as ''validating'' or ''non-validating'' depending on whether or not they check XML documents for validity. A processor that discovers a validity error must be able to report it, but may continue normal processing.   XML processors are classified as ''validating'' or ''non-validating'' depending on whether or not they check XML documents for validity. A processor that discovers a validity error must be able to report it, but may continue normal processing. [...]



DesmondW: /* Versions */ Fixed grammar

Wed, 11 Oct 2017 22:11:14 GMT

‎Versions: Fixed grammar ← Previous revision Revision as of 22:11, 11 October 2017 Line 260: Line 260:   There are two current versions of XML. The first (''XML 1.0'') was initially defined in 1998. It has undergone minor revisions since then, without being given a new version number, and is currently in its fifth edition, as published on November 26, 2008. It is widely implemented and still recommended for general use.   There are two current versions of XML. The first (''XML 1.0'') was initially defined in 1998. It has undergone minor revisions since then, without being given a new version number, and is currently in its fifth edition, as published on November 26, 2008. It is widely implemented and still recommended for general use.     − The second (''XML 1.1'') was initially published on February 4, 2004, the same day as XML 1.0 Third Edition,{{cite web|url=http://www.w3.org/TR/2004/REC-xml-20040204|title=Extensible Markup Language (XML) 1.0 (Third Edition)|publisher=W3.org|accessdate=22 August 2010}} and is currently in its second edition, as published on August 16, 2006. It contains features (some contentious) that are intended to make XML easier to use in certain cases.{{cite web|url=http://www.w3.org/TR/xml11/#sec-xml11|title=Extensible Markup Language (XML) 1.1 (Second Edition) , Rationale and list of changes for XML 1.1|accessdate=20 January 2012|publisher=W3C}} The main changes are to enable the use of line-ending characters used on [[EBCDIC]] platforms, and the use of scripts and characters absent from Unicode 3.2. XML 1.1 is not very widely implemented and is recommended for use only by those who need its unique features.{{cite book|last=Harold|first=Elliotte Rusty|title=Effective XML|publisher=Addison-Wesley|year=2004|pages=10–19|url=http://www.cafeconleche.org/books/effectivexml/|isbn=0-321-15040-6}} + The second (''XML 1.1'') was initially published on February 4, 2004, the same day as XML 1.0 Third Edition,{{cite web|url=http://www.w3.org/TR/2004/REC-xml-20040204|title=Extensible Markup Language (XML) 1.0 (Third Edition)|publisher=W3.org|accessdate=22 August 2010}} and is currently in its second edition, as published on August 16, 2006. It contains features (some contentious) that are intended to make XML easier to use in certain cases.{{cite web|url=http://www.w3.org/TR/xml11/#sec-xml11|title=Extensible Markup Language (XML) 1.1 (Second Edition) , Rationale and list of changes for XML 1.1|accessdate=20 January 2012|publisher=W3C}} The main changes are to enable the use of line-ending characters used on [[EBCDIC]] platforms, and the use of scripts and characters absent from Unicode 3.2. XML 1.1 is not very widely implemented and is recommended for use only by those who need its particular features.{{cite book|last=Harold|first=Elliotte Rusty|title=Effective XML|publisher=Addison-Wesley|year=2004|pages=10–19|url=http://www.cafeconleche.org/books/effectivexml/|isbn=0-321-15040-6}}       Prior to its fifth edition release, XML 1.0 differed from XML 1.1 in having stricter requirements for characters available for use in element and attribute names and unique identifiers: in the first four editions of XML 1.0 the characters were exclusively enumerated using a specific version of the [[Unicode]] standard (Unicode 2.0 to Unicode 3.2.) The fifth edition substitutes the mechanism of XML 1.1, which is more future-proof but reduces [[Redundancy (information theory)|redundancy]]. The approach taken in the fifth edition of XML 1.0 and in all editions of XML 1.1 is that only certain characters are forbidden in names, and everything else is allowed to accommodate suitable name characters in future Unicode versions. In the fifth edition, XML names may contain [...]



DesmondW: /* Programming interfaces */ Fixed grammar

Wed, 11 Oct 2017 22:06:21 GMT

‎Programming interfaces: Fixed grammar ← Previous revision Revision as of 22:06, 11 October 2017 Line 209: Line 209:       ==Programming interfaces==   ==Programming interfaces== − The design goals of XML include, "It shall be easy to write programs which process XML documents." Despite this, the XML specification contains almost no information about how programmers might go about doing such processing. The [[XML Infoset]] specification provides a vocabulary to refer to the constructs within an XML document, but also does not provide any guidance on how to access this information. A variety of [[API]]s for accessing XML have been developed and used, and some have been standardized. + The design goals of XML include, "It shall be easy to write programs which process XML documents." Despite this, the XML specification contains almost no information about how programmers might go about doing such processing. The [[XML Infoset]] specification provides a vocabulary to refer to the constructs within an XML document, but does not provide any guidance on how to access this information. A variety of [[API]]s for accessing XML have been developed and used, and some have been standardized.       Existing APIs for XML processing tend to fall into these categories:   Existing APIs for XML processing tend to fall into these categories: [...]



DesmondW: /* Schemas and validation */ Clarification

Wed, 11 Oct 2017 22:04:19 GMT

‎Schemas and validation: Clarification ← Previous revision Revision as of 22:04, 11 October 2017 Line 145: Line 145:       ==Schemas and validation==   ==Schemas and validation== − In addition to being well-formed, an XML document may be ''valid''. This means that it contains a reference to a [[Document Type Definition]] (DTD), and that its elements and attributes are declared in that DTD and follow the grammatical rules for them that the DTD specifies. + In addition to being well-formed, an XML document may be ''valid''. This means that it contains a reference to a [[Document Type Definition]] (DTD) or [[XML schema]] defining the allowable content, and that its elements and attributes are declared in the definition and follow the grammatical rules for them that the definition specifies.       XML processors are classified as ''validating'' or ''non-validating'' depending on whether or not they check XML documents for validity. A processor that discovers a validity error must be able to report it, but may continue normal processing.   XML processors are classified as ''validating'' or ''non-validating'' depending on whether or not they check XML documents for validity. A processor that discovers a validity error must be able to report it, but may continue normal processing. [...]



Guy Macon: Linkspam. Undid revision 802290802 by 72.163.220.4 (talk)

Mon, 25 Sep 2017 16:55:22 GMT

Linkspam. Undid revision 802290802 by 72.163.220.4 (talk) ← Previous revision Revision as of 16:55, 25 September 2017 Line 321: Line 321:   * [http://validator.w3.org/ http://validator.w3.org/] The Official [W3C] Markup Validation Service   * [http://validator.w3.org/ http://validator.w3.org/] The Official [W3C] Markup Validation Service   * [http://xml.silmaril.ie/ The XML FAQ] originally for the W3C's XML SIG by Peter Flynn   * [http://xml.silmaril.ie/ The XML FAQ] originally for the W3C's XML SIG by Peter Flynn − * [https://codebeautify.org/xmlviewer XML Viewer] XML tools to View, format and validate XML data   −         {{W3C Standards}}   {{W3C Standards}} [...]



72.163.220.4: /* External links */

Mon, 25 Sep 2017 06:17:23 GMT

‎External links ← Previous revision Revision as of 06:17, 25 September 2017 Line 321: Line 321:   * [http://validator.w3.org/ http://validator.w3.org/] The Official [W3C] Markup Validation Service   * [http://validator.w3.org/ http://validator.w3.org/] The Official [W3C] Markup Validation Service   * [http://xml.silmaril.ie/ The XML FAQ] originally for the W3C's XML SIG by Peter Flynn   * [http://xml.silmaril.ie/ The XML FAQ] originally for the W3C's XML SIG by Peter Flynn   + * [https://codebeautify.org/xmlviewer XML Viewer] XML tools to View, format and validate XML data   +       {{W3C Standards}}   {{W3C Standards}} [...]



Oshwah: Reverted edits by 182.186.254.235 (talk): editing tests (HG) (3.3.0)

Fri, 22 Sep 2017 20:23:16 GMT

Reverted edits by 182.186.254.235 (talk): editing tests (HG) (3.3.0) ← Previous revision Revision as of 20:23, 22 September 2017 Line 57: Line 57:   : An XML document is a string of ''characters''. Almost every legal [[Unicode]] character may appear in an XML document.   : An XML document is a string of ''characters''. Almost every legal [[Unicode]] character may appear in an XML document.     − ; Processor and appl + ; Processor and application −     : The ''processor'' analyzes the markup and passes structured information to an ''application''. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as an ''XML parser''.   : The ''processor'' analyzes the markup and passes structured information to an ''application''. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as an ''XML parser''.     [...]



182.186.254.235 at 20:23, 22 September 2017

Fri, 22 Sep 2017 20:23:03 GMT

← Previous revision Revision as of 20:23, 22 September 2017 Line 57: Line 57:   : An XML document is a string of ''characters''. Almost every legal [[Unicode]] character may appear in an XML document.   : An XML document is a string of ''characters''. Almost every legal [[Unicode]] character may appear in an XML document.     − ; Processor and application + ; Processor and appl   +   : The ''processor'' analyzes the markup and passes structured information to an ''application''. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as an ''XML parser''.   : The ''processor'' analyzes the markup and passes structured information to an ''application''. The specification places requirements on what an XML processor must do and not do, but the application is outside its scope. The processor (as the specification calls it) is often referred to colloquially as an ''XML parser''.     [...]



PlyrStar93: Reverted edits by 66.87.31.46 (talk) (HG) (3.3.0)

Thu, 21 Sep 2017 13:51:25 GMT

Reverted edits by 66.87.31.46 (talk) (HG) (3.3.0) ← Previous revision Revision as of 13:51, 21 September 2017 Line 1: Line 1: − {{stackistack índice + {{stack   | {{Infobox file format   | {{Infobox file format   | icon = | logo =   | icon = | logo =   | screenshot = [[File:XML.svg|200px|alt=]]   | screenshot = [[File:XML.svg|200px|alt=]] − | extension = .xml8 + | extension = .xml   |_nomimecode = on   |_nomimecode = on   | mime = {{ublist |application/xml |text/xml{{lower|0.2em|{{cite web |url=http://www.rfc-editor.org/rfc/rfc7303.txt |title=XML Media Types, RFC 7303 |publisher=Internet Engineering Task Force |date=July 2014}}}} }}   | mime = {{ublist |application/xml |text/xml{{lower|0.2em|{{cite web |url=http://www.rfc-editor.org/rfc/rfc7303.txt |title=XML Media Types, RFC 7303 |publisher=Internet Engineering Task Force |date=July 2014}}}} }} [...]



66.87.31.46 at 13:49, 21 September 2017

Thu, 21 Sep 2017 13:49:39 GMT

← Previous revision Revision as of 13:49, 21 September 2017 Line 1: Line 1: − {{stack + {{stackistack índice   | {{Infobox file format   | {{Infobox file format   | icon = | logo =   | icon = | logo =   | screenshot = [[File:XML.svg|200px|alt=]]   | screenshot = [[File:XML.svg|200px|alt=]] − | extension = .xml + | extension = .xml8   |_nomimecode = on   |_nomimecode = on   | mime = {{ublist |application/xml |text/xml{{lower|0.2em|{{cite web |url=http://www.rfc-editor.org/rfc/rfc7303.txt |title=XML Media Types, RFC 7303 |publisher=Internet Engineering Task Force |date=July 2014}}}} }}   | mime = {{ublist |application/xml |text/xml{{lower|0.2em|{{cite web |url=http://www.rfc-editor.org/rfc/rfc7303.txt |title=XML Media Types, RFC 7303 |publisher=Internet Engineering Task Force |date=July 2014}}}} }} [...]