<?xml version="1.0" encoding="UTF-8"?>
<bibtex>
@misc{xml10fourth,
    author =    "Tim Bray and Jean Paoli and C. Michael Sperberg-McQueen and Eve Maler and Fran\c{c}ois Yergeau",
    title =     "Extensible Markup Language (XML) 1.0 (Fourth Edition)",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xml-20060816",
    month =     aug,
    year =      2006,
    uri =       "http://www.w3.org/TR/2006/REC-xml-20060816",
    abstract =  "The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML."
}

@misc{xml11sec,
    author =    "Tim Bray and Jean Paoli and C. Michael Sperberg-McQueen and Eve Maler and Fran\c{c}ois Yergeau and John Cowan",
    title =     "Extensible Markup Language (XML) 1.1 (Second Edition)",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xml11-20060816",
    month =     aug,
    year =      2006,
    uri =       "http://www.w3.org/TR/2006/REC-xml11-20060816",
    abstract =  "The Extensible Markup Language (XML) is a subset of SGML that is completely described in this document. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML."
}

@misc{xmlinfoset,
    author =    "John Cowan and Richard Tobin",
    title =     "XML Information Set (Second Edition)",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xml-infoset-20040204",
    month =     feb,
    year =      2004,
    uri =       "http://www.w3.org/TR/2004/REC-xml-infoset-20040204",
    abstract =  "This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document."
}

@misc{xinclude,
    author =    "Jonathan Marsh and David Orchard",
    title =     "XML Inclusions (XInclude) Version 1.0",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xinclude-20041220",
    month =     dec,
    year =      2004,
    abstract =  "This document specifies a processing model and syntax for general purpose inclusion. Inclusion is accomplished by merging a number of XML information sets into a single composite infoset. Specification of the XML documents (infosets) to be merged and control over the merging process is expressed in XML-friendly syntax (elements, attributes, URI references)."
}

@misc{xbase,
    author =    "Jonathan Marsh",
    title =     "XML Base",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xmlbase-20010627",
    month =     jun,
    year =      2001,
    abstract =  "This document proposes a facility, similar to that of HTML BASE, for defining base URIs for parts of XML documents."
}

@misc{css21,
    author =    "Bert Bos and Tantek \c{C}elik and Ian Hickson and H\r{a}kon Wium Lie",
    title =     "Cascading Style Sheets, level 2 revision 1: CSS 2.1 Specification",
    howpublished =  "World Wide Web Consortium, Working Draft WD-CSS21-20060411",
    month =     apr,
    year =      2006,
    uri =       "http://www.w3.org/TR/2006/WD-CSS21-20060411",
    abstract =  {This specification defines Cascading Style Sheets, level 2 revision 1 (CSS 2.1). CSS 2.1 is a style sheet language that allows authors and users to attach style (e.g., fonts and spacing) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS 2.1 simplifies Web authoring and site maintenance. CSS 2.1 builds on CSS2 which builds on CSS1. It supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. It also supports content positioning, table layout, features for internationalization and some properties related to user interface. CSS 2.1 corrects a few errors in CSS2 (the most important being a new definition of the height/width of absolutely positioned elements, more influence for HTML's "style" attribute and a new calculation of the 'clip' property), and adds a few highly requested features which have already been widely implemented. But most of all CSS 2.1 represents a "snapshot" of CSS usage: it consists of all CSS features that are implemented interoperably at the date of publication of the Recommendation. CSS 2.1 is derived from and is intended to replace CSS2. Some parts of CSS2 are unchanged in CSS 2.1, some parts have been altered, and some parts removed. The removed portions may be used in a future CSS3 specification. Future specs should refer to CSS 2.1 (unless they need features from CSS2 which have been dropped in CSS 2.1, and then they should only reference CSS2 for those features, or preferably reference such feature(s) in the respective CSS3 Module that includes those feature(s)).}
}

@misc{xmlns10sec,
    author =    "Tim Bray and Dave Hollander and Andrew Layman and Richard Tobin",
    title =     "Namespaces in XML 1.0 (Second Edition)",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xml-names-20060816",
    month =     aug,
    year =      2006,
    uri =       "http://www.w3.org/TR/2006/REC-xml-names-20060816",
    abstract =  "XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references."
}

@misc{xmlns11sec,
    author =    "Tim Bray and Dave Hollander and Andrew Layman and Richard Tobin",
    title =     "Namespaces in XML 1.1 (Second Edition)",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xml-names11-20060816",
    month =     aug,
    year =      2006,
    uri =       "http://www.w3.org/TR/2006/REC-xml-names11-20060816",
    abstract =  "XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by IRI references."
}

@misc{xpath,
    author =    "James Clark and Steven J. DeRose",
    title =     "XML Path Language (XPath) Version 1.0",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xpath-19991116",
    month =     nov,
    year =      1999,
    uri =       "http://www.w3.org/TR/1999/REC-xpath-19991116",
    abstract =  "XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer."
}

@misc{xslt,
    author =    "James Clark",
    title =     "XSL Transformations (XSLT) Version 1.0",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xslt-19991116",
    month =     nov,
    year =      1999,
    uri =       "http://www.w3.org/TR/1999/REC-xslt-19991116",
    abstract =  "This specification defines the syntax and semantics of XSLT, which is a language for transforming XML documents into other XML documents. XSLT is designed for use as part of XSL, which is a stylesheet language for XML. In addition to XSLT, XSL includes an XML vocabulary for specifying formatting. XSL specifies the styling of an XML document by using XSLT to describe how the document is transformed into another XML document that uses the formatting vocabulary. XSLT is also designed to be used independently of XSL. However, XSLT is not intended as a completely general-purpose XML transformation language. Rather it is designed primarily for the kinds of transformations that are needed when XSLT is used as part of XSL."
}

@misc{xmlschema1sec,
    author =    "Henry S. Thompson and David Beech and Murray Maloney and Noah Mendelsohn",
    title =     "XML Schema Part 1: Structures Second Edition",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xmlschema-1-20041028",
    month =     oct,
    year =      2004,
    uri =       "http://www.w3.org/TR/2004/REC-xmlschema-1-20041028",
    abstract =  "XML Schema: Structures specifies the XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML 1.0 documents, including those which exploit the XML Namespace facility. The schema language, which is itself represented in XML 1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type definitions (DTDs). This specification depends on XML Schema Part 2: Datatypes."
}

@misc{xmlschema2sec,
    author =    "Paul V. Biron and Ashok Malhotra",
    title =     "XML Schema Part 2: Datatypes Second Edition",
    howpublished =  "World Wide Web Consortium, Recommendation REC-xmlschema-2-20041028",
    month =     oct,
    year =      2004,
    uri =       "http://www.w3.org/TR/2004/REC-xmlschema-2-20041028",
    abstract =  "XML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes."
}

@misc{xml11schema10,
    author =    "Henry S. Thompson",
    title =     "Processing XML 1.1 Documents with XML Schema 1.0 Processors",
    howpublished =  "World Wide Web Consortium, Note NOTE-xml11schema10-20050511",
    month =     may,
    year =      2005,
    uri =       "http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511",
    abstract =  "XML Schema 1.0 did not anticipate new versions of XML, and mandated XML 1.0 documents as the starting point for schema-validity assessment. Some users and specifications would like to use XML Schema processors which process XML 1.1 documents, and some implementors of XML Schema processors would like to provide XML 1.1 support. This Note suggests an implementation strategy for implementors to adopt to enable users and specifications to get such support in a consistent way. All aspects of XML Schema which are liable to re-interpretation as a result of changes in XML 1.1 are discussed. An implementation of schema-validity assessment employing such a strategy is strictly speaking non-conformant to the current version of the XML Schema specification. The XML Schema WG none-the-less believes that interoperability will best be served by such non-conformant processors being made available to users, until such time as a subsequent version of XML Schema addressing this issue normatively is approved."
}
</bibtex>