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:
accessdate  data  document  format  language  line  org  ref {{cite  ref  revision  unicode  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: Mon, 11 Dec 2017 21:49:18 GMT

 



ClueBot NG: Reverting possible vandalism by 2405:204:3117:432B:ED20:ACD5:3C45:C66 to version by SporkBot. Report False Positive? Thanks, ClueBot NG. (3219267) (Bot)

Mon, 11 Dec 2017 13:30:47 GMT

Reverting possible vandalism by 2405:204:3117:432B:ED20:ACD5:3C45:C66 to version by SporkBot. Report False Positive? Thanks, ClueBot NG. (3219267) (Bot) ← Previous revision Revision as of 13:30, 11 December 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]]. 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|website=Dblab.ntua.gr |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-20021231e|website=W3.org|accessdate=16 November 2017}}{{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|website=Dblab.ntua.gr |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-20021231e|website=W3.org|accessdate=16 November 2017}}       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|website=W3.org |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 usability across the [[Internet]].{{cite web |title=XML 1.0 Origin and Goals |url=http://www.w3.org/TR/REC-xml/#sec-origin-goals|website=W3.org |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[...]



2405:204:3117:432B:ED20:ACD5:3C45:C66 at 13:30, 11 December 2017

Mon, 11 Dec 2017 13:30:43 GMT

← Previous revision Revision as of 13:30, 11 December 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]]. 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|website=Dblab.ntua.gr |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-20021231e|website=W3.org|accessdate=16 November 2017}} + 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|website=Dblab.ntua.gr |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-20021231e|website=W3.org|accessdate=16 November 2017}}{{cite web |title=XML 1.0 Origin and Goals |url=http://www.w3.org/TR/REC-xml/#sec-origin-goals|website=W3.org |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 usability across the [[Internet]].{{cite web |title=XML 1.0 Origin and Goals |url=http://www.w3.org/TR/REC-xml/#sec-origin-goals|website=W3.org |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. [...]



SporkBot: Remove template per TFD outcome

Fri, 17 Nov 2017 05:21:41 GMT

Remove template per TFD outcome ← Previous revision Revision as of 05:21, 17 November 2017 Line 129: Line 129:       ===International use===   ===International use=== − {{ChineseText|example}}{{Contains Armenian text|example}}{{CyrillicText|example}} + {{Contains Armenian text|example}}{{CyrillicText|example}}   XML 1.0 (Fifth Edition) and XML 1.1 support the direct use of almost any [[Unicode]] character in element names, attributes, comments, character data, and processing instructions (other than the ones that have special symbolic meaning in XML itself, such as the less-than sign, "<"). The following is a well-formed XML document including [[Chinese character|Chinese]], [[Armenian alphabet|Armenian]] and [[Cyrillic script|Cyrillic]] characters:   XML 1.0 (Fifth Edition) and XML 1.1 support the direct use of almost any [[Unicode]] character in element names, attributes, comments, character data, and processing instructions (other than the ones that have special symbolic meaning in XML itself, such as the less-than sign, "<"). The following is a well-formed XML document including [[Chinese character|Chinese]], [[Armenian alphabet|Armenian]] and [[Cyrillic script|Cyrillic]] characters:     [...]



Derek R Bullamore: Filled in 5 bare reference(s) with reFill ()

Thu, 16 Nov 2017 16:08:37 GMT

Filled in 5 bare reference(s) with reFill () ← Previous revision Revision as of 16:08, 16 November 2017 Line 103: Line 103:   The Unicode character set can be encoded into bytes for storage or transmission in a variety of different ways, called "encodings". Unicode itself defines encodings that cover the entire repertoire; well-known ones include [[UTF-8]] and [[UTF-16]].{{cite web|url=http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF|title=Characters vs. Bytes|website=Tbray.org|accessdate=16 November 2017}} There are many other text encodings that predate Unicode, such as [[ASCII]] and [[ISO/IEC 8859]]; their character repertoires in almost every case are subsets of the Unicode character set.   The Unicode character set can be encoded into bytes for storage or transmission in a variety of different ways, called "encodings". Unicode itself defines encodings that cover the entire repertoire; well-known ones include [[UTF-8]] and [[UTF-16]].{{cite web|url=http://www.tbray.org/ongoing/When/200x/2003/04/26/UTF|title=Characters vs. Bytes|website=Tbray.org|accessdate=16 November 2017}} There are many other text encodings that predate Unicode, such as [[ASCII]] and [[ISO/IEC 8859]]; their character repertoires in almost every case are subsets of the Unicode character set.     − XML allows the use of any of the Unicode-defined encodings, and any other encodings whose characters also appear in Unicode. XML also provides a mechanism whereby an XML processor can reliably, without any prior knowledge, determine which encoding is being used.{{cite web|url=http://www.w3.org/TR/REC-xml/#sec-guessing|title=Autodetection of Character Encodings}} Encodings other than UTF-8 and UTF-16 are not necessarily recognized by every XML parser. + XML allows the use of any of the Unicode-defined encodings, and any other encodings whose characters also appear in Unicode. XML also provides a mechanism whereby an XML processor can reliably, without any prior knowledge, determine which encoding is being used.{{cite web|url=http://www.w3.org/TR/REC-xml/#sec-guessing|title=Autodetection of Character Encodings|website=W3.org|accessdate=16 November 2017}} Encodings other than UTF-8 and UTF-16 are not necessarily recognized by every XML parser.       ===Escaping===   ===Escaping===   XML provides ''[[Escape sequence|escape]]'' facilities for including characters that are problematic to include directly. For example:   XML provides ''[[Escape sequence|escape]]'' facilities for including characters that are problematic to include directly. For example: − * The characters "<" and "&" are key syntax markers and may ''never'' appear in content outside a [[CDATA]] section. It is allowed, but not recommended, to use "<" in XML entity values.http://www.w3.org/TR/2008/REC-xml-20081126/#NT-AttValue + * The characters "<" and "&" are key syntax markers and may ''never'' appear in content outside a [[CDATA]] section. It is allowed, but not recommended, to use "<" in XML entity values.{{cite web|url=http://www.w3.org/TR/2008/REC-xml-20081126/#NT-AttValue|title=Extensible Markup Language (XML) 1.0 (Fifth Edition)|website=W3.org|accessdate=16 November 2017}}   * Some character encodings support only a subset of Unicode. For example, it is legal to encode an XML document in ASCII, but ASCII lacks code points for Unicode characters such as "é".   * Some character encodings support only a subset of Unicode. For example, it is legal to encode an XML document in ASCII, but ASCII lacks code points for Unicode characters such as "é".   * It might not be possible to type the character on the author's machine. [...]



Derek R Bullamore: Improved referencing

Thu, 16 Nov 2017 16:06:23 GMT

Improved referencing

Show changes



AnomieBOT: Dating maintenance tags: {{Linkrot}}

Thu, 16 Nov 2017 15:26:46 GMT

Dating maintenance tags: {{Linkrot}}

← Previous revision Revision as of 15:26, 16 November 2017
Line 1: Line 1:
{{Linkrot}}
+
{{Linkrot|date=November 2017}}
 
{{stack
 
{{stack
 
| {{Infobox file format
 
| {{Infobox file format



Doomdorm64 at 13:26, 16 November 2017

Thu, 16 Nov 2017 13:26:43 GMT

← Previous revision Revision as of 13:26, 16 November 2017
Line 1: Line 1:
  +
{{Linkrot}}
 
{{stack
 
{{stack
 
| {{Infobox file format
 
| {{Infobox file format



137.97.13.86: /* Key terminology */

Sun, 12 Nov 2017 18:54:31 GMT

‎Key terminology ← Previous revision Revision as of 18:54, 12 November 2017 Line 57: Line 57:   Further guidelines for the use of XML in a networked context appear in RFC 3470, also known as IETF BCP 70, a document covering many aspects of designing and deploying an XML-based language.   Further guidelines for the use of XML in a networked context appear in RFC 3470, also known as IETF BCP 70, a document covering many aspects of designing and deploying an XML-based language.     − ==Key Terminology== + ==Key terminology==   The material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs that appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use.   The material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs that appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use.     [...]



137.97.13.86: /* Key Terminology */

Sun, 12 Nov 2017 18:53:13 GMT

‎Key Terminology ← Previous revision Revision as of 18:53, 12 November 2017 Line 57: Line 57:   Further guidelines for the use of XML in a networked context appear in RFC 3470, also known as IETF BCP 70, a document covering many aspects of designing and deploying an XML-based language.   Further guidelines for the use of XML in a networked context appear in RFC 3470, also known as IETF BCP 70, a document covering many aspects of designing and deploying an XML-based language.     − ==Key terminology== + ==Key Terminology==   The material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs that appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use.   The material in this section is based on the XML Specification. This is not an exhaustive list of all the constructs that appear in XML; it provides an introduction to the key constructs most often encountered in day-to-day use.     [...]



Uli.bethke: Added important and widely applied use cases for XML

Fri, 03 Nov 2017 18:42:35 GMT

Added important and widely applied use cases for XML ← Previous revision Revision as of 18:42, 3 November 2017 Line 44: Line 44:       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}}   +   + Most industry data standards, e.g. [[Health Level 7|HL7]], [[OpenTravel Alliance|OTA]], NDC, [[FpML]], [[MISMO]] etc. are based on XML and the rich features of the XML schema specification. [https://sonra.io/2017/11/03/library-xml-data-standards/ Many of these standards] are quite complex and it is not uncommon for a specification to comprise several thousand pages.   +   + In publishing, [[Darwin Information Typing Architecture|DITA]] is an XML industry data standard.  XML is used extensively to underpin various publishing formats.   +   + XML is widely used in a Services Oriented Architecture (SOA). Disparate systems communicate with each other by exchanging XML messages. The message exchange format is standardised as an XML schema (XSD). This is also referred to as the canonical schema.       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[...]