Extensible Markup Language

XML Specification and Origin[edit]

XML is a subset of the Standard Generalized Markup Language, or SGML (ISO8879-1986). XML's specification first emerged in 1996 through the efforts of the XML Special Interest Group and the SGML Editorial Review Board, chaired by John Bosak of Sun Microsystems. The group, also known as the XML Working Group, laid out the following set of guidelines or design goals for XML:

XML shall be straightforwardly usable over the Internet.

XML shall support a wide variety of applications.

XML shall be compatible with SGML.

It shall be easy to write programs which process XML documents.

The number of optional features in XML is to be kept to the absolute minimum, ideally zero.

XML documents should be human-legible and reasonably clear.

The XML design should be prepared quickly.

The design of XML shall be formal and concise.

XML documents shall be easy to create.

Terseness in XML markup is of minimal importance.

^[1]

Notably missing from the above list is efficiency. XML is plain text and can be verbose, and in applications where speed is everything, a different data representation may be preferred.

Grammar and Definitions[edit]

This section contains a brief over view of the components that define XML, for a more in-depth examination of those components read the individual sections under the heading Structure

Prolog - A prolog is a sort of 'announcement' to the XML parser as to what version the following set of XML objects is written in. The prolog also contains other information pertinent to the XML document (discussed later.)

<?xml version="1.0" standalone="no" ?>

Tag - A tag denotes the beginning, end, or existence of an XML object. They consist of the < character followed by the name of the tag, and, in the case of an opening tag, just a > at the end. The exception is with end tags and single tags. End Tags always have a < then a forward slash before the name of the tag with a > at the end. Single tags always have a space after the name of the tag followed by a forward slash and then end with the >.

Example

<ninja>
    <inventory>
        <nunchucks />
        <cookies />
    </inventory>
</ninja>

Element - An element is an XML object composed of a start tag and a stop tag or a single tag.

Example

<?xml version="1.0" standalone="no" ?>
<family>
    <member>
        <name>dad</name>
        <favorite-food>pancakes</favorite-food>
        <favorite-animal>wombats</favorite-animal>
    </member>
</family>

Document - A document is any XML object that contains a prolog and one or more elements excluding the root element.

<?xml version="1.0" standalone="no" ?>
<root-element>
    <lots-of-elements>
    ...
    </lots-of-elements>
</root-element>

Structure[edit]

Prolog[edit]

The XML prolog is a mandatory object present at the beginning of the document.

<?xml version="###" {encoding="???" standalone='y/n'} ?>

version equals the version of XML the document was written to.

(Optional) encoding equals the character codebook the document was written to. The default is UTF-8. The character encoding declaration must be written using latin characters only.^[2]

EncName    ::=    [A-Za-z] ([A-Za-z0-9._] | '-')*

The encoding name must begin with an alphabetic character and all other characters must be alphanumeric, the underscore ( _ ), the decimal ( . ), or a dash ( - ).

(Optional) standalone is either yes or no. Yes in the instance that the XML document does not have an external DTD or Schema. No if the XML document does have an external DTD or Schema.

Elements[edit]

An element is an XML object defined by the accompanying DTD or Schema that is described by the use of tags, parsed text, attributes, and entities. An element may consist of a start tag and a end tag or a single tag.

<?xml version="1.0" standalone="no" ?>
<army>
    <ninja name="woody">
        <inventory>
            <nunchucks count="2" />
            <cookies count="15" />
        </inventory>
    </ninja>
</army>

In this case, <army> represents a root element that contains a series of elements, in this example the element shown is a <ninja>. A ninja has an inventory that contains a certain number of nunchucks and a certain number of cookies. The number of cookies and nunchucks are defined by the attribute count. Note, the attribute values are in quotation marks, all well formed XML documents have their attributes quoted in that fashion either with single quotes ' or double quotes ".

References[edit]

↑ Bray, Tim, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, and François Yergeau, eds. "Extensible Markup Language (XML) 1.0 (Fourth Edition)." World Wide Web Consortium Recommendations. 29 Sept. 2006. 18 May 2007 <http://www.w3.org/TR/2006/REC-xml-20060816/#sec-origin-goals>.
↑ Bray, Tim, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, and François Yergeau, eds. "Extensible Markup Language (XML) 1.0 (Fourth Edition)." World Wide Web Consortium Recommendations. 29 Sept. 2006. 18 May 2007 <http://www.w3.org/TR/2004/REC-xml-20040204/#NT-EncodingDecl> §4.3.3 Character Encoding in Entities.

External links[edit]

http://www.w3schools.com/xml/

Related Technologies[edit]

[1] Bray, Tim, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, and François Yergeau, eds. "Extensible Markup Language (XML) 1.0 (Fourth Edition)." World Wide Web Consortium Recommendations. 29 Sept. 2006. 18 May 2007 <http://www.w3.org/TR/2006/REC-xml-20060816/#sec-origin-goals>.

[2] Bray, Tim, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, and François Yergeau, eds. "Extensible Markup Language (XML) 1.0 (Fourth Edition)." World Wide Web Consortium Recommendations. 29 Sept. 2006. 18 May 2007 <http://www.w3.org/TR/2004/REC-xml-20040204/#NT-EncodingDecl> §4.3.3 Character Encoding in Entities.

[1]

[2]