XML

From Wikipedia, the free encyclopedia XML XML XML Filename extension Internet media type Uniform Type Identifier Developed by Type of format Extended from Extended to Standard(s) .xml application/xml, text/ xml (deprecated) public.xml World Wide Web Consortium Markup language SGML XHTML, RSS, Atom, ... 1.0 (Fifth Edition) 1.1 (Second Edition) presentation environments. Most importantly, XML provides a basic syntax that can be used to share information between different kinds of computers, different applications, and different organizations without needing to pass through many layers of conversion.[4] [5] XML began as a simplified subset of the Standard Generalized Markup Language (SGML), meant to be readable by people via semantic constraints; application languages can be implemented in XML. These include XHTML,[6] RSS, MathML, GraphML, Scalable Vector Graphics, MusicXML, and others. Moreover, XML is sometimes used as the specification language for such application languages. XML is recommended by the World Wide Web Consortium (W3C). It is a fee-free open standard. The recommendation specifies lexical grammar and parsing requirements. Correctness An XML document has two correctness levels: • . A well-formed document conforms to the XML syntax rules; e.g. if a start-tag (< >) appears without a corresponding end-tag (), it is not well-formed. A document not well-formed is not in XML; a conforming parser is disallowed from processing it. • . A valid document additionally conforms to semantic rules, either user-defined or in an XML schema, especially DTD; e.g. if a document contains an undefined element, then it is not valid; a validating parser is disallowed from processing it. XML (Extensible Markup Language) is a general-purpose specification for creating custom markup languages.[1] It is classified as an extensible language, because it allows the user to define the mark-up elements. XML’s purpose is to aid information systems in sharing structured data, especially via the Internet, [2] to encode documents, and to serialize data; in the last context, it compares with text-based serialization languages such as JSON, YAML and S-Expressions. [3] XML’s set of tools helps developers in creating web pages but its usefulness goes well beyond that. XML, in combination with other standards, makes it possible to define the content of a document separately from its formatting, making it easy to reuse that content in other applications or for other Well-formedness If only a well-formed element is required, XML is a generic framework for storing any amount of text or any data whose structure can be represented as a tree. The only indispensable syntactical requirement is that the document has exactly one root element (also known as the document element), i.e. the text must be enclosed between a root 1 From Wikipedia, the free encyclopedia start-tag and a corresponding end-tag, known as a "well-formed" XML document: This is a book... The root element can be preceded by an optional (for XML 1.0 only) XML declaration element stating what XML version is in use (normally 1.0); it might also contain character encoding and external dependencies information. Starting with XML version 1.1, this declaration becomes mandatory. This is necessary, as an XML document without an XML declaration is assumed to be a version 1.0 document. XML Mix all ingredients together.Knead thoroughly. Cover with a cloth, and leave for o Knead again. Place in a bread baking tin. Cover with a cloth, and leave for o Bake in the oven at 180(degrees)C f Attribute values must always be quoted, using single or double quotes, and each attribute name may appear only once in any single element. XML requires that elements be properly nested—elements may never overlap, and so must be closed in the order opposite to which they are opened. For example, this fragment The specification requires that processors of of code below cannot be part of a well-formed XML support the pan-Unicode character enXML document because the title and author codings UTF-8 and UTF-16 (UTF-32 is not elements are closed in the wrong order: mandatory). The use of more limited encodings, e.g. those based on ISO/IEC 8859, is ac knowledged, widely used, and supported. < Comments can be placed anywhere in the tree, including in the text if the content of the One way of writing the same information in a element is text or #PCDATA. way which could be incorporated into a wellXML comments start with . Two consecutive dashes (--) may not appear anywhere in the text of the comment. Aristotle XML provides special syntax for representing In any meaningful application, additional an element with empty content. Instead of markup is used to structure the contents of writing a start-tag followed immediately by the XML document. The text enclosed by the an end-tag, a document may contain an root tags may contain an arbitrary number of empty-element tag. An empty-element tag reXML elements. The basic syntax for one elesembles a start-tag but contains a slash just ment is: before the closing angle bracket. The following three examples are equivalent in XML: Element Content The two instances of «element_name» are re ferred to as the start-tag and end-tag, re spectively. Here, «Element Content» is some text which may again contain XML elements. An empty-element may contain attributes: So, a generic XML document contains a tree An entity in XML is a named body of data, usually text. Entities are often used to represFlour ent single characters that cannot easily be Yeast entered on the keyboard; they are also used Water to represent pieces of standard Salt ("boilerplate") text that occur in many Entity references 2 From Wikipedia, the free encyclopedia documents, especially if there is a need to allow such text to be changed in one place only. Special characters can be represented either using entity references, or by means of numeric character references. An example of a numeric character reference is "€", which refers to the Euro symbol by means of its Unicode codepoint in hexadecimal. An entity reference is a placeholder that represents that entity. It consists of the entity’s name preceded by an ampersand ("&") and followed by a semicolon (";"). XML has five predeclared entities: • & (& or "ampersand") • < (< or "less than") • > (> or "greater than") • ' (’ or "apostrophe") • " (" or "quotation mark") Here is an example using a predeclared XML entity to represent the ampersand in the name "AT&T": XML not easily encodable, such as an Arabic character in a document produced on a European computer. The ampersand in the "AT&T" example could also be escaped like this (decimal 38 and hexadecimal 26 both represent the Unicode code point for the "&" character): AT&T AT&T Similarly, in the previous example, notice that "©" is used to generate the “©” symbol. See also numeric character references. Well-formed documents In XML, a well-formed document must conform to the following rules, among others: • Non-empty elements are delimited by both a start-tag and an end-tag. • Empty elements may be marked with an empty-element (self-closing) tag, such as . This is equal to . AT&T • All attribute values are quoted with either single (’) or double (") quotes. Single Additional entities (beyond the predefined quotes close a single quote and double ones) can be declared in the document’s quotes close a double quote.[7][8] Document Type Definition (DTD). A basic ex• To include a double quote inside an ample of doing so in a minimal internal DTD attribute value that is double quoted, or a follows. Declared entities can describe single single quote inside an attribute value that characters or pieces of text, and can referis single quoted, escape the inner quote ence each other. mark using entity references. • Tags may be nested but must not overlap. contained in another element. ]> character encoding. The encoding may be declared or implied externally, such as in ©right-notice; "Content-Type" headers when a document is transported via HTTP, or internally, using explicit markup at the very When viewed in a suitable browser, the XML beginning of the document. When no such document above appears as: declaration exists, a Unicode encoding is Copyright © 2009, XYZ Enterprises assumed, as defined by a Unicode Byte Order Mark before the document’s first Numeric character references character. If the mark does not exist, Numeric character references look like entity UTF-8 encoding is assumed. references, but instead of a name, they conElement names are case-sensitive. For extain the "#" character followed by a number. ample, the following is a well-formed matchThe number (in decimal or "x"-prefixed hexaing pair: decimal) represents a Unicode code point. ... Unlike entity references, they are neither whereas these are not predeclared nor do they need to be declared ... in the document’s DTD. They have typically been used to represent characters that are 3 From Wikipedia, the free encyclopedia ... XML assignments that affect how information is processed; for example, the ’month’ eleBy carefully choosing the names of the XML ment’s character data may be defined as beelements one may convey the meaning of the ing a month according to a particular schema data in the markup. This increases human language’s conventions, perhaps meaning readability while retaining the rigor needed that it must not only be formatted a certain for software parsing. way, but also must not be processed as if it Choosing meaningful names implies the were some other type of data. semantics of elements and attributes to a huAn XML document that complies with a man reader without reference to external particular schema/DTD, in addition to being documentation. However, this can lead to well-formed, is said to be valid. verbosity, which complicates authoring and Before the advent of generalised data deincreases file size. scription languages such as SGML and XML, software designers had to define special file Automatic verification formats or small languages to share data between programs. This required writing deIt is relatively simple to verify that a docutailed specifications and special-purpose ment is well-formed or validated XML, beparsers and writers. cause the rules of well-formedness and validXML’s regular structure and strict parsing ation of XML are designed for portability of rules allow software designers to leave parstools. The idea is that any tool designed to ing to standard tools, and since XML work with XML files will be able to work with provides a general, data model-oriented XML files written in any XML language (or framework for the development of XML application). Here are some examples of application-specific languages, software deways to verify XML documents: signers need only concentrate on the devel• load it into an XML-capable browser, such opment of rules for their data, at relatively as Firefox or Internet Explorer high levels of abstraction. • use a tool like xmlwf (usually bundled with Well-tested tools exist to validate an XML expat) document "against" a schema: the tool auto• parse the document, for instance in Ruby: matically verifies whether the document conirb> require "rexml/document" forms to constraints expressed in the irb> include REXML schema. Some of these validation tools are irb> doc = Document.new(File.new("test.xml")).root included in XML parsers, and some are packaged separately. Other usages of schemas exist: XML editors, for instance, can use schemas to support By leaving the names, allowable hierarchy, the editing process (by suggesting valid eleand meanings of the elements and attributes ments and attributes names, etc). open and definable by a customizable schema DTD or DTD, XML provides a syntactic foundation for the creation of purpose-specific, XMLThe oldest schema format for XML is the based markup languages. The general syntax Document Type Definition (DTD), inherited of such languages is rigid — documents must from SGML. While DTD support is ubiquitous adhere to the general rules of XML, ensuring due to its inclusion in the XML 1.0 standard, that all XML-aware software can at least read it is seen as limited for the following reasons: and understand the relative arrangement of • It has no support for newer features of information within them. The schema merely XML, most importantly namespaces. supplements the syntax rules with a set of • It lacks expressiveness. Certain formal constraints. Schemas typically restrict eleaspects of an XML document cannot be ment and attribute names and their allowable captured in a DTD. containment hierarchies, such as only allow• It uses a custom non-XML syntax, ing an element named ’birthday’ to contain inherited from SGML, to describe the one element named ’month’ and one element schema. named ’day’, each of which has to contain DTD is still used in many applications beonly character data. The constraints in a cause it is considered the easiest to read and schema may also include data type write. Validity 4 From Wikipedia, the free encyclopedia XML Some schema languages not only describe the structure of a particular XML format but also offer limited facilities to influence processing of individual XML files that conform to this format. DTDs and XSDs both have this ability; they can for instance provide attribute defaults. RELAX NG and Schematron intentionally do not provide these; for example the infoset augmentation facility. XML Schema A newer XML schema language, described by the W3C as the successor of DTDs, is XML Schema, or more informally referred to by the initialism for XML Schema instances, XSD (XML Schema Definition). XSDs are far more powerful than DTDs in describing XML languages. They use a rich datatyping system, allow for more detailed constraints on an XML document’s logical structure, and must be processed in a more robust validation framework. XSDs also use an XML-based format, which makes it possible to use ordinary XML tools to help process them, although XSD implementations require much more than just the ability to read XML. International use XML supports 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 open corner bracket, "<"). Therefore, the following is a well-formed XML document, even though it includes both Chinese and Cyrillic characters: Китайська мова RELAX NG Another popular schema language for XML is RELAX NG. Initially specified by OASIS, RELAX NG is now also an ISO international standard (as part of DSDL). It has two formats: an XML based syntax and a nonXML compact syntax. The compact syntax aims to increase readability and writability but, since there is a well-defined way to translate the compact syntax to the XML syntax and back again by means of James Clark’s Trang conversion tool, the advantage of using standard XML tools is not lost. RELAX NG has a simpler definition and validation framework than XML Schema, making it easier to use and implement. It also has the ability to use datatype framework plug-ins; a RELAX NG schema author, for example, can require values in an XML document to conform to definitions in XML Schema Datatypes. Displaying on the web Generally, generic XML documents do not carry information about how to display the data.[9] Without using CSS or XSLT, a generic XML document is rendered as raw XML text by most web browsers. Some display it with ’handles’ (e.g. + and - signs in the margin) that allow parts of the structure to be expanded or collapsed with mouse-clicks. In order to style the rendering in a browser with CSS, the XML document must include a reference to the stylesheet:[10] ISO DSDL and other schema languages The ISO DSDL (Document Schema Description Languages) standard brings together a comprehensive set of small schema languages, each targeted at specific problems. DSDL includes RELAX NG full and compact syntax, Schematron assertion language, and languages for defining datatypes, character repertoire constraints, renaming and entity expansion, and namespace-based routing of document fragments to different validators. DSDL schema languages do not have the vendor support of XML Schemas yet, and are to some extent a grassroots reaction of industrial publishers to the lack of utility of XML Schemas for publishing. element. XSLT (XSL Transformations) can be used to alter the format of XML data, either into HTML or other formats that are suitable for a browser to display. To specify client-side XSLT, the following processing instruction is required in the XML:[11] " syntax and the name "XML". Other names that had been put forward for consideration included "MAGMA" (Minimal Architecture for Generalized Markup Applications), "SLIM" (Structured Language for Internet Markup) and "MGML" (Minimal Generalized Markup Language). The co-editors of the specification were originally Tim Bray and Michael Sperberg-McQueen. Halfway through the project Bray accepted a consulting engagement with Netscape, provoking vociferous protests from Microsoft. Bray was temporarily asked to resign the editorship. This led to intense dispute in the Working Group, eventually solved by the appointment of Microsoft’s Jean Paoli as a third co-editor. The XML Working Group never met faceto-face; the design was accomplished using a combination of email and weekly teleconferences. The major design decisions were reached in twenty weeks of intense work between July and November 1996, when the first Working Draft of an XML specification was published.[28] Further design work continued through 1997, and XML 1.0 became a W3C Recommendation on February 10, 1998. Sources XML is a profile of an ISO standard SGML, and most of XML comes from SGML unchanged. From SGML comes the separation of logical and physical structures (elements and entities), the availability of grammarbased validation (DTDs), the separation of data and metadata (elements and attributes), mixed content, the separation of processing from representation (processing instructions), and the default angle-bracket syntax. Removed were the SGML Declaration (XML has a fixed delimiter set and adopts Unicode as the document character set). Other sources of technology for XML were the Text Encoding Initiative (TEI), which defined a profile of SGML for use as a ’transfer syntax’; HTML, in which elements were synchronous with their resource, the separation of document character set from resource encoding, the xml:lang attribute, and the HTTP notion that metadata accompanied the resource rather than being needed at the declaration of a link; and the Extended Reference Concrete Syntax (ERCS), from which XML 1.0’s naming rules were taken, and which had introduced hexadecimal numeric character references and the concept of references to make available all Unicode characters. Ideas that developed during discussion which were novel in XML, were the algorithm for encoding detection and the encoding header, the processing instruction target, the xml:space attribute, and the new close delimiter for empty-element tags. Versions 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 8 From Wikipedia, the free encyclopedia 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, 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[29] - mainly enabling the use of line-ending characters used on EBCDIC platforms, and the use of scripts and characters absent from Unicode 2.0. XML 1.1 is not very widely implemented and is recommended for use only by those who need its unique features. [30] Prior to the fifth edition of XML 1.0, it and XML 1.1 differed in the requirements of characters used for element and attribute names: the first four editions of XML 1.0 only allowed characters which are defined in Unicode 2.0, which includes most world scripts, but excludes those which were added in later Unicode versions. Among the excluded scripts are Mongolian, Cambodian, Amharic, Burmese, and others. Almost any Unicode character can be used in the character data and attribute values of an XML 1.1 document, even if the character is not defined, aside from having a code point, in the current version of Unicode. The approach in XML 1.1 is that only certain characters are forbidden, and everything else is allowed, whereas in older editions of XML 1.0, only certain characters were explicitly allowed, and thus prior to its fifth edition XML 1.0 could not accommodate the addition of characters in future versions of Unicode. In character data and attribute values, XML 1.1 allows the use of more control characters than XML 1.0, but, for "robustness", most of the control characters introduced in XML 1.1 must be expressed as numeric character references. Among the supported control characters in XML 1.1 are two line break codes that must be treated as whitespace. Whitespace characters are the only control codes that can be written directly. There are also discussions on an XML 2.0, although it seems unlikely if such will ever come about. XML-SW (SW for skunk works), written by one of the original developers of XML, contains some proposals for what an XML 2.0 might look like: elimination of DTDs from syntax, integration of namespaces, XML Base and XML Information Set (infoset) into the base standard. XML The World Wide Web Consortium also has an XML Binary Characterization Working Group doing preliminary research into use cases and properties for a binary encoding of the XML infoset. The working group is not chartered to produce any official standards. Since XML is by definition text-based, ITU-T and ISO are using the name Fast Infoset for their own binary infoset to avoid confusion (see ITU-T Rec. X.891 | ISO/IEC 24824-1). Patent claims In October 2005 the small company Scientigo publicly asserted that two of its patents, U.S. Patent 5,842,213 and U.S. Patent 6,393,426, apply to the use of XML. The patents cover the "modeling, storage and transfer [of data] in a particular non-hierarchical, non-integrated neutral form", according to their applications, which were filed in 1997 and 1999. Scientigo CEO Doyal Bryant expressed a desire to "monetize" the patents but stated that the company was "not interested in having us against the world." He said that Scientigo was discussing the patents with several large corporations.[31] XML users and independent experts responded to Scientigo’s claims with widespread skepticism and criticism. Some derided the company as a patent troll. Tim Bray described any claims that the patents covered XML as "ridiculous on the face of it".[32] Criticism Commentators have offered various critiques of XML, suggesting circumstances where XML provides both advantages and potential disadvantages.[33] Advantages • XML provides a basic syntax that can be used to share information between different kinds of computers, different applications, and different organizations. [4] XML data is stored in plain text format.[34] This software- and hardwareindependent way of storing data allows different incompatible systems to share data without needing to pass them through many layers of conversion. This also makes it easier to expand or upgrade to new operating systems, new 9 From Wikipedia, the free encyclopedia applications, or new browsers, without losing any data. • With XML, your data can be available to all kinds of "reading machines" (Handheld computers, voice machines, news feeds, etc), and make it more available for blind people, or people with other disabilities.[34] • XML provides a gateway for communication between applications, even applications on wildly different systems. As long as applications can share data (through HTTP, file sharing, or another mechanism), and have an XML parser, they can share structured information that is easily processed. Databases can trade tables, business applications can trade updates, and document systems can share information. [4] XML • Its predecessor, SGML, has been in use since 1986, so there is extensive experience and software available. Disadvantages • Difficult for the end-user to understand its capabilities. • XML syntax is redundant or large relative to binary representations of similar data,[35] especially with tabular data. • The redundancy may affect application efficiency through higher storage, transmission and processing costs.[36][37] • XML syntax is verbose, especially for human readers, relative to other alternative ’text-based’ data transmission formats.[38][39] • The hierarchical model for representation is limited in comparison to an object oriented graph.[40][41] • Expressing overlapping (non-hierarchical) node relationships requires extra effort.[42] • XML namespaces are problematic to use and namespace support can be difficult to correctly implement in an XML parser.[43] • XML is commonly depicted as "selfdocumenting" but this depiction ignores critical ambiguities.[44][45] • The distinction between content and attributes in XML seems unnatural to some and makes designing XML data structures harder.[46] • Transformations, even identity transforms, result in changes to format (whitespace, attribute ordering, attribute quoting, whitespace around attributes, newlines). These problems can make diff-ing the XML source very difficult except via Canonical XML. • Encourages non-relational data structures (data non-normalized) • It supports Unicode, allowing almost any information in any written human language to be communicated. • It can represent common computer science data structures: records, lists and trees. • Its self-documenting format describes structure and field names as well as specific values. • The strict syntax and parsing requirements make the necessary parsing algorithms extremely simple, efficient, and consistent. • Content-based XML markup enhances searchability, making it possible for agents and search engines to categorize data instead of wasting processing power on context-based full-text searches.[4] • XML is heavily used as a format for document storage and processing, both online and offline. • It is based on international standards. • It can be updated incrementally. • It allows validation using schema languages such as XSD and Schematron, which makes effective unit-testing, firewalls, acceptance testing, contractual specification and software construction easier. • The hierarchical structure is suitable for most (but not all) types of documents. • It is platform-independent, thus relatively immune to changes in technology. • Forward and backward compatibility are relatively easy to maintain despite changes in DTD or Schema. In business XBRL (eXtensible Business Reporting Language), which is based on XML, is widely used in the financial world. Due to increased demand for financial transparency, XBRL technology helps facilitate the processes of transferring data and reporting financial results. Notably, the SEC requires some filings in XBRL, [47] and Japanese banks and institutions run XBRL projects including mandatory filing.[48] 10 From Wikipedia, the free encyclopedia Web publishing uses XML to have a single source for creating and updating all content, which significantly saves time and reduces costs for companies when printing documents. In addition, some governments use XML for large documentation and printing maps, and airplane and car manufacturers may use XML technology to print maintenance booklets. XML encodings -- Part 1: Extensible Markup Language (XML) encoding ISO/IEC 22537:2006 Information technology -- ECMAScript for XML (E4X) specification ISO 22643:2003 Space data and information transfer systems -- Data entity dictionary specification language (DEDSL) -- XML/DTD Syntax ISO/IEC 23001-1:2006 Information technology -- MPEG systems technologies -- Part 1: Binary MPEG format for XML ISO 24531:2007 Intelligent transport systems -- System architecture, taxonomy and terminology -- Using XML in ITS standards, data registries and data dictionaries • • • Standards In addition to the ISO standards mentioned above, other related document include: • ISO/IEC 8825-4:2002 Information technology -- ASN.1 encoding rules: XML Encoding Rules (XER) • ISO/IEC 8825-5:2004 Information technology -- ASN.1 encoding rules: Mapping W3C XML schema definitions into ASN.1 • ISO/IEC 9075-14:2006 Information technology -- Database languages -- SQL -Part 14: XML-Related Specifications (SQL/ XML) • ISO 10303-28:2007 Industrial automation systems and integration -- Product data representation and exchange -- Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas • ISO/IEC 13250-3:2007 Information technology -- Topic Maps -- Part 3: XML syntax • ISO/IEC 13522-5:1997 Information technology -- Coding of multimedia and hypermedia information -- Part 5: Support for base-level interactive applications • ISO/IEC 13522-8:2001 Information technology -- Coding of multimedia and hypermedia information -- Part 8: XML notation for ISO/IEC 13522-5 • ISO/IEC 18056:2007 Information technology -- Telecommunications and information exchange between systems -XML Protocol for Computer Supported Telecommunications Applications (CSTA) Phase III • ISO/IEC 19503:2005 Information technology -- XML Metadata Interchange (XMI) • ISO/IEC 19776-1:2005 Information technology -- Computer graphics, image processing and environmental data representation -- Extensible 3D (X3D) • See also • • • • • • • Comparison of layout engines (XML) Binary XML Microsoft Office Open XML (OOXML) List of XML markup languages Document Object Model Category:XML-based standards S-expressions, an alternative from the 50s from which XML was inspired, which also can represent infinitely complex structure. Further reading • Annex A of ISO 8879:1986 (SGML) • Lawrence A. Cunningham (2005). "Language, Deals and Standards: The Future of XML Contracts". Washington University Law Review. SSRN 900616. Notes [1] Although it is not a mark-up language, itself, because it defines a syntax for markup languages without laying down a specific "vocabulary". [2] Bray, Tim; Jean Paoli, C. M. SperbergMcQueen, Eve Maler, François Yergeau (September 2006). "Extensible Markup Language (XML) 1.0 (Fourth Edition)Origin and Goals". World Wide Web Consortium. http://www.w3.org/TR/2006/ REC-xml-20060816/#sec-origin-goals. Retrieved on October 29 2006. [3] JSON , YAML, and S-Expressions are alternative text-based formats that are lighter-weight, less verbose than XML. See Critique of XML in this article. 11 From Wikipedia, the free encyclopedia [4] ^ St.Laurent, Simon (1998). "Why XML?". http://www.simonstl.com/ articles/whyxml.htm. Retrieved on January 23 2009. [5] Foster, Charles (2008). "XML Databases and XML information exchange". http://www.cfoster.net/articles/xmldbbusiness-case/. [6] XHTML attempts to simplify and improve the consistency of HTML, which is based on SGML. [7] "XML Attributes". W3Schools. http://www.w3schools.com/Xml/ xml_attributes.asp. [8] "Attributes [XML Standards"]. Microsoft. http://msdn.microsoft.com/en-us/library/ ms256152(VS.85).aspx. [9] The XML specification does not (by itself) indicate rules for formatting and layout. This is in contrast to the HTML specification (for example) which does indicate such rules. Nevertheless, some XML documents may indicate graphical layout, display or formatting based on some other specification. An example is SVG, which is a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML. [10] "Associating Style Sheets with XML documents, Version 1.0: W3C Recommendation". W3C. 29 June 1999. http://www.w3.org/TR/xml-stylesheet/. Retrieved on 2009-01-06. [11] "XSL Transformations (XSLT) Version 1.0: W3C Recommendation - Embedding Stylesheets". W3C. 16 November 1999. http://www.w3.org/TR/xslt#sectionEmbedding-Stylesheets. Retrieved on 2009-01-06. [12] xml-dev - Fw: An I-D for text/xml, application/xml, etc [13] Push, Pull, Next! by Bob DuCharme, at XML.com [14] Simplify XML processing with VTD-XML - Java World [15] http://www.ximpleware.com/wp_SUN.pdf [16] Cut, paste, split, and assemble XML documents with VTD-XML - Java World [17] VTD+XML format spec [18] Index XML documents with VTD-XML [19] http://java.sun.com/xml/jaxb/ [20] http://msdn.microsoft.com/en-us/library/ ms950721.aspx [21] http://www.liquid-technologies.com XML [22] http://www.artima.com/cppsource/ xml_data_binding.html [23] http://www.codesynthesis.com/products/ xsd/ [24] Bray, Tim (February 2005). "A conversation with Tim Bray: Searching for ways to tame the world’s vast stores of information". Association for Computing Machinery’s "Queue site". http://www.acmqueue.com/ modules.php?name=Content&pa=showpage&pid=28 Retrieved on April 16 2006. [25] edited by Sueann Ambron and Kristina Hooper ; foreword by John Sculley. (1988). "Publishers, multimedia, and interactivity". Interactive multimedia. Cobb Group. ISBN 1-55615-124-1. [26] The working group was originally called the "Editorial Review Board." The original members and seven who were added before the first edition was complete, are listed at the end of the first edition of the XML Recommendation, at http://www.w3.org/ TR/1998/REC-xml-19980210. [27] Reports From the W3C SGML ERB to the SGML WG And from the W3C XML ERB to the XML SIG [28] Extensible Markup Language (XML) [29] "Extensible Markup Language (XML) 1.1 (Second Edition) - Rationale and list of changes for XML 1.1". W3C. http://www.w3.org/TR/xml11/#secxml11. Retrieved on 2006-12-21. [30] Harold, Elliotte Rusty (2004). Effective XML. Addison-Wesley. pp. 10–19. ISBN 0321150406. http://www.cafeconleche.org/books/ effectivexml/. [31] Small company makes big claims on XML patents - CNET News.com [32] XML co-inventor Bray responds to patent assault | Between the Lines | ZDNet.com [33] (See e.g., XML-QL Proposal discussing XML benefits, When to use XML, "XML Sucks" on c2.com, Daring to Do Less with XML) [34] ^ How Can XML be Used? [35] Harold, Elliotte Rusty (2002). Processing XML with Java(tm): a guide to SAX, DOM, JDOM, JAXP, and TrAX. AddisonWesley. ISBN 0201771861. XML documents are too verbose compared with binary equivalents. [36] Harold, Elliotte Rusty (2002). XML in a Nutshell: A Desktop Quick Reference. 12 From Wikipedia, the free encyclopedia O’Reilly. ISBN 0596002920. XML documents are very verbose and searching is inefficient for highperformance largescale database applications. [37] However, the Binary XML effort strives to alleviate these problems by using a binary representation for the XML document. For example, the Java reference implementation of the Fast Infoset standard parsing speed is better by a factor 10 compared to Java Xerces, and by a factor 4 compared to the Piccolo driver, one of the fastest Javabased XML parser [1]. [38] Bierman, Gavin (2005). Database Programming Languages: 10th international symposium, DBPL 2005 Trondheim, Norway. Springer. ISBN 3540309519. XML syntax is too verbose for human readers in for certain applications. Proposes a dual syntax for human readability. [39] Although many purportedly "less verbose" text formats actually cite XML as both inspiration and prior art. See e.g., http://yaml.org/spec/current.html, http://innig.net/software/sweetxml/ index.html, http://www.json.org/ xml.html. [40] A hierarchical model only gives a fixed, monolithic view of the tree structure. For example, either actors under movies, or movies under actors, but not both. [41] Lim, Ee-Peng (2002). Digital Libraries: People, Knowledge, and Technology. Springer. ISBN 3540002618. Discusses some of the limitation with fixed hierarchy. Proceedings of the 5th International Conference on Asian Digital Libraries, ICADL 2002, held in Singapore in December 2002. [42] Searle, Leroy F. (2004). Voice, text, hypertext: emerging practices in textual studies. University of Washington Press. ISBN 0295983051. Proposes an alternative system for encoding overlapping elements. XML [43] (See e.g., http://www-128.ibm.com/ developerworks/library/x-abolns.html ) [44] "The Myth of Self-Describing XML" (PDF). http://www.oceaninformatics.biz/ publications/e2.pdf. Retrieved on 2007-05-12. [45] (See e.g., Use–mention distinction, Naming collision, Polysemy) [46] "Does XML Suck?". http://xmlsucks.org/ but_you_have_to_use_it_anyway/doesxml-suck.html. Retrieved on 2007-12-15. (See "8. Complexity: Attributes and Content") [47] "Investors Click Through to Salary Information With New Tool". The CRO Magazine. 2008-02-25. http://www.thecro.com/node/623. Retrieved on 2009-01-21. [48] "XBRL Planet - Country Overview". XBRL International www.xbrl.org. 2009-03-25. http://www.xbrlplanet.org/planet/ snapshot.php?iso3166=jp&feedID=28&gmapID=7. Retrieved on 2009-03-25. External links • W3C XML homepage • Introduction to Generalized Markup by Charles Goldfarb • Making Mistakes with XML by Sean Kelly • The Multilingual WWW by Gavin Nicol • Retrospective on Extended Reference Concrete Syntax by Rick Jelliffe • XML, Java and the Future of the Web by Jon Bosak • XML tutorials in w3schools • XML.gov • Thinking XML: The XML decade by Uche Ogbuji • XML: Ten year anniversary by Elliot Kimber • Closing Keynote, XML 2006 by Jon Bosak • Five years later, XML... by Simon St. Laurent • 23 XML fallacies to watch out for by Sean McGrath • W3C XML is Ten!, XML 10 years press release Retrieved from "http://en.wikipedia.org/wiki/XML" Categories: XML, Markup languages, World Wide Web Consortium standards, Technical communication, Bibliography file formats, Computer file formats, Open formats, Data modeling languages, Data serialization formats, Application layer protocols, Presentation layer protocols 13 From Wikipedia, the free encyclopedia XML This page was last modified on 21 May 2009, at 07:23 (UTC). All text is available under the terms of the GNU Free Documentation License. (See Copyrights for details.) Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a U.S. registered 501(c)(3) taxdeductible nonprofit charity. Privacy policy About Wikipedia Disclaimers 14