Branch merge
authorGavin Carothers <gavin@carothers.name>
Tue, 15 May 2012 10:10:48 -0700
changeset 377 62a4ad20a3d3
parent 376 8a09ac3f5fe5 (current diff)
parent 374 36d5efae5e0a (diff)
child 378 42130d6eb777
Branch merge
rdf-concepts/Graph-ex.gif
rdf-layers/index.html
--- a/ReSpec.js/bibref/biblio.js	Wed May 02 07:19:20 2012 -0700
+++ b/ReSpec.js/bibref/biblio.js	Tue May 15 10:10:48 2012 -0700
@@ -11,6 +11,7 @@
    "EBNF-NOTATION" : "Tim Bray; Jean Paoli; C. M. Sperberg-McQueen; Eve Maler; François Yergeau. <a href=\"http://www.w3.org/TR/REC-xml/#sec-notation\"><cite>EBNF Notation</cite></a> 26 November 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-xml/#sec-notation\">http://www.w3.org/TR/REC-xml/#sec-notation</a> ",
    "N-TRIPLES" : "Jan Grant; Dave Beckett. <a href=\"http://www.w3.org/TR/rdf-testcases/#ntriples\"><cite>N-Triples</cite></a> 10 February 2004. W3C Recommendation. URL:  <a href=\"http://www.w3.org/TR/rdf-testcases/#ntriples\">http://www.w3.org/TR/rdf-testcases/#ntriples</a>",
 
+   "ABA-DSIG-GUIDELINES" : "<a href=\"http://www.signelec.com/content/download/digital_signature_guidelines.pdf\"><cite>Digital Signature Guidelines.</cite></a> 1 August 1996. Information Security Committee, American Bar Association. URL: <a href=\"http://www.signelec.com/content/download/digital_signature_guidelines.pdf\">http://www.signelec.com/content/download/digital_signature_guidelines.pdf</a>",
    "ABC" : "Leo Geurts; Lambert Meertens; Steven Pemberton. <a href=\"http://www.cwi.nl/~steven/abc\"><cite>The ABC Programmer's Handbook.</cite></a> Prentice-Hall. ISBN: 0-13-000027-2. URL: <a href=\"http://www.cwi.nl/~steven/abc\">http://www.cwi.nl/~steven/abc</a>",
    "ABNF" : "D. Crocker and P. Overell. <a href='http://www.ietf.org/rfc/rfc5234.txt'><cite>Augmented BNF for Syntax Specifications: ABNF.</cite></a> January 2008. Internet RFC 5234. URL: <a href='http://www.ietf.org/rfc/rfc5234.txt'>http://www.ietf.org/rfc/rfc5234.txt</a>",
    "ACCESS-CONTROL" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-access-control-20080912\"><cite>Access Control for Cross-Site Requests.</cite></a> 12 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-access-control-20080912\">http://www.w3.org/TR/2008/WD-access-control-20080912</a> ",
@@ -31,13 +32,19 @@
    "ATAG20" : "Jan Richards; Jutta Treviranus; Jeanne Spellman. <a href=\"http://www.w3.org/TR/2009/WD-ATAG20-20090217\"><cite>Authoring Tool Accessibility Guidelines (ATAG) 2.0.</cite></a> 17 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ATAG20-20090217\">http://www.w3.org/TR/2009/WD-ATAG20-20090217</a> ",
    "ATAG20-TECHS" : "Jan Richards; Jutta Treviranus; Tim Boland. <a href=\"http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310\"><cite>Implementation Techniques for Authoring Tool Accessibility Guidelines 2.0.</cite></a> 10 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310\">http://www.w3.org/TR/2008/WD-ATAG20-TECHS-20080310</a> ",
    "BACKPLANE" : "Steven Pemberton; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-backplane-20061116\"><cite>Rich Web Application Backplane.</cite></a> 16 November 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-backplane-20061116\">http://www.w3.org/TR/2006/NOTE-backplane-20061116</a> ",
+    "BBC-WP193" : "J.P. Barrett; M.E. Hammond; S.J.E Jolly. <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper193.shtml\"><cite>White Paper 193 : The Universal Control API version 0.6.0 - An Overview</cite></a>. June 2011. URL: <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper193.shtml\">http://www.bbc.co.uk/rd/publications/whitepaper193.shtml</a>",
+    "BBC-WP194" : "J.P. Barrett; M.E. Hammond; S.J.E Jolly. <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper194.shtml\"><cite>White Paper 194 : The Universal Control API v.0.6.0 - Specification for the behaviour of a universal control server running on a set-top box, and the clients that connect to it</cite></a>. June 2011. URL: <a href=\"http://www.bbc.co.uk/rd/publications/whitepaper194.shtml\">http://www.bbc.co.uk/rd/publications/whitepaper194.shtml</a>",
    "BCP47" : "A. Phillips; M. Davis. <a href=\"http://tools.ietf.org/html/bcp47\"><cite>Tags for Identifying Languages</cite></a> September 2009. IETF Best Current Practice. URL: <a href=\"http://tools.ietf.org/html/bcp47\">http://tools.ietf.org/html/bcp47</a> ",
    "BECSS" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2007/WD-becss-20071019\"><cite>Behavioral Extensions to CSS.</cite></a> 19 October 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-becss-20071019\">http://www.w3.org/TR/2007/WD-becss-20071019</a> ",
    "BLOB" :  "Arun Ranganathan. <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/#dfn-Blob\"><cite>Blob.</cite></a> 17 November 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/\">http://www.w3.org/TR/2009/WD-FileAPI-20091117/#dfn-Blob</a> ",
    "BONDI-ARCH-SECURITY-11" :  "<a href=\"http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf\"><cite>BONDI Architecture &amp; Security Requirements v1.1</cite></a> 27 January 2010. URL: <a href=\"http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf\">http://bondi.omtp.org/1.11/security/BONDI_Architecture_and_Security_v1.1.pdf</a> ",
    "BONDI-FEATURES1-11" :  "<a href=\"http://bondi.omtp.org/1.11/apis/apifeatures.html\"><cite>BONDI API Features v1.11</cite></a> 2 June 2010. URL: <a href=\"http://bondi.omtp.org/1.11/apis/apifeatures.html\">http://bondi.omtp.org/1.11/apis/apifeatures.html</a> ",
    "C14N-ISSUES" : "Konrad Lanz; Jos&#233; Kahan. <a href=\"http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220\"><cite>Known Issues with Canonical XML 1.0 (C14N/1.0).</cite></a> 20 December 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220\">http://www.w3.org/TR/2006/NOTE-C14N-issues-20061220</a> ",
+   "C14N2-TestCases"  : "Pratik Datta, Frederick Hirsch, <a href=\"http://www.w3.org/2008/xmlsec/Drafts/c14n-20/test-cases/\"><cite>Test Cases for Canonical XML 2.0</cite></a> 5 January 2012. W3C First Public Working Draft (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xml-c14n2-testcases-20120105/\">http://www.w3.org/TR/2012/WD-xml-c14n2-testcases-20120105/</a>",
    "CALL-CONTROL-REQS" : "Brad Porter. <a href=\"http://www.w3.org/TR/2001/WD-call-control-reqs-20010413\"><cite>Call Control Requirements in a Voice Browser Framework.</cite></a> 13 April 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-call-control-reqs-20010413\">http://www.w3.org/TR/2001/WD-call-control-reqs-20010413</a> ",
+    "CEA-2014" : "<a href=\"http://www.ce.org/Standards/browseByCommittee_2757.asp\"><cite>Web-based Protocol and Framework for Remote User Interface on UPnP Networks and the Internet (Web4CE)</cite></a>. January 2011. ANSI/CEA Standard. URL: <a href=\"http://www.ce.org/Standards/browseByCommittee_2757.asp\">http://www.ce.org/Standards/browseByCommittee_2757.asp</a>",
+    "CLABS-HNAPI": "<a href=\"http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf\"><cite>CableLabs Revised Home Networking API</cite></a>. 26 July 2011. Draft proposal. URL: <a href=\"http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf\">http://www.w3.org/2011/webtv/HNTF/CableLabs_Revised_API_20110727-2.pdf</a>",
+   "CANVAS-2D" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2dcontext/\"><cite>HTML Canvas 2D Context.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2dcontext/\">http://www.w3.org/TR/2dcontext/</a> ",
    "CC-ABOUT" : "<a href = 'http://creativecommons.org/about/licenses/'><cite>Creative Commons: About Licenses</cite></a> URL: http://creativecommons.org/about/licenses/ ",
    "CC-CHOOSE" : "<a href = 'http://creativecommons.org/choose/'><cite>Creative Commons: License Your Work</cite></a> URL: http://creativecommons.org/choose/ ",
    "CCPP" : "Franklin Reynolds; et al. <a href=\"http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115\"><cite>Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0.</cite></a> 15 January 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115\">http://www.w3.org/TR/2004/REC-CCPP-struct-vocab-20040115</a> ",
@@ -58,12 +65,12 @@
    "CHARSETS" : "<a href=\"http://www.iana.org/assignments/character-sets\"><cite>Characters sets.</cite></a> These are the official names for character sets that may be used in the Internet and may be referred to in Internet documentation URL: <a href=\"http://www.iana.org/assignments/character-sets\">http://www.iana.org/assignments/character-sets</a> ",
    "CLIPBOARD-APIS" : "Doug Schepers; Charles McCathieNevile. <a href=\"http://www.w3.org/TR/2006/WD-clipboard-apis-20061115\"><cite>Clipboard Operations for the Web 1.0: Copy, Paste, Drag and Drop.</cite></a> 15 November 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-clipboard-apis-20061115\">http://www.w3.org/TR/2006/WD-clipboard-apis-20061115</a> ",
    "CMS-Algorithms" : "R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3370.txt\"><cite>RFC3370: Cryptographic Message Syntax (CMS) Algorithms</cite></a>.  IETF Informational RFC, February 2002. URL: <a href=\"http://www.ietf.org/rfc/rfc3370.txt\">http://www.ietf.org/rfc/rfc3370.txt</a>",
-   "CMS-WRAP" : "R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3217.txt\"><cite>RFC3217: Triple-DES and RC2 Key Wrapping</cite></a>.  IETF Informational RFC, December 2001. URL: <a href=\"http://www.ietf.org/rfc/rfc3217.txt\">http://www.ietf.org/rfc/rfc3217.txt</a>",
+   "CMS-WRAP" : "R. Housley. <a href=\"http://www.ietf.org/rfc/rfc3217.txt\"><cite>RFC3217: Triple-DES and R2 Key Wrapping</cite></a>.  IETF Informational RFC, December 2001. URL: <a href=\"http://www.ietf.org/rfc/rfc3217.txt\">http://www.ietf.org/rfc/rfc3217.txt</a>",
    "COLORIMETRY" : "<cite>Colorimetry, Second Edition.</cite> CIE Publication 15.2-1986. ISBN 3-900-734-00-3",
    "CONTACTS-API" : "R. Tibbett. <a href=\"http://dev.w3.org/2009/dap/contacts/Overview.html\"><cite>Contacts API</cite></a>. 3rd August 2010. W3C Latest Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/contacts/Overview.html\">http://dev.w3.org/2009/dap/contacts/Overview.html</a> ",
    "CONTACTS-WRITER-API" : "R. Tibbett. <a href=\"http://dev.w3.org/2009/dap/contacts/Writer.html\"><cite>Contacts Writer API</cite></a>. 3rd August 2010. W3C Latest Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/contacts/Writer.html\">http://dev.w3.org/2009/dap/contacts/Writer.html</a> ",
    "CONTENT-IN-RDF" : "Carlos A Velasco; Johannes Koch. <a href=\"http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908\"><cite>Representing Content in RDF.</cite></a> 8 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908\">http://www.w3.org/TR/2008/WD-Content-in-RDF-20080908</a> ",
-   "COOKIES": "Adam Barth. <cite><a href=\"http://tools.ietf.org/html/draft-abarth-cookie\">HTTP State Management Mechanism</a>.</cite> IETF, November 2009",
+   "COOKIES": "Adam Barth. <cite><a href=\"http://www.rfc-editor.org/rfc/rfc6265.txt\">HTTP State Management Mechanism</a>.</cite> April 2011. Internet Proposed Standard RFC 6265. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc6265.txt\">http://www.rfc-editor.org/rfc/rfc6265.txt</a> ",
    "COOLURIS" : "Richard Cyganiak; Leo Sauermann. <a href=\"http://www.w3.org/TR/2008/NOTE-cooluris-20081203\"><cite>Cool URIs for the Semantic Web.</cite></a> 3 December 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-cooluris-20081203\">http://www.w3.org/TR/2008/NOTE-cooluris-20081203</a> ",
    "CORS" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2009/WD-cors-20090317\"><cite>Cross-Origin Resource Sharing.</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-cors-20090317\">http://www.w3.org/TR/2009/WD-cors-20090317</a> ",
    "CORE-DEVICE" : "Robin Berjon. <a href=\"http://dev.w3.org/2009/dap/device/\"><cite>Core Device Interfaces.</cite></a> 02 December 2009. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/device/\">http://dev.w3.org/2009/dap/device/</a> ",
@@ -78,24 +85,25 @@
    "CSS-PRINT" : "Melinda Grant. <a href=\"http://www.w3.org/TR/2006/WD-css-print-20061013\"><cite>CSS Print Profile.</cite></a> 13 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-css-print-20061013\">http://www.w3.org/TR/2006/WD-css-print-20061013</a> ",
    "CSS-TV" : "Sean Hayes; et al. <a href=\"http://www.w3.org/TR/2003/CR-css-tv-20030514\"><cite>CSS TV Profile 1.0.</cite></a> 14 May 2003. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/CR-css-tv-20030514\">http://www.w3.org/TR/2003/CR-css-tv-20030514</a> ",
    "CSS1" : "H&#229;kon Wium Lie; Bert Bos. <a href=\"http://www.w3.org/TR/2008/REC-CSS1-20080411\"><cite>Cascading Style Sheets (CSS1) Level 1 Specification.</cite></a> 11 April 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-CSS1-20080411\">http://www.w3.org/TR/2008/REC-CSS1-20080411</a> ",
-   "CSS2" : "Ian Jacobs; et al. <a href=\"http://www.w3.org/TR/2008/REC-CSS2-20080411\"><cite>Cascading Style Sheets, level 2 (CSS2) Specification.</cite></a> 11 April 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-CSS2-20080411\">http://www.w3.org/TR/2008/REC-CSS2-20080411</a> ",
-   "CSS21" : "Bert Bos; et al. <a href=\"http://www.w3.org/TR/2009/CR-CSS2-20090908/\"><cite>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 08 September 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-CSS2-20090908\">http://www.w3.org/TR/2009/CR-CSS2-20090908</a> ",
-   "CSS3-2D-TRANSFORMS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/2009/WD-css3-2d-transforms-20090320\"><cite>CSS 2D Transforms Module Level 3.</cite></a> 20 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-2d-transforms-20090320\">http://www.w3.org/TR/2009/WD-css3-2d-transforms-20090320</a> ",
-   "CSS3-3D-TRANSFORMS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/2009/WD-css3-3d-transforms-20090320\"><cite>CSS 3D Transforms Module Level 3.</cite></a> 20 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-3d-transforms-20090320\">http://www.w3.org/TR/2009/WD-css3-3d-transforms-20090320</a> ",
-   "CSS3-ANIMATIONS" : "Dean Jackson (Apple Inc); David Hyatt (Apple Inc); Chris Marrin (Apple Inc). <a href=\"http://www.w3.org/TR/2009/WD-css3-animations-20090320\"><cite>CSS Animations Module Level 3.</cite></a> 20 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-animations-20090320\">http://www.w3.org/TR/2009/WD-css3-animations-20090320</a> ",
+   "CSS2" : "Ian Jacobs; et al. <a href=\"http://www.w3.org/TR/CSS21/\"><cite>Cascading Style Sheets, level 2 (CSS2) Specification.</cite></a> 07 June 2011. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-CSS2-20080411\">http://www.w3.org/TR/2008/REC-CSS2-20080411</a> ",
+   "CSS21" : "Bert Bos; et al. <a href=\"http://www.w3.org/TR/CSS21/\"><cite>Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a>. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/CSS21\">http://www.w3.org/TR/CSS21/</a> ",
+   "CSS3-2D-TRANSFORMS" : "Simon Fraser; Dean Jackson; David Hyatt; Chris Marrin; Edward O'Connor. <a href=\"http://www.w3.org/TR/css3-2d-transforms/\"><cite>CSS 2D Transforms Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-2d-transforms/\">http://www.w3.org/TR/css3-2d-transforms/</a> ",
+   "CSS3-3D-TRANSFORMS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/css3-3d-transforms/\"><cite>CSS 3D Transforms Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-3d-transforms/\">http://www.w3.org/TR/css3-3d-transforms</a> ",
+   "CSS3-ANIMATIONS" : "Dean Jackson (Apple Inc); David Hyatt (Apple Inc); Chris Marrin (Apple Inc). <a href=\"http://www.w3.org/TR/css3-animations/\"><cite>CSS Animations Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-animations/\">http://www.w3.org/TR/css3-animations/</a> ",
    "CSS3-HYPERLINKS" : "Daniel Glazman; Bert Bos; Tantek &#199;elik. <a href=\"http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224\"><cite>CSS3 Hyperlink Presentation Module.</cite></a> 24 February 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224\">http://www.w3.org/TR/2004/WD-css3-hyperlinks-20040224</a> ",
    "CSS3-MARQUEE" : "Bert Bos. <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\"><cite>CSS Marquee Module Level 3.</cite></a> 5 December 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</a> ",
    "CSS3-PRESLEV" : "Ian Hickson; H&#229;kon Wium Lie. <a href=\"http://www.w3.org/TR/2003/WD-css3-preslev-20030813\"><cite>CSS3 module: Presentation Levels.</cite></a> 13 August 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-css3-preslev-20030813\">http://www.w3.org/TR/2003/WD-css3-preslev-20030813</a> ",
    "CSS3-READER" : "Bert Bos. <a href=\"http://www.w3.org/TR/2004/WD-css3-reader-20040224\"><cite>The CSS 'Reader' Media Type.</cite></a> 24 February 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-css3-reader-20040224\">http://www.w3.org/TR/2004/WD-css3-reader-20040224</a> ",
    "CSS3-TRANSITIONS" : "Dean Jackson; David Hyatt; Chris Marrin. <a href=\"http://www.w3.org/TR/2009/WD-css3-transitions-20090320\"><cite>CSS Transitions Module Level 3.</cite></a> 20 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-transitions-20090320\">http://www.w3.org/TR/2009/WD-css3-transitions-20090320</a> ",
    "CSS3-WEBFONTS" : "Michel Suignard; Chris Lilley. <a href=\"http://www.w3.org/TR/2002/WD-css3-webfonts-20020802\"><cite>CSS3 module: Web Fonts.</cite></a> 2 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-webfonts-20020802\">http://www.w3.org/TR/2002/WD-css3-webfonts-20020802</a> ",
-   "CSS3BG" : "Elika J. Etemad; Bert Bos. <a href=\"http://www.w3.org/TR/2008/WD-css3-background-20080910\"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> 10 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-css3-background-20080910\">http://www.w3.org/TR/2008/WD-css3-background-20080910</a> ",
+   "CSS3-BG" : "Elika J. Etemad; Bert Bos; Brad Kemper. <a href=\"http://www.w3.org/TR/css3-background/\"><cite>CSS Backgrounds and Borders Module Level 3.</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-background/\">http://www.w3.org/TR/css3-background/</a> ",
    "CSS3BORDER" : "Tapas Roy. <a href=\"http://www.w3.org/TR/2002/WD-css3-border-20021107\"><cite>CSS3 module: Border.</cite></a> 7 November 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-border-20021107\">http://www.w3.org/TR/2002/WD-css3-border-20021107</a> ",
    "CSS3BOX" : "Bert Bos. <a href=\"http://www.w3.org/TR/2007/WD-css3-box-20070809\"><cite>CSS basic box model.</cite></a> 9 August 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-box-20070809\">http://www.w3.org/TR/2007/WD-css3-box-20070809</a> ",
    "CSS3CASCADE" : "H&#229;kon Wium Lie. <a href=\"http://www.w3.org/TR/2005/WD-css3-cascade-20051215\"><cite>CSS3 module: Cascading and inheritance.</cite></a> 15 December 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-css3-cascade-20051215\">http://www.w3.org/TR/2005/WD-css3-cascade-20051215</a> ",
    "CSS3COL" : "H&#229;kon Wium Lie. <a href=\"http://www.w3.org/TR/2007/WD-css3-multicol-20070606\"><cite>CSS3 module: Multi-column layout.</cite></a> 6 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-multicol-20070606\">http://www.w3.org/TR/2007/WD-css3-multicol-20070606</a> ",
    "CSS3COLOR" : "Chris Lilley; Tantek &#199;elik; L. David Baron. <a href=\"http://www.w3.org/TR/2008/WD-css3-color-20080721\"><cite>CSS Color Module Level 3.</cite></a> 21 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-css3-color-20080721\">http://www.w3.org/TR/2008/WD-css3-color-20080721</a> ",
-   "CSS3FONT" : "Michel Suignard; Chris Lilley. <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\"><cite>CSS3 module: Fonts.</cite></a> 2 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\">http://www.w3.org/TR/2002/WD-css3-fonts-20020802</a> ",
+   "CSS3-FONTS" : "John Daggett (Mozilla). <a href=\"http://www.w3.org/TR/css3-fonts\"><cite>CSS Fonts Module Level 3</cite></a> URL: <a href=\"http://www.w3.org/TR/css3-fonts\">http://www.w3.org/TR/css3-fonts</a> ",
+   "CSS3-FONTS-20020802" : "Michel Suignard; Chris Lilley. <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\"><cite>CSS3 module: Fonts.</cite></a> 2 August 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-fonts-20020802\">http://www.w3.org/TR/2002/WD-css3-fonts-20020802</a> ",
    "CSS3GCPM" : "H&#229;kon Wium Lie. <a href=\"http://www.w3.org/TR/2007/WD-css3-gcpm-20070504\"><cite>CSS3 module: Generated Content for Paged Media.</cite></a> 4 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-gcpm-20070504\">http://www.w3.org/TR/2007/WD-css3-gcpm-20070504</a> ",
    "CSS3GENCON" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2003/WD-css3-content-20030514\"><cite>CSS3 Generated and Replaced Content Module.</cite></a> 14 May 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-css3-content-20030514\">http://www.w3.org/TR/2003/WD-css3-content-20030514</a> ",
    "CSS3GRID" : "Markus Mielke; Alex Mogilevsky. <a href=\"http://www.w3.org/TR/2007/WD-css3-grid-20070905\"><cite>CSS Grid Positioning Module Level 3.</cite></a> 5 September 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-css3-grid-20070905\">http://www.w3.org/TR/2007/WD-css3-grid-20070905</a> ",
@@ -104,6 +112,7 @@
    "CSS3LINE" : "Michel Suignard; Eric A. Meyer. <a href=\"http://www.w3.org/TR/2002/WD-css3-linebox-20020515\"><cite>CSS3 module: line.</cite></a> 15 May 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-linebox-20020515\">http://www.w3.org/TR/2002/WD-css3-linebox-20020515</a> ",
    "CSS3LIST" : "Ian Hickson; Tantek &#199;elik. <a href=\"http://www.w3.org/TR/2002/WD-css3-lists-20021107\"><cite>CSS3 module: Lists.</cite></a> 7 November 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css3-lists-20021107\">http://www.w3.org/TR/2002/WD-css3-lists-20021107</a> ",
    "CSS3MARQUEE" : "Bert Bos. <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\"><cite>CSS Marquee Module Level 3.</cite></a> 5 December 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-marquee-20081205\">http://www.w3.org/TR/2008/CR-css3-marquee-20081205</a> ",
+   "CSS3-MEDIAQUERIES" : "H. Lie, T. Çelik, D. Glazman, A. van Kesteren. <a href=\"http://www.w3.org/TR/css3-mediaqueries/\"><cite>Media Queries</cite></a>  URL: <a href=\"http://www.w3.org/TR/css3-mediaqueries/\">http://www.w3.org/TR/css3-mediaqueries/</a> ",
    "CSS3NAMESPACE" : "Anne van Kesteren; Elika J. Etemad. <a href=\"http://www.w3.org/TR/2008/CR-css3-namespace-20080523\"><cite>CSS Namespaces Module.</cite></a> 23 May 2008. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/CR-css3-namespace-20080523\">http://www.w3.org/TR/2008/CR-css3-namespace-20080523</a> ",
    "CSS3PAGE" : "Melinda Grant; H&#229;kon Wium Lie. <a href=\"http://www.w3.org/TR/2006/WD-css3-page-20061010\"><cite>CSS3 Module: Paged Media.</cite></a> 10 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-css3-page-20061010\">http://www.w3.org/TR/2006/WD-css3-page-20061010</a> ",
    "CSS3POS" : "Bert Bos. <cite>CSS3 Positioning Module.</cite> (forthcoming). W3C Working Draft. (Work in progress.)",
@@ -121,18 +130,18 @@
    "CSSSTYLEATTR" : "Marc Attinasi; Bert Bos; Tantek &#199;elik. <a href=\"http://www.w3.org/TR/2002/WD-css-style-attr-20020515\"><cite>Syntax of CSS rules in HTML's &quot;style&quot; attribute.</cite></a> 15 May 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-css-style-attr-20020515\">http://www.w3.org/TR/2002/WD-css-style-attr-20020515</a> ",
    "CT-GUIDELINES" : "Jo Rabin. <a href=\"http://www.w3.org/TR/2008/WD-ct-guidelines-20080801\"><cite>Content Transformation Guidelines 1.0.</cite></a> 1 August 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-ct-guidelines-20080801\">http://www.w3.org/TR/2008/WD-ct-guidelines-20080801</a> ",
    "CT-LANDSCAPE" : "Jo Rabin; Andrew Swainston. <a href=\"http://www.w3.org/TR/2007/WD-ct-landscape-20071025\"><cite>Content Transformation Landscape 1.0.</cite></a> 25 October 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-ct-landscape-20071025\">http://www.w3.org/TR/2007/WD-ct-landscape-20071025</a> ",
-   "CURIE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2010/WD-rdfa-core-20100422/\"><cite>RDFa Core 1.1 - Section 6.</cite></a> 22 April 2010. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2010/WD-rdfa-core-20100422/\">http://www.w3.org/TR/2010/WD-rdfa-core-20100422/</a> ",
+   "CURIE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\"><cite>RDFa Core 1.1 - Section 6.</cite></a> 8 May 2012. W3C proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-core-20120508/</a> ",
    "CVE-2009-0217" : "<a href=\"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217\"><cite>Common Vulnerabilities and Exposures List, CVE-2009-0217</cite></a> URL: <a href=\"http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217\"> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217</a>",
    "CX" : "Philippe Le H&#233;garet; et al. <a href=\"http://www.w3.org/TR/2001/NOTE-CX-20011211\"><cite>Component Extension (CX) API requirements Version 1.0.</cite></a> 11 December 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-CX-20011211\">http://www.w3.org/TR/2001/NOTE-CX-20011211</a> ",
    "DAHUT": "Robin Berjon; et al. <cite>The Dahut Specification Example From the Higher Circle.</cite> 15 March 1977. Lazy Daft. (Work for progress.) URL: <a href='http://berjon.com/'>http://berjon.com/</a>",
     "DAP-ACCESS-REQS" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\"><cite>Device API Access Control Requirements</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\">http://dev.w3.org/2009/dap/policy-reqs/</a> ",
     "DAP-POLICY-FRAMEWORK" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy/Framework.html\"><cite>Device API Policy Framework.</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy/Framework.html\">http://dev.w3.org/2009/dap/policy/Framework.html</a> ",
     "DAP-PRIVACY-POSITION" : "Frederick Hirsch, Robin Berjon. <a href=\"http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html\"><cite>Position Paper: Privacy and Policy in the DAP WG - A DAP Perspective</cite></a>. 2 September 2010. URL: <a href=\"http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html\">http://www.w3.org/2010/policy-ws/papers/14-Hirsch-Berjon-DAP.html</a> (<a href=\"http://www.w3.org/2010/policy-ws/\">W3C Workshop on Privacy and Data Usage Control</a>.)",
-    "DAP-PRIVACY-REQS" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/privacy-reqs/\"><cite>Device API Privacy Requirements</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/privacy-reqs/\">http://dev.w3.org/2009/dap/privacy-reqs/</a> ",
+    "DAP-PRIVACY-REQS" : "Alissa Cooper, Frederick Hirsch, John Morris. <a href=\"http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/\"><cite>Device API Privacy Requirements</cite></a> 29 June 2010. W3C Note URL: <a href=\"http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/\">http://www.w3.org/TR/2010/NOTE-dap-privacy-reqs-20100629/</a> ",
    "DAP-REQS" : "Robin Berjon; et al. <a href=\"http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/\"><cite>Device API Requirementsml</cite></a> 15 October 2009. Working Group Note. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/\">http://www.w3.org/TR/2009/NOTE-dap-api-reqs-20091015/</a> ",
     "DAP-XACML-POLICY-PROFILE" : "L. Arribas, P. Byers, M. Hanclik, F Hirsch, D. Rogers. <a href=\"http://dev.w3.org/2009/dap/policy/Profile.html\"><cite>XACML Policy Profile for Device APIs.</cite></a> 17 June 2010. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy/Profile.html\">http://dev.w3.org/2009/dap/policy/Profile.html</a> ",
    "Davis" : "<a href=\"http://www.usenix.org/publications/library/proceedings/usenix01/davis.html\"><cite>Defective Sign &amp; Encrypt in S/MIME, PKCS#7, MOSS, PEM, PGP, and XML.</cite></a> D. Davis. USENIX Annual Technical Conference. 2001. URL: <a href=\"http://www.usenix.org/publications/library/proceedings/usenix01/davis.html\">http://www.usenix.org/publications/library/proceedings/usenix01/davis.html</a>",
-   "DC11" : "Dublin Core metadata initiative. <a href=\"http://purl.oclc.org/docs/core/documents/rec-dces-19990702.htm\"><cite>Dublin Core metadata element set, version 1.1.</cite></a> July 1999. Dublin Core recommendation. URL: <a href=\"http://purl.oclc.org/docs/core/documents/rec-dces-19990702.htm\">http://purl.oclc.org/docs/core/documents/rec-dces-19990702.htm</a> ",
+   "DC11" : "Dublin Core metadata initiative. <a href=\"http://dublincore.org/documents/dcmi-terms/\"><cite>Dublin Core metadata element set, version 1.1.</cite></a> July 1999. Dublin Core recommendation. URL: <a href=\"http://dublincore.org/documents/dcmi-terms/\">http://dublincore.org/documents/dcmi-terms/</a> ",
    "DCONTOLOGY" : "Jos&#233; Manuel Cantera Fonseca; Rhys Lewis. <a href=\"http://www.w3.org/TR/2009/WD-dcontology-20090616\"><cite>Delivery Context Ontology.</cite></a> 16 June 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-dcontology-20090616/\">http://www.w3.org/TR/2009/WD-dcontology-20090616/</a> ",
    "DD-ECOSYSTEM" : "Rotan Hanrahan. <a href=\"http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031\"><cite>Device Description Ecosystem 1.0.</cite></a> 31 October 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031\">http://www.w3.org/TR/2007/NOTE-dd-ecosystem-20071031</a> ",
    "DD-LANDSCAPE" : "Matt Womer; Eman Nkeze; James Pearce. <a href=\"http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031\"><cite>Device Description Landscape 1.0.</cite></a> 31 October 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031\">http://www.w3.org/TR/2007/NOTE-dd-landscape-20071031</a> ",
@@ -149,7 +158,9 @@
    "DIAL" : "Kevin Smith. <a href=\"http://www.w3.org/TR/2007/WD-dial-20070727\"><cite>Device Independent Authoring Language (DIAL).</cite></a> 27 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-dial-20070727\">http://www.w3.org/TR/2007/WD-dial-20070727</a> ",
    "DIAL-PRIMER" : "Kevin Smith; Kevin Smith. <a href=\"http://www.w3.org/TR/2007/WD-dial-primer-20071101\"><cite>DIAL Part 0: Primer.</cite></a> 1 November 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-dial-primer-20071101\">http://www.w3.org/TR/2007/WD-dial-primer-20071101</a> ",
    "DIG2000" : "Digital Imaging Group. <a href=\"http://www.digitalimaging.org/pdf/wg1n1017.pdf\"><cite>DIG2000 file format proposal.</cite></a> Oct 1998. Report (draft) ISO/IEC JTC1/SG29/WG1 N1017. URL: <a href=\"http://www.digitalimaging.org/pdf/wg1n1017.pdf\">http://www.digitalimaging.org/pdf/wg1n1017.pdf</a> ",
+   "DISCO-PROP" : "Rich Tibbett, Clarke Stevens. <a href=\"http://people.opera.com/richt/release/specs/discovery/Overview.html\"><cite>Networked Service Discovery and Messaging</cite></a>. 22 September 2011. Draft proposal (no official standing). URL: <a href=\"http://people.opera.com/richt/release/specs/discovery/Overview.html\">http://people.opera.com/richt/release/specs/discovery/Overview.html</a>", 
    "DOM-BINDINGS" : "Cameron McCormack. <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\"><cite>Web IDL.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\">http://www.w3.org/TR/2008/WD-WebIDL-20081219</a> ",
+   "DOM4" : "Anne van Kesteren; Aryeh Gregor; Ms2ger. <a href=\"http://www.w3.org/TR/2012/WD-dom-20120105/\"><cite>DOM4.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-dom-20120105/\">http://www.w3.org/TR/2012/WD-dom-20120105/</a> ",
    "DOM-LEVEL-1" : "Vidur Apparao; et al. <a href=\"http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/\"><cite>Document Object Model (DOM) Level 1.</cite></a> 1 October 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/\">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/</a> ",
    "DOM-LEVEL-1-2e" : "Jonathan Robie; et al. <a href=\"http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929\"><cite>Document Object Model (DOM) Level 1 Specification (Second Edition).</cite></a> 29 September 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929\">http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929</a> ",
    "DOM-LEVEL-2-CORE" : "Arnaud Le Hors; et al. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/\"><cite>Document Object Model (DOM) Level 2 Core Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/</a> ",
@@ -160,7 +171,7 @@
    "DOM-LEVEL-2-VIEWS" : "Laurence Cable; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113\"><cite>Document Object Model (DOM) Level 2 Views Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113\">http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113</a> ",
    "DOM-LEVEL-3-AS" : "Ben Chang; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725\"><cite>Document Object Model (DOM) Level 3 Abstract Schemas Specification.</cite></a> 25 July 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725\">http://www.w3.org/TR/2002/NOTE-DOM-Level-3-AS-20020725</a> ",
    "DOM-LEVEL-3-CORE" : "Gavin Nicol; et al. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407\"><cite>Document Object Model (DOM) Level 3 Core Specification.</cite></a> 7 April 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407\">http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407</a> ",
-   "DOM-LEVEL-3-EVENTS" : "Bj&#246;rn H&#246;hrmann; Tom Pixley; Philippe Le H&#233;garet. <a href=\"http://www.w3.org/TR/2010/WD-DOM-Level-3-Events-20100907\"><cite>Document Object Model (DOM) Level 3 Events Specification.</cite></a> 7 September 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-DOM-Level-3-Events-20100907\">http://www.w3.org/TR/2010/WD-DOM-Level-3-Events-20100907</a> ",
+   "DOM-LEVEL-3-EVENTS" : "Bj&#246;rn H&#246;hrmann; Tom Pixley; Philippe Le H&#233;garet. <a href=\"http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/\"><cite>Document Object Model (DOM) Level 3 Events Specification.</cite></a> 31 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/\">http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/</a> ",
    "DOM-LEVEL-3-LS" : "Johnny Stenback; Andy Heninger. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407\"><cite>Document Object Model (DOM) Level 3 Load and Save Specification.</cite></a> 7 April 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407\">http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407</a> ",
    "DOM-LEVEL-3-VAL" : "Ben Chang; Rezaur Rahman; Joe Kesselman. <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127\"><cite>Document Object Model (DOM) Level 3 Validation Specification.</cite></a> 27 January 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127\">http://www.w3.org/TR/2004/REC-DOM-Level-3-Val-20040127</a> ",
    "DOM-LEVEL-3-VIEWS" : "Ray Whitmer. <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226\"><cite>Document Object Model (DOM) Level 3 Views and Formatting Specification.</cite></a> 26 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226\">http://www.w3.org/TR/2004/NOTE-DOM-Level-3-Views-20040226</a> ",
@@ -175,13 +186,14 @@
    "EBXML-MSG" : "Ian Jones; Brian Gibb; David Fischer. <a href=\"http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf\"><cite> OASIS ebXML Message Service Specification</cite></a> 1 April 2002. URL: <a href=\"http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf\">http://www.oasis-open.org/committees/download.php/272/ebMS_v2_0.pdf</a>",
     "ECC-ALGS" : "D. McGrew, K. Igoe, M. Salter. <a href=\"http://www.rfc-editor.org/rfc/rfc6090.txt\"><cite>RFC 6090: Fundamental Elliptic Curve Cryptography Algorithms.</cite></a> February 2011. IETF Informational RFC. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc6090.txt\">http://www.rfc-editor.org/rfc/rfc6090.txt</a>",   
    "EC-RELATED-ACTIVITIES" : "Thierry Michel. <a href=\"http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107\"><cite>W3C and Electronic Commerce.</cite></a> 7 January 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107\">http://www.w3.org/TR/2000/NOTE-EC-related-activities-20000107</a> ",
-   "ECMA-262" : "<a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\"><cite>ECMAScript Language Specification, Third Edition.</cite></a> December 1999. URL: <a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> ",
+   "ECMA-262" : "<a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\"><cite>ECMAScript Language Specification.</cite></a> December 1999. URL: <a href=\"http://www.ecma-international.org/publications/standards/Ecma-262.htm\">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a> ",
    "EGOV-IMPROVING" : "Kevin Novak; Jos&#233; M. Alonso. <a href=\"http://www.w3.org/TR/2009/WD-egov-improving-20090310\"><cite>Improving Access to Government through Better Use of the Web.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-egov-improving-20090310\">http://www.w3.org/TR/2009/WD-egov-improving-20090310</a> ",
    "ELEMENTTRAVERSAL" : "Robin Berjon; Doug Schepers. <a href=\"http://www.w3.org/TR/2008/REC-ElementTraversal-20081222\"><cite>Element Traversal Specification.</cite></a> 22 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-ElementTraversal-20081222\">http://www.w3.org/TR/2008/REC-ElementTraversal-20081222</a> ",
    "ELEMTYPO" : "Robert Bringhurst. <cite>The Elements of Typographic Style, Version 3.1.</cite> Hartley &amp; Marks. 2005. ISBN 0-88179-206-3.",
    "EMAIL": "P. Resnick. <a href='http://tools.ietf.org/html/rfc5322'><cite>RFC 5322: Internet Message Format</cite></a>. October 2008. IETF draft standard. URL: <a href='http://tools.ietf.org/html/rfc5322'>http://tools.ietf.org/html/rfc5322</a> ",
    "EMMA" : "Michael Johnston. <a href=\"http://www.w3.org/TR/2009/REC-emma-20090210\"><cite>EMMA: Extensible MultiModal Annotation markup language.</cite></a> 10 February 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-emma-20090210\">http://www.w3.org/TR/2009/REC-emma-20090210</a> ",
    "EMMAREQS" : "St&#233;phane H. Maes; Stephen Potter. <a href=\"http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113\"><cite>Requirements for EMMA.</cite></a> 13 January 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113\">http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113</a> ",
+    "ERICSSON-WDC" : "<a href=\"https://labs.ericsson.com/apis/web-device-connectivity/\"><cite>Web Device Connectivity</cite></a>. 18 October 2010. Ericsson Labs. URL: <a href=\"https://labs.ericsson.com/apis/web-device-connectivity/\"></a>",
    "ESDH" : "E. Rescorla. <a href=\"http://www.ietf.org/rfc/rfc2631.txt\"><cite> Diffie-Hellman Key Agreement Method.</cite></a>. IETF RFC 2631 Standards Track, 1999. URL: <a      href=\"http://www.ietf.org/rfc/rfc2631.txt\">http://www.ietf.org/rfc/rfc2631.txt</a>",
    "EXI" : "Takuki Kamiya; John Schneider. <a href=\"http://www.w3.org/TR/2009/CR-exi-20091208/\"><cite>Efficient XML Interchange (EXI) Format 1.0.</cite></a> 8 December 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-exi-20091208/\">http://www.w3.org/TR/2009/CR-exi-20091208/</a> ",
    "EXI-BEST-PRACTICES" : "Mike Cokus; Daniel Vogelheim. <a href=\"http://www.w3.org/TR/2007/WD-exi-best-practices-20071219\"><cite>Efficient XML Interchange (EXI) Best Practices.</cite></a> 19 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-best-practices-20071219\">http://www.w3.org/TR/2007/WD-exi-best-practices-20071219</a> ",
@@ -190,8 +202,8 @@
    "EXI-MEASUREMENTS" : "Jaakko Kangasharju; et al. <a href=\"http://www.w3.org/TR/2007/WD-exi-measurements-20070725\"><cite>Efficient XML Interchange Measurements Note.</cite></a> 25 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-measurements-20070725\">http://www.w3.org/TR/2007/WD-exi-measurements-20070725</a> ",
    "EXI-PRIMER" : "Daniel Peintner; Santiago Pericas-Geertsen. <a href=\"http://www.w3.org/TR/2007/WD-exi-primer-20071219\"><cite>Efficient XML Interchange (EXI) Primer.</cite></a> 19 December 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-exi-primer-20071219\">http://www.w3.org/TR/2007/WD-exi-primer-20071219</a> ",
    "FILE-UPLOAD" : "Robin Berjon. <a href=\"http://www.w3.org/TR/2006/WD-file-upload-20061018\"><cite>File Upload.</cite></a> 18 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-file-upload-20061018\">http://www.w3.org/TR/2006/WD-file-upload-20061018</a> ",
-   "FILE-API" :  "Arun Ranganathan. <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/\"><cite>File API.</cite></a> 17 November 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-FileAPI-20091117/\">http://www.w3.org/TR/2009/WD-FileAPI-20091117/</a> ",
-   "FILE-WRITER" :  "Eric Uhrhane. <a href=\"http://dev.w3.org/2009/dap/file-system/file-writer.html\"><cite>File Writer API.</cite></a> W3C Working Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/file-system/file-writer.html\">http://dev.w3.org/2009/dap/file-system/file-writer.html</a> ",
+   "FILE-API" :  "Arun Ranganathan; Jonas Sicking. <a href=\"http://www.w3.org/TR/2011/WD-FileAPI-20111020/\"><cite>File API.</cite></a> 20 October 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-FileAPI-20111020/\">http://www.w3.org/TR/2011/WD-FileAPI-20111020/</a> ",
+   "FILE-WRITER" :  "Eric Uhrhane. <a href=\"http://www.w3.org/TR/2011/WD-file-writer-api-20110419/\"><cite>File Writer API.</cite></a> 19 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-file-writer-api-20110419/\">http://www.w3.org/TR/2011/WD-file-writer-api-20110419/</a> ",
    "FIN-PRIV-NOTICE": "Kleimann Communications Group, Inc. <a href='http://www.ftc.gov/privacy/privacyinitiatives/ftcfinalreport060228.pdf'><cite>Evolution of a Prototype Financial Privacy Notice </cite></a> 28 February 2006. URL: http://www.ftc.gov/privacy/privacyinitiatives/ftcfinalreport060228.pdf ",
    "FIPS-180-3" : "<a href=\"http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf\"><cite>FIPS PUB 180-3 Secure Hash Standard</cite></a>.  U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf\">http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf</a>",
    "FIPS-186-3" : "<a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\"><cite>FIPS PUB 186-3:  Digital Signature Standard (DSS)</cite></a>. June 2009. U.S. Department of Commerce/National Institute of Standards and Technology. URL: <a href=\"http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf\">http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf</a>",
@@ -199,8 +211,11 @@
    "FLEX" : "<cite>Flex: The Lexical Scanner Generator.</cite> Version 2.3.7, ISBN 1882114213",
    "FLEXBOX" :  "L. David Baron. <a href=\"http://www.w3.org/TR/css3-flexbox/\"><cite>Flexible Box Layout Module.</cite></a> 23 July 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/css3-flexbox/\">http://www.w3.org/TR/css3-flexbox/</a> ",
    "FOAF" : "Dan Brickley, Libby Miller. <a href=\"http://xmlns.com/foaf/spec/\"><cite>FOAF Vocabulary Specification 0.98.</cite></a> 9 August 2010. URL: <a href=\"http://xmlns.com/foaf/spec/\">http://xmlns.com/foaf/spec/</a>",
+   "FULLSCREEN" : "Anne van Kesteren. <a href=\"http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html\"><cite>The Fullscreen API.</cite></a> 4 January 2012. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html\">http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html</a> ",
    "GEOLOCATION-API" : "Andrei Popescu. <a href=\"http://www.w3.org/TR/2008/WD-geolocation-API-20081222/\"><cite>Geolocation API Specification.</cite></a> 22 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-geolocation-API-20081222/\">http://www.w3.org/TR/2008/WD-geolocation-API-20081222/</a> ",
-   "GEOPRIV-ARCH" : "Barnes, R. Lepinski, M. Cooper, A. Morris, J. Tschofenig, H. Schulzrinne, H. <a href = 'http://tools.ietf.org/html/draft-ietf-geopriv-arch-01'><cite>An Architecture for Location and Location Privacy in Internet Applications</cite></a> 29 October 2009. URL: http://tools.ietf.org/html/draft-ietf-geopriv-arch-01 ",
+   "GEOPRIV-ARCH" : "Barnes, R. Lepinski, M. Cooper, A. Morris, J. Tschofenig, H. Schulzrinne, H. <a href = 'http://tools.ietf.org/html/draft-ietf-geopriv-arch-01'><cite>An Architecture for Location and Location Privacy in Internet Applications</cite></a> 29 October 2009. URL: <a href=\"http://tools.ietf.org/html/draft-ietf-geopriv-arch-01\">http://tools.ietf.org/html/draft-ietf-geopriv-arch-01</a>",
+    "GEOLOCATION-PRIVACY" : "Marcos Cáceres <a href=\"http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf\"><cite>Privacy of Geolocation Implementations</cite></a>, \"W3C Workshop on Privacy for Advanced Web APIs\" paper, 12/13 July 2010. URL: <a href=\"http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf\">http://www.w3.org/2010/api-privacy-ws/papers/privacy-ws-21.pdf</a>",
+    "GETUSERMEDIA": "D. Burnett, A. Narayanan. <a href=\"http://dev.w3.org/2011/webrtc/editor/getusermedia.html\"><cite>getusermedia: Getting access to local devices that can generate multimedia streams</cite></a> 22 December 2011. W3C Editors draft (Work in progress.) URL: <a href=\"http://dev.w3.org/2011/webrtc/editor/getusermedia.html\">http://dev.w3.org/2011/webrtc/editor/getusermedia.html</a> ",
    "GRDDL" : "Dan Connolly. <a href=\"http://www.w3.org/TR/2007/REC-grddl-20070911\"><cite>Gleaning Resource Descriptions from Dialects of Languages (GRDDL).</cite></a> 11 September 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-grddl-20070911\">http://www.w3.org/TR/2007/REC-grddl-20070911</a> ",
    "GRDDL-PRIMER" : "Harry Halpin; Ian Davis. <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628\"><cite>GRDDL Primer.</cite></a> 28 June 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628\">http://www.w3.org/TR/2007/NOTE-grddl-primer-20070628</a> ",
    "GRDDL-SCENARIOS" : "Fabien Gandon. <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406\"><cite>GRDDL Use Cases: Scenarios of extracting RDF data from XML documents.</cite></a> 6 April 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406\">http://www.w3.org/TR/2007/NOTE-grddl-scenarios-20070406</a> ",
@@ -218,7 +233,7 @@
    "HTML40" : "Ian Jacobs; David Raggett; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/1998/REC-html40-19980424\"><cite>HTML 4.0 Specification.</cite></a> 24 April 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-html40-19980424\">http://www.w3.org/TR/1998/REC-html40-19980424</a> ",
    "HTML40-MOBILE" : "Shin'ichi Matsui; et al. <a href=\"http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315\"><cite>HTML 4.0 Guidelines for Mobile Access.</cite></a> 15 March 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315\">http://www.w3.org/TR/1999/NOTE-html40-mobile-19990315</a> ",
    "HTML401" : "David Raggett; Ian Jacobs; Arnaud Le Hors. <a href=\"http://www.w3.org/TR/1999/REC-html401-19991224\"><cite>HTML 4.01 Specification.</cite></a> 24 December 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-html401-19991224\">http://www.w3.org/TR/1999/REC-html401-19991224</a> ",
-   "HTML5" : "Ian Hickson. <a href=\"http://dev.w3.org/html5/spec/Overview.html\"><cite>HTML 5.</cite></a> 23 September 2011. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/spec/Overview.html\">http://dev.w3.org/html5/spec/Overview.html</a> ",
+   "HTML5" : "Ian Hickson; David Hyatt. <a href=\"http://www.w3.org/TR/html5\"><cite>HTML5.</cite></a> 25 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/html5\">http://www.w3.org/TR/html5</a> ",
    "HTML5-DIFF" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2009/WD-html5-diff-20090212\"><cite>HTML 5 differences from HTML 4.</cite></a> 12 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-html5-diff-20090212\">http://www.w3.org/TR/2009/WD-html5-diff-20090212</a> ",
    "HTML5-PUBNOTES" : "Michael Smith. <a href=\"http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610\"><cite>HTML 5 Publication Notes.</cite></a> 10 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610\">http://www.w3.org/TR/2008/NOTE-html5-pubnotes-20080610</a> ",
    "HTML-DEVICE" : "Ian Hickson. <a href=\"http://dev.w3.org/html5/html-device/\"><cite>HTML Device</cite></a> 9th September 2010. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/html5/html-device/\">http://dev.w3.org/html5/html-device/</a>",
@@ -228,15 +243,20 @@
    "HTTP11" : "R. Fielding; et al. <a href=\"http://www.ietf.org/rfc/rfc2616.txt\"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a> June 1999. Internet RFC 2616. URL: <a href=\"http://www.ietf.org/rfc/rfc2616.txt\">http://www.ietf.org/rfc/rfc2616.txt</a> ",
    "HTTP-TLS" : "E. Rescorla. <a href=\"http://www.ietf.org/rfc/rfc2818.txt\"><cite>HTTP Over TLS.</cite></a> May 2000. Internet RFC 2818. URL: <a href=\"http://www.ietf.org/rfc/rfc2818.txt\">http://www.ietf.org/rfc/rfc2818.txt</a> ",
    "HunterZhan" : "Hunter, Jane; Zhan, Zhimin. <a href=\"http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html\">&ldquo;An Indexing and Querying System for Online Images Based on the PNG Format and Embedded Metadata&rdquo;</a> in: <cite>ARLIS/ANZ Conference.</cite> Sep 1999. Brisbane, Australia. URL: <a href=\"http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html\">http://archive.dstc.edu.au/RDU/staff/jane-hunter/PNG/paper.html</a> ",
+   "HTML-RDFA" : "Manu Sporny; et al. <a href=\"http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/\"><cite>HTML+RDFa 1.1</cite></a> 25 May 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/\">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/</a> ",
    "I18N-GUIDE-FRAMEWORK" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417\"><cite>Framework Document for i18n Guidelines 1.0.</cite></a> 17 April 2003. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417\">http://www.w3.org/TR/2003/WD-i18n-guide-framework-20030417</a> ",
    "ID-MGM" : "Rundle, M. <a href = 'http://identityproject.lse.ac.uk/mary.pdf'><cite>International Data Protection and Digitial Identity Management Tools</cite></a> Internet Governance Forum 2006 - Athens, Privacy Workshop I. 31 October 2006. URL: http://identityproject.lse.ac.uk/mary.pdf ",
    "IEEE1363" : "<a href=\"http://grouper.ieee.org/groups/1363/\"><cite>IEEE 1363: Standard Specifications for Public Key Cryptography</cite></a>. August 2000.  URL: <a href=\"http://grouper.ieee.org/groups/1363/\">http://grouper.ieee.org/groups/1363/</a>",
+    "IEEE1588" : "<a href=\"http://grouper.ieee.org/groups/1588/\"><cite>IEEE 1588-2008: A Precision Clock Synchronization Protocol for Networked Measurement and Control Systems</cite></a>. 24 July 2008. URL: <a href=\"http://grouper.ieee.org/groups/1588/\">http://grouper.ieee.org/groups/1588/</a>",
+    "IEEE802-1AS" : "Geoff Garner. <a href=\"http://ieee802.org/1/pages/802.1as.html\"><cite>IEEE 802.1AS - Timing and Synchronization</cite></a>. 30 March 2011. IEEE Standard. URL: <a href=\"http://ieee802.org/1/pages/802.1as.html\">http://ieee802.org/1/pages/802.1as.html</a>",
    "IEEE802-3" : "<cite>IEEE 802.3: Carrier sense multiple access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications</cite>. December 2008.",
    "I18N-HTML-TECH-BIDI" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606\"><cite>Internationalization Best Practices: Handling Right-to-left Scripts in XHTML and HTML Content.</cite></a> 6 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606\">http://www.w3.org/TR/2007/WD-i18n-html-tech-bidi-20070606</a> ",
    "I18N-HTML-TECH-CHAR" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509\"><cite>Authoring Techniques for XHTML &amp; HTML Internationalization: Characters and Encodings 1.0.</cite></a> 9 May 2004. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509\">http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509</a> ",
    "I18N-HTML-TECH-LANG" : "Richard Ishida. <a href=\"http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412\"><cite>Internationalization Best Practices: Specifying Language in XHTML &amp; HTML Content.</cite></a> 12 April 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412\">http://www.w3.org/TR/2007/NOTE-i18n-html-tech-lang-20070412</a> ",
+   "IANA-TSV" : "Paul Lindner. <a href=\"http://www.iana.org/assignments/media-types/text/tab-separated-values\"><cite>Definition of tab-separated-values (tsv)</cite></a> June 1993. IANA Media Type Registration. URL: <a href=\"http://www.iana.org/assignments/media-types/text/tab-separated-values\">http://www.iana.org/assignments/media-types/text/tab-separated-values</a>",
    "ICC32" : "<a href=\"http://www.color.org/icc32.pdf\"><cite>ICC Profile Format Specification, version 3.2.</cite></a> 1995. URL: <a href=\"http://www.color.org/icc32.pdf\">http://www.color.org/icc32.pdf</a>",
    "ICC42" : "<a href=\"http://color.org/ICC1v42_2006-05.pdf\"><cite>Image technology colour management &#8212; Architecture, profile format, and data structure.</cite></a> International Color Consortium. Specification ICC.1:2004-10 (Profile version 4.2.0.0) With errata incorporated, 5/22/2006. URL: <a href=\"http://color.org/ICC1v42_2006-05.pdf\">http://color.org/ICC1v42_2006-05.pdf</a> ",
+   "ICE" : "J. Rosenberg. <a href=\"http://tools.ietf.org/html/rfc5245\"><cite>Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols.</cite></a> April 2010. Internet RFC 5245. URL: <a href=\"http://tools.ietf.org/html/rfc5245\">http://tools.ietf.org/html/rfc5245</a>",
    "ILU-REQUESTOR" : "Paul Everitt. <a href=\"http://www.w3.org/TR/WD-ilu-requestor-960307\"><cite>The ILU Requester: Object Services in HTTP Servers.</cite></a> 7 March 1996. W3C Note. URL: <a href=\"http://www.w3.org/TR/WD-ilu-requestor-960307\">http://www.w3.org/TR/WD-ilu-requestor-960307</a> ",
    "IMAGEMAP" : "Ian Graham. <a href=\"http://www.w3.org/TR/NOTE-imagemap\"><cite>Imagemapped Images and Image-Incapable User Agents.</cite></a> 27 November 1996. W3C Note. URL: <a href=\"http://www.w3.org/TR/NOTE-imagemap\">http://www.w3.org/TR/NOTE-imagemap</a> ",
    "INKML" : "Stephen M. Watt; Max Froumentin; Yi-Min Chee. <a href=\"http://www.w3.org/TR/2006/WD-InkML-20061023\"><cite>Ink Markup Language (InkML).</cite></a> 23 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-InkML-20061023\">http://www.w3.org/TR/2006/WD-InkML-20061023</a> ",
@@ -259,6 +279,7 @@
    "JPEG" : "Hamilton, Eric. <a href=\"http://www.w3.org/Graphics/JPEG/jfif3.pdf\"><cite>JPEG File Interchange Format.</cite></a> Sep 1992. URL: <a href=\"http://www.w3.org/Graphics/JPEG/jfif3.pdf\">http://www.w3.org/Graphics/JPEG/jfif3.pdf</a> C-Cube Microsystems. Milpitas, CA, USA.",
    "JPEG2000" : "Joint Photographers Expert Group (JPEG). <a href=\"http://www.jpeg.org/cd15444-1.pdf\"><cite>Jpeg 2000 image coding system.</cite></a> 9 Dec 1999. Report (draft) ISO/IEC CD15444-1:1999. URL: <a href=\"http://www.jpeg.org/cd15444-1.pdf\">http://www.jpeg.org/cd15444-1.pdf</a> ",
    "JSON-LD" : "Manu Sporny, et al. <a href=\"http://json-ld.org/spec/latest/\"><cite>JSON-LD - Linked Data Expression in JSON</cite></a> 15 October 2010. Unofficial Draft. URL: <a href=\"http://json-ld.org/spec/latest/\">http://json-ld.org/spec/latest/</a> ",
+   "KnowPrivacy" : "Joshua Gomez; Travis Pinnick; Ashkan Soltani. <a href=\"http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf\"><cite>KnowPrivacy.</cite></a> 1 June 2009. URL: <a href=\"http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf\">http://www.knowprivacy.org/report/KnowPrivacy_Final_Report.pdf</a> ",
    "KUIL" : "Kormann, Thierry. <a href=\"http://www.inria.fr/koala/kuil/index.html\"><cite>KUIL, the Koala User Interface Language.</cite></a> Sep 1999. Software package URL: <a href=\"http://www.inria.fr/koala/kuil/index.html\">http://www.inria.fr/koala/kuil/index.html</a> ",
    "LANGCULTTYPE" : "John D. Berry, Ed. <cite>Language Culture Type.</cite> Graphis. 2001. ISBN 1-932026-01-0.",
    "LBASE" : "Ramanathan V. Guha; Patrick Hayes. <a href=\"http://www.w3.org/TR/2003/NOTE-lbase-20031010\"><cite>LBase: Semantics for Languages of the Semantic Web.</cite></a> 10 October 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-lbase-20031010\">http://www.w3.org/TR/2003/NOTE-lbase-20031010</a> ",
@@ -275,15 +296,17 @@
    "MATHML2" : "Nico Poppelier; et al. <a href=\"http://www.w3.org/TR/2003/REC-MathML2-20031021\"><cite>Mathematical Markup Language (MathML) Version 2.0 (Second Edition).</cite></a> 21 October 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-MathML2-20031021\">http://www.w3.org/TR/2003/REC-MathML2-20031021</a> ",
    "MATHML3" : "Patrick Ion; David Carlisle; Robert Miner. <a href=\"http://www.w3.org/TR/2008/WD-MathML3-20081117\"><cite>Mathematical Markup Language (MathML) Version 3.0.</cite></a> 17 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-MathML3-20081117\">http://www.w3.org/TR/2008/WD-MathML3-20081117</a> ",
    "MCINTOSH-WRAP" : " Michael McIntosh; Paula Austel. <cite>XML signature element wrapping attacks and countermeasures.</cite> In Workshop on Secure Web Services, 2005",
-   "MEDIA-ANNOT-REQS" : "WonSuk Lee; Felix Sasaki; Tobias B&#252;rger. <a href=\"http://www.w3.org/TR/2009/WD-media-annot-reqs-20090119\"><cite>Use Cases and Requirements for Ontology and API for Media Object 1.0.</cite></a> 19 January 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-media-annot-reqs-20090119\">http://www.w3.org/TR/2009/WD-media-annot-reqs-20090119</a> ",
+   "MDN-SETCAPTURE" : "Shepherd, Eric; et. al. <a href='https://developer.mozilla.org/en/DOM/element.setCapture'><cite>element.setCapture</cite></a> 12 Nov 2010. Mozilla Developer Network. URL: <a href='https://developer.mozilla.org/en/DOM/element.setCapture'>https://developer.mozilla.org/en/DOM/element.setCapture</a>",
+   "MEDIA-ANNOT-REQS" : "WonSuk Lee; Felix Sasaki; Tobias B&#252;rger; V&eacute;ronique Malais&eacute;. <a href=\"http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/\"><cite>Use Cases and Requirements for Ontology and API for Media Object 1.0.</cite></a>W3C Working Draft 21 January 2010. URL: <a href=\"http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/\">http://www.w3.org/TR/2010/WD-media-annot-reqs-20100121/</a> ",
    "MEDIA-FRAGMENT" : "R. Troncy; E. Mannens; Silvia Pfeiffer and Davy Van Deursen. <a href=\"http://www.w3.org/TR/2010/WD-media-frags-20100624\"><cite>Media Fragments URI 1.0.</cite></a> 18 November 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/WD-media-frags-20100624\">http://www.w3.org/TR/2010/WD-media-frags-20100624</a> ",
+   "MEDIA-FRAGMENTS" : "Raphael Troncy; Erik Mannens; Silvia Pfeiffer and Davy Van Deursen. <a href=\"http://www.w3.org/TR/2011/WD-media-frags-20110317/\"><cite>Media Fragments URI 1.0</a>. W3C Working Draft 17 March 2011.</cite> URL: <a href=\"http://www.w3.org/TR/2011/WD-media-frags-20110317/\">http://www.w3.org/TR/2011/WD-media-frags-20110317/</a> ",
    "MEDIAACCESSEVENTS" : "Ola Andersson; Jean-Claude Dufourd; Roland Lundblad. <a href=\"http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013\"><cite>Media Access Events.</cite></a> 13 October 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013\">http://www.w3.org/TR/2006/WD-MediaAccessEvents-20061013</a> ",
    "MEDIACAPTURE-API": "Dzung D Tran; Ilkka Oksanen; Ingmar Kliche. <a href='http://dev.w3.org/2009/dap/camera/Overview-API.html'><cite>The Media Capture API</cite></a> 3 September 2010. W3C Editors Draft. (Work in progress.) URL: <a href='http://dev.w3.org/2009/dap/camera/Overview-API.html'>http://dev.w3.org/2009/dap/camera/Overview-API.html</a> ",
    "MEDIAONT-API": "WonSuk Lee; Florian Stegmaier; Chris Poppe. <a href=\"http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608\"><cite>API for Media Resource 1.0.</cite></a> 8 June 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608\">http://www.w3.org/TR/2010/WD-mediaont-api-1.0-20100608</a> ",
-   "MEDIAQ" : "Håkon Wium Lie; et al. <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\"><cite>Media Queries.</cite></a> 15 September 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\">http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/</a> ",
+   "MEDIAQ" : "Håkon Wium Lie; et al. <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\"><cite>Media Queries.</cite></a>. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/\">http://www.w3.org/TR/2009/CR-css3-mediaqueries-20090915/</a> ",
    "MESSAGING-API": "Suresh Chitturi, Daniel Coloma, Max Froumentin, Maria Angeles Oteo, Niklas Widell. <a href='http://dev.w3.org/2009/dap/messaging/'><cite>The Messaging API.</cite></a> 23 August 2010. W3C Editors' Draft. (Work in progress.) URL: <a href='http://dev.w3.org/2009/dap/messaging/'>http://dev.w3.org/2009/dap/messaging/</a>",
    "MICROFORMATS" : "<a href='http://microformats.org'><cite>Microformats</cite></a>. URL: <a href='http://microformats.org'>http://microformats.org</a> ",
-   "MIME-REG" : "N. Freed, J. Klensin, J. Postel. <a href=\"http://www.ietf.org/rfc/rfc2048.txt\"><cite>RFC 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</cite></a>. November 1996. Best Current Practice. URL: <a href=\"http://www.ietf.org/rfc/rfc2048.txt\">http://www.ietf.org/rfc/rfc2048.txt</a>",
+   "MIME-REG" : "N. Freed, J. Klensin. <a href=\"http://www.ietf.org/rfc/rfc4289.txt\"><cite>RFC 4289: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures</cite></a>. December 2005. Best Current Practice. URL: <a href=\"http://www.ietf.org/rfc/rfc4289.txt\">http://www.ietf.org/rfc/rfc4289.txt</a>",
    "MMI-ARCH" : "Jim Barnett. <a href=\"http://www.w3.org/TR/2008/WD-mmi-arch-20081016\"><cite>Multimodal Architecture and Interfaces.</cite></a> 16 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mmi-arch-20081016\">http://www.w3.org/TR/2008/WD-mmi-arch-20081016</a> ",
    "MMI-AUTH" : "Ingmar Kliche. <a href=\"http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702\"><cite>Authoring Applications for the Multimodal Architecture.</cite></a> 2 July 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702\">http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702</a> ",
    "MMI-DEV-FEEDBACK" : "Gerald McCobb; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414\"><cite>Multimodal Application Developer Feedback.</cite></a> 14 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414\">http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414</a> ",
@@ -297,8 +320,9 @@
    "MOBILEOK-BASIC10-TESTS" : "Jo Rabin; Sean Owen. <a href=\"http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208\"><cite>W3C mobileOK Basic Tests 1.0.</cite></a> 8 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208\">http://www.w3.org/TR/2008/REC-mobileOK-basic10-tests-20081208</a> ",
    "MODALITY-INTERFACE" : "Brad Porter. <a href=\"http://www.w3.org/TR/2004/NOTE-modality-interface-20040510\"><cite>Modality Component to Host Environment DOM Requirements and Capabilities Assessment.</cite></a> 10 May 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-modality-interface-20040510\">http://www.w3.org/TR/2004/NOTE-modality-interface-20040510</a> ",
    "MOZ-ICONS" : "Martin, J. Raskin, A. Gelman, L. Rood, D. Surman, M. Hadfield, G. Greant, Z. <a href = 'https://wiki.mozilla.org/Drumbeat/Challenges/Privacy_Icons'<cite>Privacy Icons</cite></a> 6 March 2010. Mozilla Wiki. URL: https://wiki.mozilla.org/Drumbeat/Challenges/Privacy_Icons ",
+   "MRCPv2" : "Burnett, D. Shanmugham, S. <a href = 'http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27'><cite>Media Resource Control Protocol Version 2</cite></a> 15 November 2011. URL: <a href=\"http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27\">http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-27</a>",
    "MULTIMODAL-REQS" : "Marianne Hickey. <a href=\"http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710\"><cite>Multimodal Requirements for Voice Markup Languages.</cite></a> 10 July 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710\">http://www.w3.org/TR/2000/WD-multimodal-reqs-20000710</a> ",
-   "MWABP" : "Adam Connors; Bryan Sullivan. <a href=\"http://www.w3.org/TR/2008/WD-mwabp-20081222\"><cite>Mobile Web Application Best Practices.</cite></a> 22 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mwabp-20081222\">http://www.w3.org/TR/2008/WD-mwabp-20081222</a> ",
+   "MWABP" : "Adam Connors; Bryan Sullivan. <a href=\"http://www.w3.org/TR/2010/REC-mwabp-20101214/\">Mobile Web Application Best Practices.</cite></a> 14 December 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-mwabp-20101214/\">http://www.w3.org/TR/2010/REC-mwabp-20101214/</a> ",
    "MWBP-WCAG" : "Yeliz Yesilada; Alan Chuter. <a href=\"http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703\"><cite>Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG).</cite></a> 3 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703\">http://www.w3.org/TR/2008/WD-mwbp-wcag-20080703</a> ",
    "NAMES" : "Lilley, Chris. <a href=\"http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html\"><cite>Restrictions on identifiers.</cite></a> (forthcoming). W3C Note. URL: <a href=\"http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html\">http://lists.w3.org/Archives/Member/w3c-ui-tech/2001Mar/0002.html</a> ",
    "NAMESPACESTATE" : "Norman Walsh. <a href=\"http://www.w3.org/TR/2006/WD-namespaceState-20060329\"><cite>The Disposition of Names in an XML Namespace.</cite></a> 29 March 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-namespaceState-20060329\">http://www.w3.org/TR/2006/WD-namespaceState-20060329</a> ",
@@ -309,13 +333,22 @@
    "NL-SPEC" : "Deborah A. Dahl. <a href=\"http://www.w3.org/TR/2000/WD-nl-spec-20001120\"><cite>Natural Language Semantics Markup Language for the Speech Interface Framework.</cite></a> 20 November 2000. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2000/WD-nl-spec-20001120\">http://www.w3.org/TR/2000/WD-nl-spec-20001120</a> ",
    "NOTE-CCPP" : "Franklin Reynolds; et al. <a href=\"http://www.w3.org/1999/07/NOTE-CCPP-19990727\"><cite>Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation.</cite></a> 27 July 1999. W3C Note. URL: <a href=\"http://www.w3.org/1999/07/NOTE-CCPP-19990727\">http://www.w3.org/1999/07/NOTE-CCPP-19990727</a> ",
     "N3" : "Tim Berners-Lee; Dan Connolly. <a href=\"http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/\"><cite>Notation3 (N3): A readable RDF syntax.</cite></a> 14 January 2008. W3C Team Submission. URL: <a href=\"http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/\">http://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/</a> ",
+    "NTP"  :    "D. Mills. <a href=\"http://www.ietf.org/rfc/rfc1305.txt\"><cite>Network Time Protocol (Version 3)</cite></a>. March 1992. IETF RFC 1305. URL: <a href=\"http://www.ietf.org/rfc/rfc1305.txt\">http://www.ietf.org/rfc/rfc1305.txt</a>",
+    "OAEP-ATTACK" : "Manger, James. <a href=\"http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf\"><cite> A Chosen Ciphertext Attack on RSA Optimal Asymmetric Encryption Padding (OAEP) as Standardized in PKCS #1 v2.0</cite></a>. URL: <a href=\"http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf\">http://archiv.infsec.ethz.ch/education/fs08/secsem/Manger01.pdf</a>",
    "OASIS-TAG": "Stephen D. Green, Dmitry Kostovarov. <a href=\"http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html\"><cite>Test Assertions Guidelines</cite></a>. OASIS Committee Draft (Work in progress) .URL: <a href=\"http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html\">http://docs.oasis-open.org/tag/guidelines/v1.0/testassertionsguidelines.html</a>",
     "OGP"  :    "<a href=\"http://ogp.me\"> <cite>The Open Graph Protocol</cite></a>.  December 2010. URL: <a href=\"http://ogp.me\">http://ogp.me</a>",
     "OCSP"  :    "M. Myers, R. Ankney, A. Malpani, S. Galperin. <a href=\"http://www.ietf.org/rfc/rfc2560.txt\"><cite>X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP</cite></a>. June 1999. IETF RFC 2560. URL: <a href=\"http://www.ietf.org/rfc/rfc2560.txt\">http://www.ietf.org/rfc/rfc2560.txt</a>",
     "ODRL11" : "Renato Iannella. <a href=\"http://www.w3.org/TR/odrl\"><cite>Open Digital Rights Language (ODRL) Version 1.1.</cite></a> W3C Note. 19 September 2002. URL: <a href=\"http://www.w3.org/TR/odrl\">http://www.w3.org/TR/odrl</a> ",
    "OEB101" : "<a href=\"http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm\"><cite>Open eBook(tm) Publication Structure 1.0.1.</cite></a> Open eBook Forum(tm). 02 July 2001. URL: <a href=\"http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm\">http://www.openebook.org/oebps/oebps1.0.1/download/oeb101-xhtml.htm</a> ",
    "OFFLINE-WEBAPPS" : "Ian Hickson; Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530\"><cite>Offline Web Applications.</cite></a> 30 May 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530\">http://www.w3.org/TR/2008/NOTE-offline-webapps-20080530</a> ",
+   	"OIPF-DAE-2": "Open IPTV Forum. Release 2 volume 5 (v2.1). URL:<a href='http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf'>http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-5-Declarative-Application-Environment-v2_1-2011-06-21.pdf</a>",
+   	"OIPF-SERV-2": "Open IPTV Forum. Services and Functions for Release 2 - v1.0”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Services_and_Functions-V1_0-2008-10-20.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Services_and_Functions-V1_0-2008-10-20.pdf</a>",
+   	"OIPF-REQS-2": "Open IPTV Forum. Open IPTV Forum Service and Platform Requirements v2.0”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Service-and-Platform-RequirementsV2_0-2008-12-12.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Service-and-Platform-RequirementsV2_0-2008-12-12.pdf</a>",
+   	"OIPF-ARCH-2": "Open IPTV Forum. Functional Architecture - V2.1”. URL:<a href='http://www.oipf.tv/docs/OIPF-T1-R2-Functional_Architecture-v2_1-2011-03-15.pdf'>http://www.oipf.tv/docs/OIPF-T1-R2-Functional_Architecture-v2_1-2011-03-15.pdf</a>",
+   	"OIPF-PROT-2": "Open IPTV Forum. Release 2 volume 4 (v2.1). URL:<a href='http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-4-Protocols-v2_1-2011-06-21.pdf'>http://www.oipf.tv/docs/Release2/V2.1/OIPF-T1-R2-Specification-Volume-4-Protocols-v2_1-2011-06-21.pdf</a>",   	
+   "OMA-CAB":  "Converged Address Book Enabler, Version 1.0, Open Mobile Alliance, URL: http://www.openmobilealliance.org/",
    "OMA-DM" :  "<a href=\"http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx\"><cite>OMA Device Management V1.2 </cite></a> 17 June 2008. URL: <a href=\"http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx\">http://www.openmobilealliance.org/Technical/release_program/dm_v1_2.aspx</a> ",
+   "ORIGIN" : "<a href='http://tools.ietf.org/html/rfc6454'>The Web Origin Concept</a>, A. Barth. IETF.",
    "OWL-FEATURES" : "Deborah L. McGuinness; Frank van Harmelen. <a href=\"http://www.w3.org/TR/2004/REC-owl-features-20040210\"><cite>OWL Web Ontology Language Overview.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-features-20040210\">http://www.w3.org/TR/2004/REC-owl-features-20040210</a> ",
    "OWL-GUIDE" : "Deborah L. McGuinness; Michael K. Smith; Chris Welty. <a href=\"http://www.w3.org/TR/2004/REC-owl-guide-20040210\"><cite>OWL Web Ontology Language Guide.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-owl-guide-20040210\">http://www.w3.org/TR/2004/REC-owl-guide-20040210</a> ",
    "OWL-PARSING" : "Sean Bechhofer. <a href=\"http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121\"><cite>OWL Web Ontology Language Parsing OWL in RDF/XML.</cite></a> 21 January 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121\">http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121</a> ",
@@ -331,6 +364,7 @@
    "OWL2-PROFILES" : "Boris Motik; Bernardo Cuenca Grau; Ian Horrocks; Zhe Wu; Achille Fokoue; Carsten Lutz. <a href=\"http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/\"><cite>OWL 2 Web Ontology Language:Profiles.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/\">http://www.w3.org/TR/2009/REC-owl2-profiles-20091027/</a> ",
    "OWL2-QUICK-REFERENCE" : "Jie Bao; Elisa F. Kendall; Deborah L. McGuinness, Peter F. Patel-Schneider. <a href=\"http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/\"><cite>OWL 2 Web Ontology Language:Quick Reference Guide.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/\">http://www.w3.org/TR/2009/REC-owl2-quick-reference-20091027/</a> ",
    "OWL2-RDF-BASED-SEMANTICS" : "Michael Schneider. <a href=\"http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/\"><cite>OWL 2 Web Ontology Language:RDF-Based Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/\">http://www.w3.org/TR/2009/REC-owl2-rdf-based-semantics-20091027/</a> ",
+   "OWL-RL-in-RIF" : "Dave Reynolds. <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\"><cite>OWL 2 RL in RIF.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\">http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/</a> ",
    "OWL2-DIRECT-SEMANTICS" : "Boris Motik; Peter F. Patel-Schneider; Bernardo Cuenca Grau. <a href=\"http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/\"><cite>OWL 2 Web Ontology Language:Direct Semantics.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/\">http://www.w3.org/TR/2009/REC-owl2-direct-semantics-20091027/</a> ",
    "OWL2-SYNTAX" : "Boris Motik; Peter F. Patel-Schneider; Bijan Parsia. <a href=\"http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/\"><cite>OWL 2 Web Ontology Language:Structural Specification and Functional-Style Syntax.</cite></a> 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/\">http://www.w3.org/TR/2009/REC-owl2-syntax-20091027/</a> ",
    "OWL2-CONFORMANCE" : "Michael Smith; Ian Horrocks; Markus Krötzsch; Birte Glimm. <a href=\"http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/\"><cite>OWL 2 Web Ontology Language:Conformance.</cite></a> 27 October 2009. W3C Recommendation.  URL: <a href=\"http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/\">http://www.w3.org/TR/2009/REC-owl2-conformance-20091027/</a> ",
@@ -343,7 +377,8 @@
    "P3P10-PROTOCOLS" : "Joseph Reagle; Philip DesAutels; Steve Lucas. <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324\"><cite>P3P Protocol and Data Transport Working Group Draft White Paper.</cite></a> 24 March 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324\">http://www.w3.org/TR/1998/NOTE-P3P10-Protocols-19980324</a> ",
    "P3P11" : "Matthias Schunter; Rigo Wenning. <a href=\"http://www.w3.org/TR/2006/NOTE-P3P11-20061113\"><cite>The Platform for Privacy Preferences 1.1 (P3P1.1) Specification.</cite></a> 13 November 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-P3P11-20061113\">http://www.w3.org/TR/2006/NOTE-P3P11-20061113</a> ",
    "P3PDEPLOYMENT" : "Martin Presler-Marshall. <a href=\"http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211\"><cite>The Platform for Privacy Preferences 1.0 Deployment Guide.</cite></a> 11 February 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211\">http://www.w3.org/TR/2002/NOTE-p3pdeployment-20020211</a> ",
-   "PGP" : "J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer. <a href=\"http://www.ietf.org/rfc/rfc2440.txt\"><cite>OpenPGP Message Format.</cite></a>. IETF RFC 4880. November 2007. URL: <a href=\"http://www.ietf.org/rfc/rfc4880.txt\">http://www.ietf.org/rfc/rfc4880.txt</a>",
+   "PAGE-VISIBILITY" : "J. Mann; A. Jain. <a href=\"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html\"><cite>Page Visibility</cite></a>. 26 September 2011. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html\">http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html</a> ",
+   "PGP" : "J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer. <a href=\"http://www.ietf.org/rfc/rfc4880.txt\"><cite>OpenPGP Message Format</cite></a>. IETF RFC 4880. November 2007. URL: <a href=\"http://www.ietf.org/rfc/rfc4880.txt\">http://www.ietf.org/rfc/rfc4880.txt</a>",
    "PICS-LABELS" : "Win Treese; et al. <a href=\"http://www.w3.org/TR/REC-PICS-labels-961031\"><cite>PICS 1.1 Label Distribution -- Label Syntax and Communication Protocols.</cite></a> 31 October 1996. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICS-labels-961031\">http://www.w3.org/TR/REC-PICS-labels-961031</a> ",
    "PICS-SERVICES" : "David Singer; Paul Resnick; Jim Miller. <a href=\"http://www.w3.org/TR/REC-PICS-services-961031\"><cite>PICS 1.1 Rating Services and Rating Systems -- and Their Machine Readable Descriptions.</cite></a> 31 October 1996. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICS-services-961031\">http://www.w3.org/TR/REC-PICS-services-961031</a> ",
    "PICSRULES" : "Clive D.W. Feather; et al. <a href=\"http://www.w3.org/TR/REC-PICSRules-971229\"><cite>PICSRules 1.1 Specification.</cite></a> 29 December 1997. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-PICSRules-971229\">http://www.w3.org/TR/REC-PICSRules-971229</a> ",
@@ -356,6 +391,7 @@
    "POINTERS-IN-RDF" : "Mike Squillace; Carlos Iglesias. <a href=\"http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310\"><cite>Pointer Methods in RDF.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310\">http://www.w3.org/TR/2009/WD-Pointers-in-RDF-20090310</a> ",
    "POLICY-REQS" : "Laura Arribas; Paddy Byers; Marcin Hanclik; Frederick Hirsch; David Rogers. <a href=\"http://dev.w3.org/2009/dap/policy-reqs\"><cite>Device API Policy Requirements.</cite></a> 13 April 2010. W3C Editor's Draft. (Work in progress.) URL: <a href=\"http://dev.w3.org/2009/dap/policy-reqs/\">http://dev.w3.org/2009/dap/policy-reqs/</a> ",
    "POSITIONING" : "Robert Stevahn; Scott Furman; Scott Isaacs. <a href=\"http://www.w3.org/TR/1999/WD-positioning-19990902\"><cite>Positioning HTML Elements with Cascading Style Sheets.</cite></a> 2 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-positioning-19990902\">http://www.w3.org/TR/1999/WD-positioning-19990902</a> ",
+   "POSTMSG":   "Ian Hickson. <a href='http://www.w3.org/TR/webmessaging/'><cite>HTML5 Web Messaging.</cite></a> 13 March 2012. W3C Working Draft. (Work In Progress.) URL: <a href='http://www.w3.org/TR/webmessaging/'>http://www.w3.org/TR/webmessaging/</a>",
    "POWDER-DR" : "Kevin Smith; Phil Archer; Andrea Perego. <a href=\"http://www.w3.org/TR/2008/WD-powder-dr-20081114\"><cite>Protocol for Web Description Resources (POWDER): Description Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-dr-20081114\">http://www.w3.org/TR/2008/WD-powder-dr-20081114</a> ",
    "POWDER-FORMAL" : "Phil Archer; Stasinos Konstantopoulos. <a href=\"http://www.w3.org/TR/2008/WD-powder-formal-20081114\"><cite>Protocol for Web Description Resources (POWDER): Formal Semantics.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-formal-20081114\">http://www.w3.org/TR/2008/WD-powder-formal-20081114</a> ",
    "POWDER-GROUPING" : "Andrea Perego; Kevin Smith; Phil Archer. <a href=\"http://www.w3.org/TR/2008/WD-powder-grouping-20081114\"><cite>Protocol for Web Description Resources (POWDER): Grouping of Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-powder-grouping-20081114\">http://www.w3.org/TR/2008/WD-powder-grouping-20081114</a> ",
@@ -368,13 +404,18 @@
    "PRIV-ICONS": "Raskin, A. <a href ='http://www.azarask.in/blog/post/what-should-matter-in-privacy'><cite>The 7 Things that Mater Most in Privacy</cite></a> 31 March 2010. URL: http://www.azarask.in/blog/post/what-should-matter-in-privacy ",
    "PRIV-ICONSET" : "Mehldau, M. <a href = 'http://asset.netzpolitik.org/wp-upload/data-privacy-icons-v01.pdf'><cite>Iconset for Data-Privacy Declarations v0.1</cite></a> URL: http://www.netzpolitik.org/wp-upload/data-privacy-icons-v01.pdf ",
    "PRIV-LABEL": "Kelley, P. Bresse, J. Cranor, L. Reeder, R. <a href ='http://cups.cs.cmu.edu/soups/2009/proceedings/a4-kelley.pdf'><cite>A 'Nutrition Label' for Privacy</cite></a> 10 November 2009. Carnegie Mellon University. URL: http://cups.cs.cmu.edu/soups/2009/proceedings/a4-kelley.pdf ",
+   "PRIVACY-BY-DESIGN": "Ann Cavoukian, PhD. <a href='http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf'><cite>Privacy By Design: The 7 Foundational Principles</cite></a>. August 2009, revised January 2011. URL: <a href='http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf'>http://www.ipc.on.ca/images/Resources/7foundationalprinciples.pdf</a>",
    "PRIVACY-ISSUES-GEO": "Doty, N. Mulligan, D. Wilde, E. <a href='http://escholarship.org/uc/item/0rp834wf'><cite>Privacy Issues of the W3C Geolocation API</cite></a>. UC Berkeley School of Information. 24 February 2010. URL: http://escholarship.org/uc/item/0rp834wf ",
     "PRIVACY-TERMINOLOGY" : "A. Pfitzmann, M. Hansen, H Tschofenig. <a href=\"http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html\"><cite>Terminology for Talking about Privacy by Data Minimization: Anonymity, Unlinkability, Undetectability, Unobservability, Pseudonymity, and Identity Management</cite></a> IETF Internet Draft. URL: <a hre\"http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html\">http://tools.ietf.org/id/draft-hansen-privacy-terminology-00.html</a>",
    "PROC-MODEL-REQ" : "Dmitry Lenkov; Norman Walsh. <a href=\"http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405\"><cite>XML Processing Model Requirements.</cite></a> 5 April 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405\">http://www.w3.org/TR/2004/NOTE-proc-model-req-20040405</a> ",
-   "PROGRESS-EVENTS" : "Charles McCathieNevile. <a href=\"http://www.w3.org/TR/2008/WD-progress-events-20080521\"><cite>Progress Events 1.0.</cite></a> 21 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-progress-events-20080521\">http://www.w3.org/TR/2008/WD-progress-events-20080521</a> ",
+   "PROGRESS-EVENTS" : "Charles McCathieNevile. <a href=\"http://www.w3.org/TR/2011/CR-progress-events-20110922/\"><cite>Progress Events 1.0.</cite></a> 22 September 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-progress-events-20110922/\">http://www.w3.org/TR/2011/CR-progress-events-20110922/</a> ",
    "PROV-RDF-S" : "Panagiotis Pediaditis; Giorgos Flouris; Irini Fundulaki; Vassilis Christophides. <a href=\"http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/\"><cite>On Explicit Provenance Management in RDF/S Graphs</cite></a> 2009. First Workshop on the Theory and Practice of Provenance (TaPP'09), ed. James Cheney. San Francisco, CA. URL: <a href='http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/'>http://www.usenix.org/events/tapp09/tech/full_papers/pediaditis/pediaditis_html/</a> ",
    "PROV-QUERY" : "Renata Dividino; Sergey Sizov; Steffen Staab; Bernhard Schueler. <a href=\"http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237\"><cite>Querying for provenance, trust, uncertainty and other meta knowledge in RDF</cite></a>. 2009. Web Semantics: Science, Services and Agents on the World Wide Web, vol. 7, 2009, p. 204-219. URL: <a href='http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237'>http://linkinghub.elsevier.com/retrieve/pii/S1570826809000237</a> ",
    "PRONUNCIATION-LEXICON" : "Paolo Baggia. <a href=\"http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014\"><cite>Pronunciation Lexicon Specification (PLS) Version 1.0.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014\">http://www.w3.org/TR/2008/REC-pronunciation-lexicon-20081014</a> ",
+    "PTECH-DECL" : "C. Concolato; J. Le Feuvre; J. C. Dufourd. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917\"><cite>Declarative Interfaces for Dynamic Widgets Communications</cite></a>. September 2009. Document Engineering, Munich, Germany, September 2009, pp. 241-244. PDF Document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9917</a>",
+    "PTECH-MIGRATE" : "C. Concolato; J. C. Dufourd; J. Le Feuvre; K. Parkl J. Song. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187\"><cite>Communicating and migratable interactive multimedia documents</cite></a>. May 2011. Multimedia Tools and Applications. PDF document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=11187</a>",
+    "PTECH-SCW" : "J. C. Dufourd; C. Concolato; J. Le Feuvre. <a href=\"http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/\"><cite>SVG Communicating Widgets</cite></a>. October 2009. SVG Open, Mountain View, CA, USA. URL: <a href=\"http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/\">http://www.svgopen.org/2009/papers/28-SVG_Communicating_Widgets/</a>",
+    "PTECH-WM" : "J. Le Feuvre; C. Concolato; J. C. Dufourd. <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919\"><cite>Widgets Mobility</cite></a>. September 2009. International Conference on Mobile Technology, Applications and Systems, Nice, France. PDF document. URL: <a href=\"http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919\">http://biblio.telecom-paristech.fr/cgi-bin/download.cgi?id=9919</a>",
    "PWGMSN" : "Ron Bergman; Tom Hastings. <a href=\"ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf\"><cite>Media Standardized Names.</cite></a> 26 February 2002. IEEE ISTO Printer Working Group 5101.1-2002. URL: <a href=\"ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf\">ftp://ftp.pwg.org/pub/pwg/candidates/cs-pwgmsn10-20020226-5101.1.pdf</a> ",
    "QA-HANDBOOK" : "Lofton Henderson. <a href=\"http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906\"><cite>The QA Handbook.</cite></a> 6 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906\">http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906</a> ",
    "QAFRAME-OPS-EXTECH" : "Dimitris Dimitriadis; et al. <a href=\"http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202\"><cite>QA Framework: Operational Examples &amp; Techniques.</cite></a> 2 December 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202\">http://www.w3.org/TR/2002/NOTE-qaframe-ops-extech-20021202</a> ",
@@ -395,8 +436,9 @@
    "RDF-SYNTAX-GRAMMAR" : "Dave Beckett. <a href=\"http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210\"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210\">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a> ",
    "RDF-TESTCASES" : "Jan Grant; Dave Beckett. <a href=\"http://www.w3.org/TR/2004/REC-rdf-testcases-20040210\"><cite>RDF Test Cases.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-testcases-20040210\">http://www.w3.org/TR/2004/REC-rdf-testcases-20040210</a> ",
    "RDF-UML" : "Walter W. Chang. <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\"><cite>A Discussion of the Relationship Between RDF-Schema and UML.</cite></a> 4 August 1998. W3C Note. URL: <a href=\"http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804\">http://www.w3.org/TR/1998/NOTE-rdf-uml-19980804</a> ",
-   "RDFA-CORE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2011/WD-rdfa-core-20110331\"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 31 March 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-rdfa-core-20110331\">http://www.w3.org/TR/2011/WD-rdfa-core-20110331</a> ",
-   "RDFA-PRIMER" : "Mark Birbeck; Ben Adida. <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\"><cite>RDFa Primer.</cite></a> 14 October 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\">http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014</a> ",
+   "RDFA-CORE" : "Shane McCarron; et al. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 8 May 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-core-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-core-20120508/</a> ",
+  "RDFA-LITE" : "Manu Sporny. <a href=\"http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/\"><cite>RDFa Lite 1.1.</cite></a> 8 May 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/\">http://www.w3.org/TR/2012/PR-rdfa-lite-20120508/</a> ",
+   "RDFA-PRIMER" : "Ben Adida, Ivan Herman, Manu Sporny. <a href=\"http://www.w3.org/TR/2011/WD-rdfa-primer-20111208\"><cite>RDFa Primer.</cite></a> 08 December 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-rdfa-primer-20111208\">http://www.w3.org/TR/2011/WD-rdfa-primer-20111208</a> ",
    "RDFA-SYNTAX" : "Ben Adida, et al. <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\"><cite>RDFa in XHTML: Syntax and Processing.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014\">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a> ",
    "RDFCAL" : "Dan Connolly; Libby Miller. <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\"><cite>RDF Calendar - an application of the Resource Description Framework to iCalendar Data.</cite></a> 29 September 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-rdfcal-20050929\">http://www.w3.org/TR/2005/NOTE-rdfcal-20050929</a> ",
    "RDFTM-SURVEY" : "Fabio Vitali; et al. <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\"><cite>A Survey of RDF/Topic Maps Interoperability Proposals.</cite></a> 10 February 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210\">http://www.w3.org/TR/2006/NOTE-rdftm-survey-20060210</a> ",
@@ -423,15 +465,19 @@
    "RFC3023" : "M. Murata; S. St.Laurent; D. Kohn. <a href=\"http://www.ietf.org/rfc/rfc3023.txt\"><cite>XML Media Types</cite></a> January 2001. Internet RFC 3023. URL: <a href=\"http://www.ietf.org/rfc/rfc3023.txt\">http://www.ietf.org/rfc/rfc3023.txt</a> ",
    "RFC3161" : "C. Adams, P. Cain, D. Pinkas, R. Zuccherato. <a href=\"http://www.rfc-editor.org/rfc/rfc3161.txt\"><cite>Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)</cite></a> August 2001. Internet RFC 3161. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3161.txt\">http://www.rfc-editor.org/rfc/rfc3161.txt</a> ",
    "RFC3161-PKIX-UPDATE-9" : "Stefan Santesson, Nick Pope. <a href=\"http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt\"><cite> ESSCertIDv2 update for RFC 3161</cite></a> 29 April 2010, IETF Internet Draft. URL: <a href=\"http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt\"> http://tools.ietf.org/id/draft-ietf-pkix-rfc3161-update-09.txt</a> ",
+    "RFC3218" : "Rescorla, E. <a href=\"http://tools.ietf.org/html/rfc3218\"><cite>Preventing the Million Message Attack on Cryptographic Message Syntax.</cite></a>January 2002. Informational RFC 3218. URL: <a href=\"http://tools.ietf.org/html/rfc3218\">http://tools.ietf.org/html/rfc3218</a>",
    "RFC3236" : "P. Stark; M. Baker. <a href=\"http://www.rfc-editor.org/rfc/rfc3236.txt\"><cite>The 'application/xhtml+xml' Media Type.</cite></a> January 2002. Internet RFC 3236. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc3236.txt\">http://www.rfc-editor.org/rfc/rfc3236.txt</a> ",
-   "RFC3279" : "W. Polk, R. Housley, L. Bassham. <a href=\"http://www.ietf.org/rfc/rfc3279.txt\"><cite>Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</cite></a>. April 2002. Internet RFC 3279. URL: <a href=\"http://www.ietf.org/rfc/rfc3279.txt\">http://www.ietf.org/rfc/rfc3279.txt</a>",
+   "RFC3279" : "W. Polk, R. Housley, L. Bassham. <a href=\"http://www.ietf.org/rfc/rfc3279.txt\"><cite>Algorithmupdates and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</cite></a>. April 2002. Internet RFC 3279. URL: <a href=\"http://www.ietf.org/rfc/rfc3279.txt\">http://www.ietf.org/rfc/rfc3279.txt</a>",
+   "RFC3339" : "G. Klyne, C. Newman. <a href=\"http://www.ietf.org/rfc/rfc3339.txt\"><cite>Date and Time on the Internet: Timestamps</cite></a>. July 2002. Internet RFC 3339. URL: <a href=\"http://www.ietf.org/rfc/rfc3339.txt\">http://www.ietf.org/rfc/rfc3339.txt</a>",
    "RFC3490" : "P. Faltstrom; P. Hoffman; A. Costello. <a href='http://www.rfc-editor.org/rfc/rfc3490.txt'><cite>Internationalizing Domain Names in Applications (IDNA).</cite></a> March 2003. Internet RFC 3490. URL: <a href='http://www.rfc-editor.org/rfc/rfc3490.txt'>http://www.rfc-editor.org/rfc/rfc3490.txt</a>",
+   "RFC3555" : "S. Casner; P. Hoschka. <a href='http://www.rfc-editor.org/rfc/rfc3555.txt'><cite>MIME Type Registration of RTP Payload Formats</cite></a>. July 2003. Internet RFC 3555. URL: <a href='http://www.rfc-editor.org/rfc/rfc3555.txt'>http://www.rfc-editor.org/rfc/rfc3555.txt</a>",
    "RFC3986" : "T. Berners-Lee; R. Fielding; L. Masinter. <a href=\"http://www.ietf.org/rfc/rfc3986.txt\"><cite>Uniform Resource Identifier (URI): Generic Syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href=\"http://www.ietf.org/rfc/rfc3986.txt\">http://www.ietf.org/rfc/rfc3986.txt</a> ",
    "RFC3987" : "M. D&#252;rst; M. Suignard. <a href=\"http://www.ietf.org/rfc/rfc3987.txt\"><cite>Internationalized Resource Identifiers (IRIs).</cite></a> January 2005. Internet RFC 3987. URL: <a href=\"http://www.ietf.org/rfc/rfc3987.txt\">http://www.ietf.org/rfc/rfc3987.txt</a> ",
    "RFC4050" : "S. Blake-Wilson, G. Karlinger, T. Kobayashi, Y. Wang.     <a href=\"http://www.ietf.org/rfc/rfc4050.txt\"><cite>Using the Elliptic Curve Signature Algorithm (ECDSA) for XML Digital Signatures.</cite></a> IETF RFC 4050. April 2005. URL: <a href=\"http://www.ietf.org/rfc/rfc4050.txt\">http://www.ietf.org/rfc/rfc4050.txt</a>",
    "RFC4051" : "D. Eastlake 3rd. <a href=\"http://www.ietf.org/rfc/rfc4051.txt\"><cite>Additional XML Security Uniform Resource Identifiers</cite></a>. RFC 4051 April 2005. URL: <a href=\"http://www.ietf.org/rfc/rfc4051.txt\">http://www.ietf.org/rfc/rfc4051.txt</a>",
    "RFC4055" : "J. Schaad, B. Kaliski, R. Housley. <a href=\"http://www.ietf.org/rfc/rfc4055.txt\"><cite>Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</cite></a>. June 2005. IETF RFC 4055. URL: <a href=\"http://www.ietf.org/rfc/rfc4055.txt\">http://www.ietf.org/rfc/rfc4055.txt</a>",
    "RFC4122" : "P. Leach; M. Mealling; R. Salz. <a href=\"http://www.ietf.org/rfc/rfc4122.txt\"><cite>A Universally Unique IDentifier (UUID) URN Namespace</cite></a> July 2005. Internet RFC 4122. URL: <a href=\"http://www.ietf.org/rfc/rfc4122.txt\">http://www.ietf.org/rfc/rfc4122.txt</a> ",
+   "RFC4180" : "Y. Shafranovich. <a href=\"http://www.ietf.org/rfc/rfc4180.txt\"> <cite>Common Format and MIME Type for Comma-Separated Values (CSV) Files</cite></a> October 2005. Internet RFC 3987. URL: <a href=\"http://www.ietf.org/rfc/rfc4180.txt\">http://www.ietf.org/rfc/rfc4180.txt</a>",
    "RFC4281" : "R. Gellens, D. Singer, P. Frojdh. <a href=\"http://www.ietf.org/rfc/rfc4281.txt\"><cite>The Codecs Parameter for &quot;Bucket&quot; Media Types</cite></a> November 2005. Internet RFC 4281. URL: <a href=\"http://www.ietf.org/rfc/rfc4281.txt\">http://www.ietf.org/rfc/rfc4281.txt</a> ",
    "RFC4572" : "J. Lennox. <a href=\"http://www.ietf.org/rfc/rfc4572.txt\"><cite> Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP).</cite></a> July 2006. Internet RFC 4572. URL: <a href=\"http://www.ietf.org/rfc/rfc4572.txt\">http://www.ietf.org/rfc/rfc4572.txt</a>",
    "RFC4627" : "D. Crockford. <a href=\"http://www.ietf.org/rfc/rfc4627.txt\"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a> July 2006. Internet RFC 4627. URL: <a href=\"http://www.ietf.org/rfc/rfc4627.txt\">http://www.ietf.org/rfc/rfc4627.txt</a>",
@@ -440,6 +486,8 @@
    "RFC5280" : "D. Cooper, et. al. <a href=\"http://www.ietf.org/rfc/rfc5280.txt\"><cite> Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile. </cite></a>. IETF RFC 5280 May 2008. URL: <a href=\"http://www.ietf.org/rfc/rfc5280.txt\">http://www.ietf.org/rfc/rfc5280.txt</a>",
    "RFC5480" : "S. Turner, et. al. <a href=\"http://www.ietf.org/rfc/rfc5480.txt\"><cite> Elliptic Curve Cryptography Subject Public Key Information.</cite></a>. IETF RFC 5480 March 2009. URL: <a href=\"http://www.ietf.org/rfc/rfc5480.txt\">http://www.ietf.org/rfc/rfc5480.txt</a>",
    "RFC5545" : "B. Desruisseaux. <a href=\"http://www.rfc-editor.org/rfc/rfc5545.txt\"><cite>Internet Calendaring and Scheduling Core Object Specification (iCalendar).</cite></a> September 2009. Internet RFC 5545. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5545.txt\">http://www.rfc-editor.org/rfc/rfc5545.txt</a> ",
+   "RFC5646" : "A. Phillips, M. Davis. <a href=\"http://www.rfc-editor.org/rfc/rfc5646.txt\"><cite>Tags for Identifying Languages.</cite></a> September 2009. Internet RFC 5646. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5646.txt\">http://www.rfc-editor.org/rfc/rfc5646.txt</a> ",
+   "RFC5785" : "Mark Nottingham; Eran Hammer-Lahav. <a href=\"http://www.rfc-editor.org/rfc/rfc5785.txt\"><cite>Defining Well-Known Uniform Resource Identifiers (URIs).</cite></a> April 2010. Internet Proposed Standard RFC 5785. URL: <a href=\"http://www.rfc-editor.org/rfc/rfc5785.txt\">http://www.rfc-editor.org/rfc/rfc5785.txt</a> ",
    "RichSnippets" : "<a href=\"http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/\"><cite>Introducing Rich Snippets.</cite></a> 12 May 2009. Google Webmaster Central Blog. URL: <a href=\"http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/\">http://googlewebmastercentral.blogspot.com/2009/05/introducing-rich-snippets.html/</a> ",
    "RIF-BLD" : "Harold Boley, Michael Kifer; . <a href=\"http://www.w3.org/TR/2010/REC-rif-bld-20100622/\"><cite>RIF Basic Logic Dialect.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-bld-20100622/\">http://www.w3.org/TR/2010/REC-rif-bld-20100622/</a> ",
    "RIF-CORE": "Harold Boley, et al. <a href=\"http://www.w3.org/TR/2010/REC-rif-core-20100622/\"><cite>RIF Core.</cite></a> 22 June 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-rif-core-20100622/\">http://www.w3.org/TR/2010/REC-rif-core-20100622/</a> ",
@@ -450,33 +498,35 @@
    "RIF-TEST" : "Stella Mitchell, Leora Morgenstern, Adrian Paschke. <a href=\"http://www.w3.org/TR/2010/WD-rif-test-20100622/\"><cite>RIF Test Cases.</cite></a> 1 October 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-rif-test-20100622/\">http://www.w3.org/TR/2010/WD-rif-test-20100622/</a> ",
    "RIF-OVERVIEW" : "Michael Kifer; Harold Boley. <a href=\"http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/\"><cite>RIF Overview.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/\">http://www.w3.org/TR/2010/NOTE-rif-overview-20100622/</a> ",
    "RIF-UCR" : "David Hirtle; et al. <a href=\"http://www.w3.org/TR/2008/WD-rif-ucr-20081218\"><cite>RIF Use Cases and Requirements.</cite></a> 18 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-rif-ucr-20081218\">http://www.w3.org/TR/2008/WD-rif-ucr-20081218</a> ",
-   "OWL-RL-in-RIF" : "Dave Reynolds. <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\"><cite>OWL 2 RL in RIF.</cite></a> 22 June 2010. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/\">http://www.w3.org/TR/2010/NOTE-rif-owl-rl-20100622/</a> ",
-   "RIPEMD-160" : "CryptoBytes, Volume 3, Number 2. <a href=\"http://homes.esat.kuleuven.be/~cosicart/pdf/AB-9601/AB-9601.pdf\"><cite>The Cryptographic Hash Function RIPEMD-160</cite></a>. RSA Laboratories. Autumn 1997. URL: <a href=\"http://homes.esat.kuleuven.be/~cosicart/pdf/AB-9601/AB-9601.pdf\">http://homes.esat.kuleuven.be/~cosicart/pdf/AB-9601/AB-9601.pdf</a>",
+   "RIPEMD-160" : "B. Preneel, A. Bosselaers, and H. Dobbertin. <a href=\"http://www.cosic.esat.kuleuven.be/publications/article-317.pdf\"><cite>The Cryptographic Hash Function RIPEMD-160</cite></a>. CryptoBytes, Volume 3, Number 2. pp. 9-14, RSA Laboratories 1997. URL: <a href=\"http://www.cosic.esat.kuleuven.be/publications/article-317.pdf\">http://www.cosic.esat.kuleuven.be/publications/article-317.pdf</a>",
+   "RTCWEB-USECAS" : "C. Holmberg, S. Hakansson, G. Eriksson. <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/\"><cite>Web Real-Time Communication Use-cases and Requirements.</cite></a> URL: <a href=\"http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/\">http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/</a> ",
    "RUBY" : "Masayasu Ishikawa; et al. <a href=\"http://www.w3.org/TR/2001/REC-ruby-20010531\"><cite>Ruby Annotation.</cite></a> 31 May 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-ruby-20010531\">http://www.w3.org/TR/2001/REC-ruby-20010531</a> ",
    "S6GROUP2" : "Stuart Weibel. <a href=\"http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2\"><cite>A Proposed Convention for Embedding Metadata in HTML.</cite></a> 2 June 1996. W3C Note. URL: <a href=\"http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2\">http://www.w3.org/Search/9605-Indexing-Workshop/ReportOutcomes/S6Group2</a> ",
-"SAML2-CORE" : "Scott Cantor; John Kemp; Rob Philpott; Eve Maler. <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\"><cite>Assertions and Protocols for SAML V2.0</cite></a> 15 March 2005. URL: <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\">http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf</a>",
+   "SAML2-CORE" : "Scott Cantor; John Kemp; Rob Philpott; Eve Maler. <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\"><cite>Assertions and Protocols for SAML V2.0</cite></a> 15 March 2005. URL: <a href=\"http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf\">http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf</a>",
    "SAWSDL" : "Joel Farrell; Holger Lausen. <a href=\"http://www.w3.org/TR/2007/REC-sawsdl-20070828\"><cite>Semantic Annotations for WSDL and XML Schema.</cite></a> 28 August 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-sawsdl-20070828\">http://www.w3.org/TR/2007/REC-sawsdl-20070828</a> ",
    "SAWSDL-GUIDE" : "Rama Akkiraju; Brahmananda Sapkota. <a href=\"http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828\"><cite>Semantic Annotations for WSDL and XML Schema &#8212; Usage Guide.</cite></a> 28 August 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828\">http://www.w3.org/TR/2007/NOTE-sawsdl-guide-20070828</a> ",
    "SAX" : "D. Megginson, et al. <a href=\"http://www.megginson.com/downloads/SAX/\"><cite>SAX: The Simple API for XML</cite></a>. May 1998. URL: <a href=\"http://www.megginson.com/downloads/SAX/\"> http://www.megginson.com/downloads/SAX/</a>",
    "SCHEMA-ARCH" : "Ralph R. Swick; Henry S. Thompson. <a href=\"http://www.w3.org/TR/1999/NOTE-schema-arch-19991007\"><cite>The Cambridge Communiqu&#233;.</cite></a> 7 October 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-schema-arch-19991007\">http://www.w3.org/TR/1999/NOTE-schema-arch-19991007</a> ",
    "SCXML" : "Torbj&#246;rn Lage; et al. <a href=\"http://www.w3.org/TR/2008/WD-scxml-20080516\"><cite>State Chart XML (SCXML): State Machine Notation for Control Abstraction.</cite></a> 16 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-scxml-20080516\">http://www.w3.org/TR/2008/WD-scxml-20080516</a> ",
+   "SDP" : "J. Rosenberg, H. Schulzrinne. <a href=\"http://tools.ietf.org/html/rfc3264\"><cite>An Offer/Answer Model with the Session Description Protocol (SDP).</cite></a> June 2002. Internet RFC 3264. URL: <a href=\"http://tools.ietf.org/html/rfc3264\">http://tools.ietf.org/html/rfc3264</a>",
+   "SDPLABEL" : "O. Levin, G. Camarillo. <a href=\"http://tools.ietf.org/html/rfc4574\"><cite>The Session Description Protocol (SDP) Label Attribute.</cite></a> August 2006. Internet RFC 4574. URL: <a href=\"http://tools.ietf.org/html/rfc4574\">http://tools.ietf.org/html/rfc4574</a>",
    "SECG1" : "<a href=\"http://www.secg.org/download/aid-780/sec1-v2.pdf\"><cite>SEC1: Elliptic Curve Cryptography, Version 2.0, Standards for Efficient Cryptography Group</cite></a>. May 2009. URL: <a href=\"http://www.secg.org/download/aid-780/sec1-v2.pdf\">http://www.secg.org/download/aid-780/sec1-v2.pdf</a> ",
    "SELECT" : "Daniel Glazman; et al. <a href=\"http://www.w3.org/TR/2009/WD-css3-selectors-20090310\"><cite>Selectors Level 3.</cite></a> 10 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-css3-selectors-20090310\">http://www.w3.org/TR/2009/WD-css3-selectors-20090310</a> ",
    "SELECTORS-API" : "Lachlan Hunt; Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-selectors-api-20081114\"><cite>Selectors API.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-selectors-api-20081114\">http://www.w3.org/TR/2008/WD-selectors-api-20081114</a> ",
    "SEMANTIC-INTERPRETATION" : "David Burke; Luc Van Tichelen. <a href=\"http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405\"><cite>Semantic Interpretation for Speech Recognition (SISR) Version 1.0.</cite></a> 5 April 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405\">http://www.w3.org/TR/2007/REC-semantic-interpretation-20070405</a> ",
    "SGML-CATALOG" : "Paul Grosso. <cite><a href='http://www.oasis-open.org/html/a401.htm'>Entity Management: OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401)</cite></a> 10 september 1007. Entity Management Subcommittee, SGML Open. URL: <a href='http://www.oasis-open.org/html/a401.htm'>http://www.oasis-open.org/html/a401.htm</a> ",
    "SGML-XML" : "James Clark. <a href=\"http://www.w3.org/TR/NOTE-sgml-xml-971215\"><cite>Comparison of SGML and XML.</cite></a> 15 December 1997. W3C Note. URL: <a href=\"http://www.w3.org/TR/NOTE-sgml-xml-971215\">http://www.w3.org/TR/NOTE-sgml-xml-971215</a> ",
- "SHA-1-Analysis" : "McDonald, C., Hawkes, P., and J. Pieprzyk. <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\"><cite>SHA-1 collisions now 2<sup>52</sup> </cite></a>. EuroCrypt 2009 Rump session. URL: <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\">http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf</a>",
-    "SHA-1-Collisions"  : "X. Wang, Y.L. Yin, H. Yu. <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\"><cite>Finding Collisions in the Full SHA-1</cite></a>. In Shoup, V., editor, Advances in Cryptology - CRYPTO 2005, 25th Annual International Cryptology Conference, Santa Barbara, California, USA, August 14-18, 2005, Proceedings, volume 3621 of LNCS, pages 17–36. Springer, 2005. URL: <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\">http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf</a> (also published in <a href=\"http://www.springerlink.com/content/26vljj3xhc28ux5m/\">http://www.springerlink.com/content/26vljj3xhc28ux5m/</a>)",
-   "SKOS-PRIMER" : "Ed Summers; Antoine Isaac. <a href=\"http://www.w3.org/TR/2009/WD-skos-primer-20090317\"><cite>SKOS Simple Knowledge Organization System Primer.</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-skos-primer-20090317\">http://www.w3.org/TR/2009/WD-skos-primer-20090317</a> ",
-   "SKOS-REFERENCE" : "Sean Bechhofer; Alistair Miles. <a href=\"http://www.w3.org/TR/2009/CR-skos-reference-20090317\"><cite>SKOS Simple Knowledge Organization System Reference.</cite></a> 17 March 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-skos-reference-20090317\">http://www.w3.org/TR/2009/CR-skos-reference-20090317</a> ",
+   "SHA-1-Analysis" : "McDonald, C., Hawkes, P., and J. Pieprzyk. <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\"><cite>SHA-1 collisions now 2<sup>52</sup> </cite></a>. EuroCrypt 2009 Rump session. URL: <a href=\"http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf\">http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf</a>",
+   "SHA-1-Collisions"  : "X. Wang, Y.L. Yin, H. Yu. <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\"><cite>Finding Collisions in the Full SHA-1</cite></a>. In Shoup, V., editor, Advances in Cryptology - CRYPTO 2005, 25th Annual International Cryptology Conference, Santa Barbara, California, USA, August 14-18, 2005, Proceedings, volume 3621 of LNCS, pages 17–36. Springer, 2005. URL: <a href=\"http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf\">http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf</a> (also published in <a href=\"http://www.springerlink.com/content/26vljj3xhc28ux5m/\">http://www.springerlink.com/content/26vljj3xhc28ux5m/</a>)",
+   "SKOS-PRIMER" : "Antoine Isaac; Ed Summers. <a href=\"http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/\"><cite>SKOS Simple Knowledge Organization System Primer.</cite></a> 18 August 2009. W3C Note. URL: <a href=\"http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/\">http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/</a> ",
+   "SKOS-REFERENCE" : "Sean Bechhofer; Alistair Miles. <a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\"><cite>SKOS Simple Knowledge Organization System Reference.</cite></a> 18 August 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">http://www.w3.org/TR/2009/REC-skos-reference-20090818/</a> ",
    "SKOS-UCR" : "Jon Phipps; Daniel Rubin; Antoine Isaac. <a href=\"http://www.w3.org/TR/2007/WD-skos-ucr-20070516\"><cite>SKOS Use Cases and Requirements.</cite></a> 16 May 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-skos-ucr-20070516\">http://www.w3.org/TR/2007/WD-skos-ucr-20070516</a> ",
    "SMIL-ANIMATION" : "Patrick Schmitz; Aaron Cohen. <a href=\"http://www.w3.org/TR/2001/REC-smil-animation-20010904\"><cite>SMIL Animation.</cite></a> 4 September 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-smil-animation-20010904\">http://www.w3.org/TR/2001/REC-smil-animation-20010904</a> ",
    "SMIL10" : "Philipp Hoschka. <a href=\"http://www.w3.org/TR/1998/REC-smil-19980615\"><cite>Synchronized Multimedia Integration Language (SMIL) 1.0 Specification.</cite></a> 15 June 1998. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1998/REC-smil-19980615\">http://www.w3.org/TR/1998/REC-smil-19980615</a> ",
    "SMIL2" : "Dick Bulterman; et al. <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\"><cite>Synchronized Multimedia Integration Language (SMIL 2.1).</cite></a> 13 December 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\">http://www.w3.org/TR/2005/REC-SMIL2-20051213</a> ",
    "SMIL20" : "Jack Jansen; et al. <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\"><cite>Synchronized Multimedia Integration Language (SMIL 2.1).</cite></a> 13 December 2005. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2005/REC-SMIL2-20051213\">http://www.w3.org/TR/2005/REC-SMIL2-20051213</a> ",
    "SMIL3" : "Dick Bulterman. <a href=\"http://www.w3.org/TR/2008/REC-SMIL3-20081201\"><cite>Synchronized Multimedia Integration Language (SMIL 3.0).</cite></a> 1 December 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-SMIL3-20081201\">http://www.w3.org/TR/2008/REC-SMIL3-20081201</a> ",
-   "SMIME" : "B. Ramsdell. <a href=\"http://www.ietf.org/rfc/rfc2633.txt\"><cite>S/MIME Version 3 Message Specification.</cite></a> June 1999. Internet RFC 2633. URL: <a href=\"http://www.ietf.org/rfc/rfc2633.txt\">http://www.ietf.org/rfc/rfc2633.txt</a> ",
+   "SMIME" : "B. Ramsdell. <a href=\"http://www.ietf.org/rfc/rfc3851.txt\"><cite>S/MIME Version 3.1 Message Specification.</cite></a> July 2004. Internet RFC 3851. URL: <a href=\"http://www.ietf.org/rfc/rfc3851.txt\">http://www.ietf.org/rfc/rfc3851.txt</a> ",
    "SML" : "Valentina Popescu; Virginia Smith; Bhalchandra Pandit. <a href=\"http://www.w3.org/TR/2009/PR-sml-20090212\"><cite>Service Modeling Language, Version 1.1.</cite></a> 12 February 2009. W3C Proposed Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/PR-sml-20090212\">http://www.w3.org/TR/2009/PR-sml-20090212</a> ",
    "SML-IF" : "Valentina Popescu; Bhalchandra Pandit; Virginia Smith. <a href=\"http://www.w3.org/TR/2009/PR-sml-if-20090212\"><cite>Service Modeling Language Interchange Format Version 1.1.</cite></a> 12 February 2009. W3C Proposed Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/PR-sml-if-20090212\">http://www.w3.org/TR/2009/PR-sml-if-20090212</a> ",
    "SOAP11-ROR-HTTPBINDING" : "David Orchard. <a href=\"http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321\"><cite>SOAP 1.1 Request Optional Response HTTP Binding.</cite></a> 21 March 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321\">http://www.w3.org/TR/2006/NOTE-soap11-ror-httpbinding-20060321</a> ",
@@ -505,10 +555,11 @@
    "SRGB" : "<a href=\"http://www.iec.ch/nr1899.htm\"><cite>Multimedia systems and equipment - Colour measurement and management - Part 2-1: Colour management - Default RGB colour space - sRGB.</cite></a> IEC 61966-2-1 (1999-10). ISBN: 2-8318-4989-6 - ICS codes: 33.160.60, 37.080 - TC 100 - 51 pp. URL: <a href=\"http://www.iec.ch/nr1899.htm\">http://www.iec.ch/nr1899.htm</a>",
    "SSML-SAYAS" : "Daniel C. Burnett; et al. <a href=\"http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526\"><cite>SSML 1.0 say-as attribute values.</cite></a> 26 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526\">http://www.w3.org/TR/2005/NOTE-ssml-sayas-20050526</a> ",
    "SSML11REQS" : "Daniel C. Burnett; Zhi Wei Shuang. <a href=\"http://www.w3.org/TR/2007/WD-ssml11reqs-20070611\"><cite>Speech Synthesis Markup Language Version 1.1 Requirements.</cite></a> 11 June 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-ssml11reqs-20070611\">http://www.w3.org/TR/2007/WD-ssml11reqs-20070611</a> ",
-    "SUITEB" : "<a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\"><cite>NSA Suite B Cryptography</cite></a>. URL: <a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\">http://www.nsa.gov/ia/programs/suiteb_cryptography/</a> ",
+   "STUN" : "J. Rosenberg, R. Mahy, P. Matthews, D. Wing. <a href=\"http://tools.ietf.org/html/rfc5389\"><cite>Session Traversal Utilities for NAT (STUN).</cite></a> October 2008. Internet RFC 5389. URL: <a href=\"http://tools.ietf.org/html/rfc5389\">http://tools.ietf.org/html/rfc5389</a>",
+   "SUITEB" : "<a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\"><cite>NSA Suite B Cryptography</cite></a>. URL: <a href=\"http://www.nsa.gov/ia/programs/suiteb_cryptography/\">http://www.nsa.gov/ia/programs/suiteb_cryptography/</a> ",
    "SUS3" : "Cathy Hughes. <a href=\"http://www.unix.org/single_unix_specification/\"><cite>The Single UNIX Specification, Version 3</cite></a>. 2004 URL: <a href=\"http://www.unix.org/single_unix_specification/\">http://www.unix.org/single_unix_specification/</a>",
    "SVG10" : "Jon Ferraiolo. <a href=\"http://www.w3.org/TR/2001/REC-SVG-20010904\"><cite>Scalable Vector Graphics (SVG) 1.0 Specification.</cite></a> 4 September 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-SVG-20010904\">http://www.w3.org/TR/2001/REC-SVG-20010904</a> ",
-   "SVG11" : "Dean Jackson; &#34276;&#27810; &#28147;; Jon Ferraiolo. <a href=\"http://www.w3.org/TR/2003/REC-SVG11-20030114\"><cite>Scalable Vector Graphics (SVG) 1.1 Specification.</cite></a> 14 January 2003. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2003/REC-SVG11-20030114\">http://www.w3.org/TR/2003/REC-SVG11-20030114</a> ",
+   "SVG11" : "Erik Dahlstr&#246;m; et al. <a href=\"http://www.w3.org/TR/2011/REC-SVG11-20110816/\"><cite>Scalable Vector Graphics (SVG) 1.1 (Second Edition).</cite></a> 16 August 2011. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2011/REC-SVG11-20110816/\">http://www.w3.org/TR/2011/REC-SVG11-20110816/</a> ",
    "SVG112" : "Erik Dahlstr&#246;m; et al. <a href=\"http://www.w3.org/TR/2010/WD-SVG11-20100622\"><cite>Scalable Vector Graphics (SVG) 1.1 (Second Edition).</cite></a> 22 June 2010. W3C Working Draft. (Work in progress). URL: <a href=\"http://www.w3.org/TR/2010/WD-SVG11-20100622\">http://www.w3.org/TR/2010/WD-SVG11-20100622</a> ",
    "SVG12" : "Craig Northway; Dean Jackson. <a href=\"http://www.w3.org/TR/2005/WD-SVG12-20050413\"><cite>Scalable Vector Graphics (SVG) Full 1.2 Specification.</cite></a> 13 April 2005. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2005/WD-SVG12-20050413\">http://www.w3.org/TR/2005/WD-SVG12-20050413</a> ",
    "SVG2REQS" : "Dean Jackson. <a href=\"http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422\"><cite>SVG 1.1/1.2/2.0 Requirements.</cite></a> 22 April 2002. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422\">http://www.w3.org/TR/2002/WD-SVG2Reqs-20020422</a> ",
@@ -543,14 +594,19 @@
    "THEGRID" : "Allen Hurlburt. <cite>Grid: A Modular System for the Design and Production of Newpapers, Magazines, and Books.</cite> Wiley. 1982. ISBN 0-471-28923-X.",
    "TIMESHEETS" : "Pablo Cesar; Dick Bulterman; Petri Vuorimaa. <a href=\"http://www.w3.org/TR/2008/WD-timesheets-20080110\"><cite>SMIL Timesheets 1.0.</cite></a> 10 January 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-timesheets-20080110\">http://www.w3.org/TR/2008/WD-timesheets-20080110</a> ",
    "TIMEZONE" : "Martin D&#252;rst; et al. <a href=\"http://www.w3.org/TR/2005/NOTE-timezone-20051013\"><cite>Working with Time Zones.</cite></a> 13 October 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-timezone-20051013\">http://www.w3.org/TR/2005/NOTE-timezone-20051013</a> ",
+   "TLS" : "T. Dierks, E. Rescorla. <a href=\"http://tools.ietf.org/html/rfc5246\"><cite>The Transport Layer Security (TLS) Protocol, Version 1.2.</cite></a> August 2008. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5246\">http://tools.ietf.org/html/rfc5246</a>",
    "Tobin" : "R. Tobin. <a href=\"http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054\"><cite>Infoset for external entities.</cite></a> 2000. URL: <a href=\"http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054\">http://lists.w3.org/Archives/Member/w3c-xml-core-wg/2000OctDec/0054</a> [XML Core mailing list, <a href=\"http://cgi.w3.org/MemberAccess/AccessRequest\">W3C Member Only</a>].",
+   "TOUCH-EVENTS": "Matt Brubeck; Sangwhan Moon; Doug Schepers; <a href=\"http://www.w3.org/TR/touch-events/\"><cite>Touch Events version 1</cite></a> URL: <a href=\"http://www.w3.org/TR/touch-events/\">http://www.w3.org/TR/touch-events</a>",
+   "TRACKING-COMPLIANCE" : "Justin Brookman; Sean Harvey; Erica Newland; Heather West. <a href=\"http://www.w3.org/TR/tracking-compliance/\"><cite>Tracking Compliance and Scope.</cite></a> 13 March 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-tracking-compliance-20120313/\">http://www.w3.org/TR/2011/WD-tracking-compliance-20120313/</a> ",
+   "TRACKING-DNT" : "Roy T. Fielding; David Singer. <a href=\"http://www.w3.org/TR/tracking-dnt/\"><cite>Tracking Preference Expression (DNT).</cite></a> 13 March 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-tracking-dnt-20120313/\">http://www.w3.org/TR/2011/WD-tracking-dnt-20120313/</a> ",
    "TRIPLEDES" : "<a href=\"http://www.ansi.org/\"><cite>ANSI X9.52: Triple Data Encryption Algorithm Modes of Operation. 1998</cite></a>. URL: <a href=\"http://www.ansi.org/\">http://www.ansi.org/</a>",
    "TTAF1-DFXP" : "Glenn Adams. <a href=\"http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116\"><cite>Timed Text (TT) Authoring Format 1.0&#160;&#8211; Distribution Format Exchange Profile (DFXP).</cite></a> 16 November 2006. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116\">http://www.w3.org/TR/2006/CR-ttaf1-dfxp-20061116</a> ",
    "TTAF1-REQ" : "Glenn Adams. <a href=\"http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427\"><cite>Timed Text (TT) Authoring Format 1.0 Use Cases and Requirements.</cite></a> 27 April 2006. W3C Note. URL: <a href=\"http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427\">http://www.w3.org/TR/2006/NOTE-ttaf1-req-20060427</a> ",
    "TURINGTEST" : "Matt May. <a href=\"http://www.w3.org/TR/2005/NOTE-turingtest-20051123\"><cite>Inaccessibility of CAPTCHA.</cite></a> 23 November 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-turingtest-20051123\">http://www.w3.org/TR/2005/NOTE-turingtest-20051123</a> ",
+   "TURN" : "P. Mahy, P. Matthews, J. Rosenberg. <a href=\"http://tools.ietf.org/html/rfc5766\"><cite>Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN).</cite></a> April 2010. Internet RFC 5766. URL: <a href=\"http://tools.ietf.org/html/rfc5766\">http://tools.ietf.org/html/rfc5766</a>",
    "TURTLE" : "David Beckett, Tim Berners-Lee. <a href=\"http://www.w3.org/TeamSubmission/turtle/\"><cite>Turtle: Terse RDF Triple Language.</cite></a> January 2008. W3C Team Submission. URL: <a href=\"http://www.w3.org/TeamSubmission/turtle/\">http://www.w3.org/TeamSubmission/turtle/</a> ",
    "TVWEB-URI-REQUIREMENTS" : "Gomar Thomas; Warner ten Kate; Craig Finseth. <a href=\"http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021\"><cite>TV Broadcast URI Schemes Requirements.</cite></a> 21 October 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021\">http://www.w3.org/TR/1999/NOTE-TVWeb-URI-Requirements-19991021</a> ",
-   "TYPED-ARRAYS" :  "Vladimir Vukicevic, Kenneth Russell. <a href=\"https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html\"><cite>Typed Arrays</cite></a> Khronos Working Draft. (Work in progress.) URL: <a href=\"https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html\">https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/TypedArray-spec.html</a> ",
+   "TYPED-ARRAYS" :  "David Herman, Kenneth Russell. <a href=\"https://www.khronos.org/registry/typedarray/specs/latest/\"><cite>Typed Arrays</cite></a> Khronos Working Draft. (Work in progress.) URL: <a href=\"https://www.khronos.org/registry/typedarray/specs/latest/\">https://www.khronos.org/registry/typedarray/specs/latest/</a> ",
    "TZDB" : "<a href='http://www.twinsun.com/tz/tz-link.htm'><cite>Time Zone Information Database.</cite></a> URL: <a href='http://www.twinsun.com/tz/tz-link.htm'>http://www.twinsun.com/tz/tz-link.htm</a>",
    "UAAG10" : "Jon Gunderson; Ian Jacobs; Eric Hansen. <a href=\"http://www.w3.org/TR/2002/REC-UAAG10-20021217\"><cite>User Agent Accessibility Guidelines 1.0.</cite></a> 17 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-UAAG10-20021217\">http://www.w3.org/TR/2002/REC-UAAG10-20021217</a> ",
    "UAAG10-TECHS" : "Ian Jacobs; Jon Gunderson; Eric Hansen. <a href=\"http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217\"><cite>Techniques for User Agent Accessibility Guidelines 1.0.</cite></a> 17 December 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217\">http://www.w3.org/TR/2002/NOTE-UAAG10-TECHS-20021217</a> ",
@@ -568,8 +624,19 @@
    "UNICODE310" : "The Unicode Consortium. <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0\"><cite>The Unicode Standard: Version 3.1.0.</cite></a> Addison Wesley Longman. 2000. ISBN 0-201-61633-5. For more information, consult the Unicode Consortium's home page at &lt;a href=&quot;http://www.unicode.org/&quot;&gt;http://www.unicode.org/&lt;/a&gt; URL: <a href=\"http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0\">http://www.unicode.org/unicode/standard/versions/enumeratedversions.html#Unicode_3_1_0</a> ",
    "UNICODE4" : "The Unicode Consortium. <a href=\"http://www.unicode.org/versions/Unicode4.1.0/\"><cite>The Unicode Standard, Version 4.1.0.</cite></a> Defined by: The Unicode Standard, Version 4.0 (Boston, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1), as amended by Unicode 4.0.1 (http://www.unicode.org/versions/Unicode4.0.1) and by Unicode 4.1.0 (http://www.unicode.org/versions/Unicode4.1.0) URL: <a href=\"http://www.unicode.org/versions/Unicode4.1.0/\">http://www.unicode.org/versions/Unicode4.1.0/</a> ",
    "UNICODE5" : "The Unicode Consortium. <a href=\"http://www.unicode.org/versions/Unicode5.1.0/\"><cite>The Unicode Standard, Version 5.1.0.</cite></a> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: <a href=\"http://www.unicode.org/versions/Unicode5.1.0/\">http://www.unicode.org/versions/Unicode5.1.0/</a> ",
+    "UPNP-AVARCH2" : "John Ritchie, Thomas Kuehnel, Wouter van der Beek, Jeffrey Kang. <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf\"><cite>UPnP AV Architecture:2</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-AVArchitecture-v2-20101231.pdf</a>",
+    "UPNP-AVT3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf\"><cite>AVTransport:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-AVTransport-v3-Service-20101231.pdf</a>",
+    "UPNP-CD4" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf\"><cite>ContentDirectory:4 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v4-Service-20101231.pdf</a>",
+    "UPNP-CM3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf\"><cite>ConnectionManager:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ConnectionManager-v3-Service-20101231.pdf</a>",
+    "UPNP-DEVICEARCH" : "<a href=\"http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf\"><cite>UPnP Device Architecture 1.0</cite></a>. 15 October 2008. UPnP Forum. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf\">http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20081015.pdf</a>",
+    "UPNP-DP1" : "<a href=\"http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf\"><cite>DeviceProtection:1 Service</cite></a>. 24 February 2011. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf\">http://www.upnp.org/specs/gw/UPnP-gw-DeviceProtection-v1-Service-20110224.pdf</a>",
+    "UPNP-MR3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf\"><cite>MediaRenderer:3 Device</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-MediaRenderer-v3-Device-20101231.pdf</a>",
+    "UPNP-MS4" : "<a href=\"http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf\"><cite>MediaServer:4 Device</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf\">http://upnp.org/specs/av/UPnP-av-MediaServer-v4-Device.pdf</a>",
+    "UPNP-RC3" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf\"><cite>RenderingControl:3 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. PDF document. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-RenderingControl-v3-Service-20101231.pdf</a>",
+    "UPNP-SR2" : "<a href=\"http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf\"><cite>ScheduledRecording:2 Service</cite></a>. 31 December 2010. UPnP Forum. Standardized DCP. For UPnP Version 1.0. URL: <a href=\"http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf\">http://www.upnp.org/specs/av/UPnP-av-ScheduledRecording-v2-Service-20101231.pdf</a>",
    "URI" : "T. Berners-Lee; R. Fielding; L. Masinter. <a href=\"http://www.ietf.org/rfc/rfc3986.txt\"><cite>Uniform Resource Identifiers (URI): generic syntax.</cite></a> January 2005. Internet RFC 3986. URL: <a href=\"http://www.ietf.org/rfc/rfc3986.txt\">http://www.ietf.org/rfc/rfc3986.txt</a> ",
    "URI-CLARIFICATION" : "URI Planning Interest Group. <a href=\"http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921\"><cite>URIs, URLs, and URNs: Clarifications and Recommendations 1.0.</cite></a> 21 September 2001. W3C Note. URL: <a href=\"http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921\">http://www.w3.org/TR/2001/NOTE-uri-clarification-20010921</a> ",
+   "URI-TEMPLATE" : "Joe Gregorio; Roy T. Fielding; Marc Hadley; Mark Nottingham; David Orchard. <a href=\"http://tools.ietf.org/html/draft-gregorio-uritemplate-08\"><cite>URI Template.</cite></a> 26 January 2012. Internet Draft (work in progress). URL: <a href=\"http://tools.ietf.org/html/draft-gregorio-uritemplate-08\">http://tools.ietf.org/html/draft-gregorio-uritemplate-08</a> ",
    "URN" : "R. Moats. <a href=\"http://www.ietf.org/rfc/rfc2141.txt\"><cite>URN Syntax.</cite></a> IETF RFC 2141. May 1997.  URL: <a href=\"http://www.ietf.org/rfc/rfc2141.txt\">http://www.ietf.org/rfc/rfc2141.txt</a>",
    "URN-OID" : "M. Mealling. <a href=\"http://www.ietf.org/rfc/rfc3061.txt\"><cite>A URN Namespace of Object Identifiers. </cite></a>. IETF RFC 3061. February 2001. URL: <a href=\"http://www.ietf.org/rfc/rfc3061.txt\">http://www.ietf.org/rfc/rfc3061.txt</a>",
    "UTF-8" : "F. Yergeau. <a href=\"http://www.ietf.org/rfc/rfc3629.txt\"><cite>UTF-8, a transformation format of ISO 10646</cite></a>. IETF RFC 3629. November 2003. URL: <a href=\"http://www.ietf.org/rfc/rfc3629.txt\">http://www.ietf.org/rfc/rfc3629.txt</a>",
@@ -587,6 +654,8 @@
    "VOICEXML21" : "Scott McGlashan; et al. <a href=\"http://www.w3.org/TR/2007/REC-voicexml21-20070619\"><cite>Voice Extensible Markup Language (VoiceXML) 2.1.</cite></a> 19 June 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-voicexml21-20070619\">http://www.w3.org/TR/2007/REC-voicexml21-20070619</a> ",
    "VOICEXML30" : "Paolo Baggia; et al. <a href=\"http://www.w3.org/TR/2008/WD-voicexml30-20081219\"><cite>Voice Extensible Markup Language (VoiceXML) 3.0.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-voicexml30-20081219\">http://www.w3.org/TR/2008/WD-voicexml30-20081219</a> ",
    "VXML30REQS" : "Emily Candell; Jeff Hoepfinger. <a href=\"http://www.w3.org/TR/2008/WD-vxml30reqs-20080808\"><cite>Voice Extensible Markup Language (VoiceXML) 3.0 Requirements.</cite></a> 8 August 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-vxml30reqs-20080808\">http://www.w3.org/TR/2008/WD-vxml30reqs-20080808</a> ",
+   "WAC-ORIENTATION-API" : "WAC Application Services Ltd. <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html\"><cite>Device APIs: The orientation module</cite></a> 28 January 2011. WAC 2.0 Proposed Release Version (PRV) URL: <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html\">http://specs.wacapps.net/2.0/jun2011/deviceapis/orientation.html</a> ",
+   "WAC-SENSOR-API" : "WAC Application Services Ltd. <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html\"><cite>Device APIs: The sensor module</cite></a> July 2011. WAC Ipanema Editor's Draft. URL: <a href=\"http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html\">http://specs.wacapps.net/2.0/jun2011/deviceapis/sensors.html</a> ",
    "WAI-AGE-LITERATURE" : "Andrew Arch. <a href=\"http://www.w3.org/TR/2008/WD-wai-age-literature-20080514\"><cite>Web Accessibility for Older Users: A Literature Review.</cite></a> 14 May 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-wai-age-literature-20080514\">http://www.w3.org/TR/2008/WD-wai-age-literature-20080514</a> ",
    "WAI-ARIA" : "Lisa Pappas; et al. <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-20090224\"><cite>Accessible Rich Internet Applications (WAI-ARIA) 1.0.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-20090224\">http://www.w3.org/TR/2009/WD-wai-aria-20090224</a> ",
    "WAI-ARIA-IMPLEMENTATION" : "Michael Cooper; Aaron Leventhal. <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224\"><cite>WAI-ARIA 1.0 User Agent Implementation Guide.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224\">http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224</a> ",
@@ -610,22 +679,26 @@
    "WEBCGM" : "Lofton Henderson; et al. <a href=\"http://www.w3.org/TR/2001/REC-WebCGM-20011217\"><cite>WebCGM 1.0 Second Release.</cite></a> 17 December 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-WebCGM-20011217\">http://www.w3.org/TR/2001/REC-WebCGM-20011217</a> ",
    "WEBCGM20" : "Benoit Bezaire; Lofton Henderson; David Cruikshank. <a href=\"http://www.w3.org/TR/2007/REC-webcgm20-20070130\"><cite>WebCGM 2.0.</cite></a> 30 January 2007. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2007/REC-webcgm20-20070130\">http://www.w3.org/TR/2007/REC-webcgm20-20070130</a> ",
    "WEBCGM21" : "Lofton Henderson; Benoit Bezaire. <a href=\"http://www.w3.org/TR/2009/WD-webcgm21-20090130\"><cite>WebCGM 2.1.</cite></a> 30 January 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-webcgm21-20090130\">http://www.w3.org/TR/2009/WD-webcgm21-20090130</a> ",
-   "WEBIDL" : "Cameron McCormack. <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\"><cite>Web IDL.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-WebIDL-20081219\">http://www.w3.org/TR/2008/WD-WebIDL-20081219</a> ",
+   "WEBIDL" : "Cameron McCormack. <a href=\"http://www.w3.org/TR/2011/WD-WebIDL-20110927/\"><cite>Web IDL.</cite></a> 27 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-WebIDL-20110927/\">http://www.w3.org/TR/2011/WD-WebIDL-20110927/</a> ",
    "WEBONT-REQ" : "Jeff Heflin. <a href=\"http://www.w3.org/TR/2004/REC-webont-req-20040210\"><cite>OWL Web Ontology Language Use Cases and Requirements.</cite></a> 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-webont-req-20040210\">http://www.w3.org/TR/2004/REC-webont-req-20040210</a> ",
    "WebBug-Wikipedia" : "<a href=\"http://en.wikipedia.org/wiki/Web_bug\"><cite>Wikipedia Web Bug definition</cite></a> URL: <a href=\"http://en.wikipedia.org/wiki/Web_bug\"> http://en.wikipedia.org/wiki/Web_bug</a> ",
+   "WEBRTC10" : "A Bergkvist; D Burnett; C Jennings; A Narayanan. <a href=\"http://www.w3.org/TR/2011/WD-webrtc-20111027/\"><cite>WebRTC 1.0.</cite></a> 27 October 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-webrtc-20111027/\">http://www.w3.org/TR/2011/WD-webrtc-20111027/</a> ",
+   "WEBSOCKETS-API" : "I. Hickson. <a href=\"http://www.w3.org/TR/2011/WD-websockets-20110929/\"><cite>The WebSocket API.</cite></a> 29 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-websockets-20110929/\">http://www.w3.org/TR/2011/WD-websockets-20110929/</a> ",
+   "WEBSOCKETS-PROTOCOL" : "C. Holmberg, S. Hakansson, G. Eriksson. <a href=\"http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt\"><cite>The WebSocket protocol.</cite></a> URL: <a href=\"http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt\">http://tools.ietf.org/id/draft-ietf-hybi-thewebsocketprotocol-09.txt</a> ",
    "WEBSTORAGE" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2009/WD-webstorage-20090910/\"><cite>Web Storage.</cite></a> 10 September 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-webstorage-20090910/\">http://www.w3.org/TR/2009/WD-webstorage-20090910/</a> ",
-   "WEBWORKERS" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2009/WD-workers-20091222/\"><cite>Web Workers.</cite></a> 22 December 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-workers-20091222/\">http://www.w3.org/TR/2009/WD-workers-20091222/</a> ",
+   "WEBWORKERS" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2011/WD-workers-20110901/\"><cite>Web Workers.</cite></a> 1 September 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-workers-20110901/\">http://www.w3.org/TR/2011/WD-workers-20110901/</a> ",
    "WICD" : "Daniel Appelquist; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICD-20070718\"><cite>WICD Core 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICD-20070718\">http://www.w3.org/TR/2007/CR-WICD-20070718</a> ",
    "WICDFULL" : "Timur Mehrvarz; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICDFull-20070718\"><cite>WICD Full 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICDFull-20070718\">http://www.w3.org/TR/2007/CR-WICDFull-20070718</a> ",
    "WICDMobile10" : "Timur Mehrvarz; et al. <a href=\"http://www.w3.org/TR/2007/CR-WICDMobile-20070718\"><cite>WICD Mobile 1.0.</cite></a> 18 July 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-WICDMobile-20070718\">http://www.w3.org/TR/2007/CR-WICDMobile-20070718</a> ",
-   "WIDGETS" : "Marcos Caceres. <a href=\"http://www.w3.org/TR/2009/CR-widgets-20091201/\"><cite>Widget Packaging and Configuration.</cite></a> 01 December 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-widgets-20091201/\">http://www.w3.org/TR/2009/CR-widgets-20091201/</a> ",
-   "WIDGETS-APIS" : "Marcos Caceres; Robin Berjon; Arve Bersvendsen. <a href=\"http://www.w3.org/TR/2009/CR-widgets-apis-20091222/\"><cite>The Widget Interface.</cite></a> 22 December 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/CR-widgets-apis-20091222/\">http://www.w3.org/TR/2009/CR-widgets-apis-20091222/</a> ",
-   "WIDGETS-DIGSIG" : "M. Caceres; F. Hirsch; M Priestley. <a href=\"http://www.w3.org/TR/2010/CR-widgets-digsig-20100624\"><cite>Digital Signatures for Widgets.</cite></a> 24 June 2010. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/CR-widgets-digsig-20100624\">http://www.w3.org/TR/2010/CR-widgets-digsig-20100624\</a> ",
-   "WIDGETS-LAND" : "Marcos Caceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\"><cite>Widgets 1.0: The Widget Landscape (Q1 2008).</cite></a> 14 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\">http://www.w3.org/TR/2008/WD-widgets-land-20080414</a> ",
-   "WIDGETS-PC-TESTS" : "Marcos Caceres, Kai Hendry. <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\"><cite>Test Suite for Packaging and Configuration.</cite></a> W3C Test Suite. (Work in progress.) URL: <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\">http://dev.w3.org/2006/waf/widgets/test-suite/</a> ",
-   "WIDGETS-PC-INTEROP" : "Marcos Cáceres, Samuel Santos, Daniel Silva. <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\"><cite>Implementation Report: Widgets Packaging and Configuration.</cite></a> 10 February 2011. URL: <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\">http://dev.w3.org/2006/waf/widgets/imp-report/</a> ",
-   "WIDGETS-REQS" : "Marcos Caceres. <a href=\"http://www.w3.org/TR/2009/WD-widgets-reqs-20090430\"><cite>Widgets 1.0: Requirements.</cite></a> 30 April 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-widgets-reqs-20090430\">http://www.w3.org/TR/2009/WD-widgets-reqs-20090430</a> ",
-   "WIDGETS-UPDATES" : "Marcos Caceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\"><cite>Widgets 1.0: Updates.</cite></a> 7 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\">http://www.w3.org/TR/2008/WD-widgets-updates-20081007</a> ",
+   "WIDGETS" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/widgets/\"><cite>Widget Packaging and XML Configuration</cite></a>. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/widgets/\">http://www.w3.org/TR/widgets/</a> ",
+   "WIDGETS-APIS" : "Marcos Cáceres <a href=\"http://www.w3.org/TR/widgets-api/\"><cite>Widget Interface.</cite></a> W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/widgets-api/\">http://www.w3.org/TR/widgets-api/</a> ",
+   "WIDGETS-DIGSIG" : "M. Cáceres; P. Bayers; Stuart Knightley; F. Hirsch; M Priestley. <a href=\"http://www.w3.org/TR/2010/CR-widgets-digsig-20100624\"><cite>Digital Signatures for Widgets.</cite></a> 24 June 2010. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/CR-widgets-digsig-20100624\">http://www.w3.org/TR/2010/CR-widgets-digsig-20100624</a> ",
+   "WIDGETS-LAND" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\"><cite>The Widget Landscape (Q1 2008).</cite></a> 14 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-land-20080414\">http://www.w3.org/TR/2008/WD-widgets-land-20080414</a> ",
+   "WIDGETS-PC-TESTS" : "Marcos Cáceres <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\"><cite>Test Suite for Packaging and XML Configuration.</cite></a> W3C Test Suite. URL: <a href=\"http://dev.w3.org/2006/waf/widgets/test-suite/\">http://dev.w3.org/2006/waf/widgets/test-suite/</a> ",
+   "WIDGETS-PC-INTEROP" : "Marcos Cáceres <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\"><cite>Implementation Report for Widgets Packaging and XML Configuration.</cite></a>. URL: <a href=\"http://dev.w3.org/2006/waf/widgets/imp-report/\">http://dev.w3.org/2006/waf/widgets/imp-report/</a> ",
+   "WIDGETS-REQS" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/widgets-reqs/\"><cite> Requirements For Standardizing Widgets.</cite></a>. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/widgets-reqs/\">http://www.w3.org/TR/widgets-reqs/</a> ",
+   "WIDGETS-UPDATES" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\"><cite>Widget Updates.</cite></a> 7 October 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-widgets-updates-20081007\">http://www.w3.org/TR/2008/WD-widgets-updates-20081007</a> ",
+   "WIDGETS-URI" : "Marcos Cáceres. <a href=\"http://www.w3.org/TR/2011/WD-widgets-uri-20110927\"><cite>Widget URI Scheme.</cite></a> 27 September 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-widgets-uri-20110927\">http://www.w3.org/TR/2011/WD-widgets-uri-20110927</a> ",
    "WINDOW" : "Ian Davis; Maciej Stachowiak. <a href=\"http://www.w3.org/TR/2006/WD-Window-20060407\"><cite>Window Object 1.0.</cite></a> 7 April 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-Window-20060407\">http://www.w3.org/TR/2006/WD-Window-20060407</a> ",
    "WORDNET-RDF" : "Aldo Gangemi; Guus Schreiber; Mark van Assem. <a href=\"http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619\"><cite>RDF/OWL Representation of WordNet.</cite></a> 19 June 2006. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619\">http://www.w3.org/TR/2006/WD-wordnet-rdf-20060619</a> ",
    "WS-ADDR-CORE" : "Martin Gudgin; Marc Hadley; Tony Rogers. <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-core-20060509\"><cite>Web Services Addressing 1.0 - Core.</cite></a> 9 May 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-ws-addr-core-20060509\">http://www.w3.org/TR/2006/REC-ws-addr-core-20060509</a> ",
@@ -652,11 +725,11 @@
    "WS-POLICY-GUIDELINES" : "Maryann Hondo; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112\"><cite>Web Services Policy 1.5 - Guidelines for Policy Assertion Authors.</cite></a> 12 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112\">http://www.w3.org/TR/2007/NOTE-ws-policy-guidelines-20071112</a> ",
    "WS-POLICY-PRIMER" : "Asir S Vedamuthu; et al. <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112\"><cite>Web Services Policy 1.5 - Primer.</cite></a> 12 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112\">http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112</a> ",
    "WS-RESOURCE-TRANSFER" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317\"><cite>Web Services Resource Transfer (WS-RT).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317\">http://www.w3.org/TR/2009/WD-ws-resource-transfer-20090317</a> ",
-   "WS-SECURITY11" : "A. Nadalin, C. Kaler, R. Monzillo, P. Hallam-Baker. <a href=\"http://www.oasis-open.org/specs/index.php#wssv1.1\"><cite>Web Services Security: SOAP Message Security 1.1 (WS-Security 2004)</cite></a>. OASIS Standard, 1 February 2006. URL: <a href=\"http://www.oasis-open.org/specs/index.php#wssv1.1\">http://www.oasis-open.org/specs/index.php#wssv1.1</a> ",
-    "WS-SECURECONVERSATION13" :   "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"http://www.oasis-open.org/specs/index.php#wssecconv1.3\"><cite>WS-SecureConversation 1.3</cite></a>. OASIS Standard, 1 March 2007. URL: <a href=\"http://www.oasis-open.org/specs/index.php#wssecconv1.3\">http://www.oasis-open.org/specs/index.php#wssecconv1.3</a> ",
-    "WS-SECURITYPOLICY12" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"http://www.oasis-open.org/specs/index.php#wssecpolv1.2\"><cite>WS-SecurityPolicy 1.2, OASIS Standard</cite></a>. 1 July 2007. URL: <a href=\"http://www.oasis-open.org/specs/index.php#wssecpolv1.2\">http://www.oasis-open.org/specs/index.php#wssecpolv1.2</a> ",
+   "WS-SECURITY11" : "A. Nadalin, C. Kaler, R. Monzillo, P. Hallam-Baker. <a href=\"http://www.oasis-open.org/standards#wssv1.1\"><cite>Web Services Security: SOAP Message Security 1.1 (WS-Security 2004)</cite></a>. OASIS Standard, 1 February 2006. URL: <a href=\"http://www.oasis-open.org/standards#wssv1.1\">http://www.oasis-open.org/standards#wssv1.1</a> ",
+    "WS-SECURECONVERSATION13" :   "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"http://www.oasis-open.org/standards#wssecconv1.3\"><cite>WS-SecureConversation 1.3</cite></a>. OASIS Standard, 1 March 2007. URL: <a href=\"http://www.oasis-open.org/standards#wssecconv1.3\">http://www.oasis-open.org/standards#wssecconv1.3</a> ",
+    "WS-SECURITYPOLICY12" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist. <a href=\"http://www.oasis-open.org/standards#wssecpolv1.2\"><cite>WS-SecurityPolicy 1.2, OASIS Standard</cite></a>. 1 July 2007. URL: <a href=\"http://www.oasis-open.org/standards#wssecpolv1.2\">http://www.oasis-open.org/standards#wssecpolv1.2</a> ",
     "WS-TRANSFER" : "Ashok Malhotra; et al. <a href=\"http://www.w3.org/TR/2009/WD-ws-transfer-20090317\"><cite>Web Services Transfer (WS-Transfer).</cite></a> 17 March 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-ws-transfer-20090317\">http://www.w3.org/TR/2009/WD-ws-transfer-20090317</a> ",
-    "WS-TRUST13" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist.  <a href=\"http://www.oasis-open.org/specs/index.php#wstrustv1.3\"><cite>WS-Trust 1.3</cite></a>. OASIS Standard, 19 March 2007. URL: <a href=\"http://www.oasis-open.org/specs/index.php#wstrustv1.3\">http://www.oasis-open.org/specs/index.php#wstrustv1.3</a> ",
+    "WS-TRUST13" : "A. Nadalin, M. Goodner, M. Gudgin, A. Barbir, H. Granqvist.  <a href=\"http://www.oasis-open.org/standards#wstrustv1.3\"><cite>WS-Trust 1.3</cite></a>. OASIS Standard, 19 March 2007. URL: <a href=\"http://www.oasis-open.org/standards#wstrustv1.3\">http://www.oasis-open.org/standards#wstrustv1.3</a> ",
     "WSS-USERNAME11" : "A. Nadalin, C. Kaler, R. Monzillo, P. Hallam-Baker. <a href=\"http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf\"><cite>Web Services Security UsernameToken Profile 1.1</cite></a>. OASIS Standard Specification, 1 February 2006. URL: <a href=\"http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf\">http://www.oasis-open.org/committees/download.php/16782/wss-v1.1-spec-os-UsernameTokenProfile.pdf</a> ",
    "WSA-REQS" : "Sharad Garg; et al. <a href=\"http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211\"><cite>Web Services Architecture Requirements.</cite></a> 11 February 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211\">http://www.w3.org/TR/2004/NOTE-wsa-reqs-20040211</a> ",
    "WSC-THREATS" : "Thomas Roessler. <a href=\"http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101\"><cite>Web User Interaction: Threat Trees.</cite></a> 1 November 2007. W3C Note. URL: <a href=\"http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101\">http://www.w3.org/TR/2007/NOTE-wsc-threats-20071101</a> ",
@@ -684,7 +757,7 @@
    "XBC-PROPERTIES" : "Santiago Pericas-Geertsen; Mike Cokus. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331\"><cite>XML Binary Characterization Properties.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-properties-20050331</a> ",
    "XBC-USE-CASES" : "Santiago Pericas-Geertsen; Mike Cokus. <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331\"><cite>XML Binary Characterization Use Cases.</cite></a> 31 March 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331\">http://www.w3.org/TR/2005/NOTE-xbc-use-cases-20050331</a> ",
    "XBL" : "Ian Hickson. <a href=\"http://www.w3.org/TR/2007/CR-xbl-20070316\"><cite>XML Binding Language (XBL) 2.0.</cite></a> 16 March 2007. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/CR-xbl-20070316\">http://www.w3.org/TR/2007/CR-xbl-20070316</a> ",
-   "XBL-PRIMER" : "Lachlan Hunt; Marcos Caceres. <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\"><cite>XBL 2.0 Primer: An Introduction for Developers.</cite></a> 18 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\">http://www.w3.org/TR/2007/WD-xbl-primer-20070718</a> ",
+   "XBL-PRIMER" : "Lachlan Hunt; Marcos Cáceres. <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\"><cite>XBL 2.0 Primer: An Introduction for Developers.</cite></a> 18 July 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xbl-primer-20070718\">http://www.w3.org/TR/2007/WD-xbl-primer-20070718</a> ",
    "XFORMS-11-REQ" : "John Boyer; Roland Merrick. <a href=\"http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831\"><cite>XForms 1.1 Requirements.</cite></a> 31 August 2004. W3C Note. URL: <a href=\"http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831\">http://www.w3.org/TR/2004/NOTE-xforms-11-req-20040831</a> ",
    "XFORMS-BASIC" : "T. V. Raman; Micah Dubinko. <a href=\"http://www.w3.org/TR/2003/CR-xforms-basic-20031014\"><cite>XForms 1.0 Basic Profile.</cite></a> 14 October 2003. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2003/CR-xforms-basic-20031014\">http://www.w3.org/TR/2003/CR-xforms-basic-20031014</a> ",
    "XFORMS-FOR-HTML" : "John M. Boyer. <a href=\"http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219\"><cite>XForms for HTML.</cite></a> 19 December 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219\">http://www.w3.org/TR/2008/WD-XForms-for-HTML-20081219</a> ",
@@ -702,7 +775,7 @@
    "XHTML-MODULARIZATION11-2e" : "Shane McCarron. <a href=\"http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729\"><cite>XHTML&#8482; Modularization 1.1 Second Edition.</cite></a> 29 July 2010. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729\">http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729</a> ",
    "XHTML-PRINT" : "Jim Bigelow; Melinda Grant. <a href=\"http://www.w3.org/TR/2006/REC-xhtml-print-20060920\"><cite>XHTML-Print.</cite></a> 20 September 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xhtml-print-20060920\">http://www.w3.org/TR/2006/REC-xhtml-print-20060920</a> ",
    "XHTML-PROF-REQ" : "David Raggett; Ted Wugofski; Peter Stark. <a href=\"http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906\"><cite>XHTML&#8482; Document Profile Requirements.</cite></a> 6 September 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906\">http://www.w3.org/TR/1999/WD-xhtml-prof-req-19990906</a> ",
-   "XHTML-RDFA" : "Shane McCarron; et. al. <a href=\"http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331\"><cite>XHTML+RDFa 1.1.</cite></a> 31 March 2011. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331\">http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331</a> ",
+   "XHTML-RDFA" : "Shane McCarron; et. al. <a href=\"http://www.w3.org/TR/2012/PR-xhtml-rdfa-20120508/\"><cite>XHTML+RDFa 1.1.</cite></a> 8 May 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-xhtml-rdfa-20120508/\">http://www.w3.org/TR/2012/PR-xhtml-rdfa-20120508/</a> ",
    "XHTML-RDFA-PRIMER" : "Mark Birbeck; Ben Adida. <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\"><cite>RDFa Primer.</cite></a> 14 October 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014\">http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014</a> ",
    "XHTML-RDFA-SCENARIOS" : "Michael Hausenblas; Ben Adida. <a href=\"http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330\"><cite>RDFa Use Cases: Scenarios for Embedding RDF in HTML.</cite></a> 30 March 2007. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330\">http://www.w3.org/TR/2007/WD-xhtml-rdfa-scenarios-20070330</a> ",
    "XHTML-ROADMAP" : "Steven Pemberton; David Raggett; Masayasu Ishikawa. <a href=\"http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108\"><cite>HTML Working Group Roadmap.</cite></a> 8 November 2000. W3C Note. URL: <a href=\"http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108\">http://www.w3.org/TR/2000/NOTE-xhtml-roadmap-20001108</a> ",
@@ -730,7 +803,7 @@
    "XML-BLUEBERRY-REQ" : "John Cowan. <a href=\"http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921\"><cite>XML Blueberry Requirements.</cite></a> 21 September 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921\">http://www.w3.org/TR/2001/WD-xml-blueberry-req-20010921</a> ",
    "XML-C14N" : "John Boyer. <a href=\"http://www.w3.org/TR/2001/REC-xml-c14n-20010315\"><cite>Canonical XML Version 1.0.</cite></a> 15 March 2001. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2001/REC-xml-c14n-20010315\">http://www.w3.org/TR/2001/REC-xml-c14n-20010315</a> ",
    "XML-C14N11" : "John Boyer, Glenn Marcy. <a href=\"http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/\"><cite>Canonical XML Version 1.1.</cite></a> 2 May 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/\">http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/</a> ",
-    "XML-C14N20" : "John Boyer; Glen Marcy; Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/WD-xml-c14n2-20110421/\"><cite>Canonical XML Version 2.0.</cite></a> 21 April 2011. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-xml-c14n2-20110421/\">http://www.w3.org/TR/2011/WD-xml-c14n2-20110421/</a>",
+    "XML-C14N20" : "John Boyer; Glen Marcy; Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/\"><cite>Canonical XML Version 2.0.</cite></a> 24 January 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/\">http://www.w3.org/TR/2012/CR-xml-c14n2-20120124/</a>", 
    "XML-CANONICAL-REQ" : "James Tauber; Joel Nava. <a href=\"http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605\"><cite>XML Canonicalization Requirements.</cite></a> 5 June 1999. W3C Note. URL: <a href=\"http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605\">http://www.w3.org/TR/1999/NOTE-xml-canonical-req-19990605</a> ",
    "XML-ENCRYPTION-REQ" : "Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304\"><cite>XML Encryption Requirements.</cite></a> 4 March 2002. W3C Note. URL: <a href=\"http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304\">http://www.w3.org/TR/2002/NOTE-xml-encryption-req-20020304</a> ",
    "XML-ENTITY-NAMES" : "Patrick Ion; David Carlisle. <a href=\"http://www.w3.org/TR/2008/WD-xml-entity-names-20080721\"><cite>XML Entity definitions for Characters.</cite></a> 21 July 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xml-entity-names-20080721\">http://www.w3.org/TR/2008/WD-xml-entity-names-20080721</a> ",
@@ -759,26 +832,34 @@
    "XML11" : "Eve Maler; et al. <a href=\"http://www.w3.org/TR/2006/REC-xml11-20060816\"><cite>Extensible Markup Language (XML) 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2006/REC-xml11-20060816\">http://www.w3.org/TR/2006/REC-xml11-20060816</a> ",
    "XML11SCHEMA10" : "Henry S. Thompson. <a href=\"http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511\"><cite>Processing XML 1.1 documents with XML Schema 1.0 processors.</cite></a> 11 May 2005. W3C Note. URL: <a href=\"http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511\">http://www.w3.org/TR/2005/NOTE-xml11schema10-20050511</a> ",
    "XMLBASE" : "Jonathan Marsh, Richard Tobin. <a href=\"http://www.w3.org/TR/2009/REC-xmlbase-20090128/\"><cite>XML Base (Second Edition).</cite></a> 28 January 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-xmlbase-20090128/\">http://www.w3.org/TR/2009/REC-xmlbase-20090128/</a> ",
-   "XMLDSIG-BESTPRACTICES" : "Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100204/\"><cite>XML Signature Best Practices.</cite></a> 4 February 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100204/\">http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100204/</a> ",
+   "XMLDSIG-BESTPRACTICES" : "Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100831/\"><cite>XML Signature Best Practices.</cite></a> 31 August 2010. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100831/\">http://www.w3.org/TR/2010/WD-xmldsig-bestpractices-20100831/</a> ",
    "XMLDSIG-CORE2002" : "Joseph Reagle; et al. <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/\"><cite>XML Signature Syntax and Processing.</cite></a> 12 February 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/\">http://www.w3.org/TR/2002/REC-xmldsig-core-20020212</a> ",
    "XMLDSIG-CORE" : "Joseph Reagle; et al. <a href=\"http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/\"><cite>XML Signature Syntax and Processing (Second Edition).</cite></a> 10 June 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/\">http://www.w3.org/TR/2008/REC-xmldsig-core-20080610</a> ",
     "XMLDSIG-CORE1" : "D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/\"><cite>XML Signature Syntax and Processing Version 1.1.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/\">http://www.w3.org/TR/2011/CR-xmldsig-core1-20110303/</a> ",
-    "XMLDSIG-CORE2" : "Mark Bartel; John Boyer; Barb Fox et al. <a href=\"http://www.w3.org/TR/2011/WD-xmldsig-core2-20110421/\"><cite>XML Signature Syntax and Processing Version 2.0</cite></a>. 21 April 2011. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/2011/WD-xmldsig-core2-20110421/\">http://www.w3.org/TR/2011/WD-xmldsig-core2-20110421/</a>",
+    "XMLDSIG-CORE1-CHGS" : "Frederick Hirsch. <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-explain/Overview.html\"><cite>Functional explanation of changes in XML Signature 1.1</cite></a>. W3C Editors Draft (Note Track - Work in Progress). URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmldisg-core1-explain/Overview.html\">http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core1-explain/Overview.html</a> ",
+    "XMLDSIG-CORE2" : "Mark Bartel; John Boyer; Barb Fox et al. <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/\"><cite>XML Signature Syntax and Processing Version 2.0</cite></a>. 24 January 2012.  W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/\">http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124/</a>", 
     "XMLDSIG-GARCIA" :  "Raúl Benito García. <a href=\"http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf\"><cite>Verificación De Firmas Digitales En Documentos XML De Tamaño Arbitrario.</cite></a> December 2006. URL: <a href=\"http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf\">http://www.w3.org/2008/xmlsec/papers/TFCFirmasdigitalesenXML-11-10-2007.pdf</a>",
     "XMLDSIG-COMPLEXITY" : "Brad Hill. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/\"><cite>Complexity as the Enemy of Security: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption.</cite></a>. 25-26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/\">http://www.w3.org/2007/xmlsec/ws/papers/04-hill-isecpartners/</a> ",
    "XMLDSIG-SEMANTICS" : "Sebastian Gajek, Lijun Liao, and Jörg Schwenk. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/\"><cite> Towards a Semantic of XML Signature: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption </cite></a> 25-26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/\">http://www.w3.org/2007/xmlsec/ws/papers/07-gajek-rub/</a> ",
     "XMLDSIG-THOMPSON": "Henry Thompson. <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/\"><cite>Radical proposal for Vnext of XML Signature: Position Paper for W3C Workshop on Next Steps for XML Signature and XML Encryption</cite></a> 26 September 2007. W3C Workshop. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/\"> http://www.w3.org/2007/xmlsec/ws/papers/20-thompson/</a> ",
-   "XMLDSIG-XPATH" : "Pratik Datta. Frederick Hirsch, Meiko Jensen <a href=\"http://www.w3.org/TR/2011/WD-xmldsig-xpath-20110421/\"><cite>XML Signature Streaming Profile of XPath 1.0</cite></a> 21 April 2011. W3C Last Call Working draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmldsig-xpath-20110421/\">http://www.w3.org/TR/2011/WD-xmldsig-xpath-20110421/</a> ",
+   "XMLDSIG-XPATH" : "Pratik Datta. Frederick Hirsch, Meiko Jensen <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/\"><cite>XML Signature Streaming Profile of XPath 1.0</cite>.</a> 24 January 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/\">http://www.w3.org/TR/2012/CR-xmldsig-xpath-20120124/</a>", 
    "XMLDSIG-XPATH-FILTER2" : "Merlin Hughes; John Boyer; Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/\"><cite>XML-Signature XPath Filter 2.0.</cite></a> 8 November 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/\">http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/</a> ",
    "XMLDSIG-PROPERTIES" : "Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/\"><cite>XML Signature Properties.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/\">http://www.w3.org/TR/2011/CR-xmldsig-properties-20110303/</a> ",
    "XMLDSIG-REQUIREMENTS" : "Joseph Reagle Jr. <a href=\"http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014\"><cite>XML-Signature Requirements.</cite></a> 14 October 1999. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014\">http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014</a> ",
    "XMLDSIG-SIMPLIFY" : "Pratik Datta; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226\"><cite>XML Signature Transform Simplification: Requirements and Design.</cite></a> 26 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226\">http://www.w3.org/TR/2009/WD-xmldsig-simplify-20090226</a> ",
    "XMLDSIG2ED-TESTS" : "Konrad Lanz; Sean Mullan; Juan Carlos Cruellas. <a href=\"http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610\"><cite>Test Cases for C14N 1.1 and XMLDSig Interoperability.</cite></a> 10 June 2008. W3C Note. URL: <a href=\"http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610\">http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610</a> ",
+   "XMLENC-CBC-ATTACK" : "Tibor Jager; Juraj Somorovsky. <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf\"><cite>How to Break XML Encryption</cite></a> 17-21 October 2011. CCS' 11, ACM. URL: <a href=\"http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf\">http://www.nds.rub.de/media/nds/veroeffentlichungen/2011/10/22/HowToBreakXMLenc.pdf</a> ",
+    "XMLENC-CBC-ATTACK-COUNTERMEASURES" : "Juraj Somorovsky, J&ouml;rg Schwenk. <a href=\"http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf\"><cite>Technical Analysis of Countermeasures against Attack on XML Encryption - or - Just Another Motivation for Authenticated Encryption</cite.></a>. 2011.  URL: <a href=\"http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf\">http://www.w3.org/2008/xmlsec/papers/xmlEncCountermeasuresW3C.pdf</a>",
+   "XMLENC-CREF2" : "Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/\">Encryption 1.1 CipherReference Processing Using 2.0 Transforms</cite></a> 13 March 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\" http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/\">http://www.w3.org/TR/2012/CR-xmlenc-transform20-20120313/</a>",
    "XMLENC-CORE" : "Donald Eastlake; Joseph Reagle. <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/\"><cite>XML Encryption Syntax and Processing.</cite></a> 10 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/\">http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/</a> ",
-    "XMLENC-CORE1" : "J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. <a href=\"http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/\"><cite>XML Encryption Syntax and Processing Version 1.1.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/\">http://www.w3.org/TR/2011/CR-xmlenc-core1-20110303/</a> ",
+    "XMLENC-CORE1" : "J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/\"><cite>XML Encryption Syntax and Processing Version 1.1.</cite></a> 13 March 2012. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/\">http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313/</a> ", 
+    "XMLENC-CORE1-CHGS" : "Frederick Hirsch. <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html\"><cite>Functional explanation of changes in XML Encryption 1.1</cite></a>. W3C Editors Draft (Note Track - Work in Progress). URL: <a href=\"http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html\">http://www.w3.org/2008/xmlsec/Drafts/xmlenc-core1-explain/Overview.html</a> ",
    "XMLENC-DECRYPT" : "Takeshi Imamura; Merlin Hughes; Hiroshi Maruyama. <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210\"><cite>Decryption Transform for XML Signature.</cite></a> 10 December 2002. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210\">http://www.w3.org/TR/2002/REC-xmlenc-decrypt-20021210</a> ",
+   "XMLENC11-TESTCASES" : "Pratik Datta, Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/\"><cite>Test Cases for XML Encryption 1.1.</cite></a> 5 January 2012. W3C First Public Working Draft (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/\">http://www.w3.org/TR/2012/WD-xmlenc-core1-testcases-20120105/</a>",
+   "XHR" : "Anne van Kesteren. <a href='http://www.w3.org/TR/XMLHttpRequest/'>XMLHttpRequest</a>",
    "XMLHTTPREQUEST" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415\"><cite>The XMLHttpRequest Object.</cite></a> 15 April 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415\">http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415</a> ",
    "XMLHTTPREQUEST2" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930\"><cite>XMLHttpRequest Level 2.</cite></a> 30 September 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930\">http://www.w3.org/TR/2008/WD-XMLHttpRequest2-20080930</a> ",
+   "XMLHTTPREQUEST3" : "Anne van Kesteren. <a href=\"http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803\"><cite>XMLHttpRequest</cite></a> 3 August 2010. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803\">http://www.w3.org/TR/2010/CR-XMLHttpRequest-20100803</a> ",
    "XMLP-REQS" : "Oisin Hurley; et al. <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728\"><cite>XML Protocol (XMLP) Requirements.</cite></a> 28 July 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728\">http://www.w3.org/TR/2003/NOTE-xmlp-reqs-20030728</a> ",
    "XMLP-SCENARIOS" : "John Ibbotson. <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730\"><cite>SOAP Version 1.2 Usage Scenarios.</cite></a> 30 July 2003. W3C Note. URL: <a href=\"http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730\">http://www.w3.org/TR/2003/NOTE-xmlp-scenarios-20030730</a> ",
    "XMLSCHEMA-0" : "David C. Fallside; Priscilla Walmsley. <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/\"><cite>XML Schema Part 0: Primer Second Edition.</cite></a> 28 October 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/\">http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/</a> ",
@@ -790,13 +871,13 @@
    "XMLSCHEMA-PATTERNS" : "Jonathan Calladine; et al. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328\"><cite>Basic XML Schema Patterns for Databinding Version 1.0.</cite></a> 28 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328\">http://www.w3.org/TR/2008/WD-xmlschema-patterns-20080328</a> ",
    "XMLSCHEMA-PATTERNS-ADVANCED" : "George Cowe; et al. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328\"><cite>Advanced XML Schema Patterns for Databinding Version 1.0.</cite></a> 28 March 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328\">http://www.w3.org/TR/2008/WD-xmlschema-patterns-advanced-20080328</a> ",
    "XMLSCHEMA-REF" : "Asir S. Vedamuthu; Mary Holstege. <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117\"><cite>W3C XML Schema Definition Language (XSD): Component Designators.</cite></a> 17 November 2008. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117\">http://www.w3.org/TR/2008/WD-xmlschema-ref-20081117</a> ",
-   "XMLSCHEMA11-1" : "C. M. Sperberg-McQueen; Henry S. Thompson; Shudi Gao. <a href=\"http://www.w3.org/TR/2009/WD-xmlschema11-1-20090130\"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.</cite></a> 30 January 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmlschema11-1-20090130\">http://www.w3.org/TR/2009/WD-xmlschema11-1-20090130</a> ",
-   "XMLSCHEMA11-2" : "Henry S. Thompson; et al. <a href=\"http://www.w3.org/TR/2009/WD-xmlschema11-2-20090130\"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 30 January 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmlschema11-2-20090130\">http://www.w3.org/TR/2009/WD-xmlschema11-2-20090130</a> ",
-   "XMLSEC-ALGORITHMS" : "Thomas Roessler; Frederick Hirsch; Kelvin Yiu. <a href=\"http://www.w3.org/TR/2010/WD-xmlsec-algorithms-20100513/\"><cite>XML Security Algorithm Cross-Reference.</cite></a> 21 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-xmlsec-algorithms-20100513/\">http://www.w3.org/TR/2010/WD-xmlsec-algorithms-20100513/</a> ",
+   "XMLSCHEMA11-1" : "C. M. Sperberg-McQueen; Henry S. Thompson; Shudi Gao. <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/\"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 1: Structures.</cite></a> 5 April 2012. W3C Recommendation URL: <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/\">http://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/</a> ",
+   "XMLSCHEMA11-2" : "Henry S. Thompson; et al. <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/\"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 5 April 2012. W3C Recommendation URL: <a href=\"http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/\">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a> ",
+   "XMLSEC-ALGORITHMS" : "Thomas Roessler; Frederick Hirsch; Kelvin Yiu. <a href=\"http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/\"><cite>XML Security Algorithm Cross-Reference.</cite></a> 5 January 2012. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/\">http://www.w3.org/TR/2012/WD-xmlsec-algorithms-20120105/</a> ",
    "XMLSEC-DERIVEDKEYS" : "Magnus Nystr&#246;m. <a href=\"http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226/\"><cite>XML Security Derived Keys.</cite></a> 26 February 2009. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226\">http://www.w3.org/TR/2009/WD-xmlsec-derivedkeys-20090226</a> ",
     "XMLSEC-GHCIPHERS" : "Magnus Nystr&#246;m; Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/\"><cite>XML Security Generic Hybrid Ciphers.</cite></a> 3 March 2011. W3C Candidate Recommendation. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/\">http://www.w3.org/TR/2011/CR-xmlsec-generic-hybrid-20110303/</a> ",
    "XMLSEC-NEXTSTEPS-2007" : "Frederick Hirsch; Thomas Roessler. <a href=\"http://www.w3.org/2007/xmlsec/ws/report.html\"><cite>Workshop Report W3C Workshop on Next Steps for XML Signature and XML Encryption</cite></a> 25-26 September 2007. W3C Workshop Report. URL: <a href=\"http://www.w3.org/2007/xmlsec/ws/report.html\">http://www.w3.org/2007/xmlsec/ws/report.html</a>",
-   "XMLSEC-RELAXNG" : "Makoto Murata, Frederick Hirsch. <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/\"><cite>XML Security RELAX NG Schemas.</cite></a> 21 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/\">http://www.w3.org/TR/2011/WD-xmlsec-rngschema-20110421/</a>",
+   "XMLSEC-RELAXNG" : "Makoto Murata, Frederick Hirsch. <a href=\"http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/\"><cite>XML Security RELAX NG Schemas.</cite></a> 24 January 2012. W3C Working Group Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/\">http://www.w3.org/TR/2012/NOTE-xmlsec-rngschema-20120124/</a>",
    "XMLSEC11-REQS" : "Frederick Hirsch, Thomas Roessler. <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/\"><cite>XML Security 1.1 Requirements and Design Considerations.</cite></a> 3 March 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/\">http://www.w3.org/TR/2011/WD-xmlsec-reqs-20110303/</a> ",
    "XMLSEC2-REQS" : "Frederick Hirsch, Pratik Datta. <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/\"><cite>XML Security 2.0 Requirements and Design Considerations.</cite></a> 21 April 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/\">http://www.w3.org/TR/2011/WD-xmlsec-reqs2-20110421/</a> ",
    "XMLSTYLE" : "James Clark. <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\"><cite>Associating Style Sheets with XML documents.</cite></a> 29 June 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/1999/06/REC-xml-stylesheet-19990629\">http://www.w3.org/1999/06/REC-xml-stylesheet-19990629</a> ",
@@ -851,5 +932,5 @@
    "XSLT21" : "Michael Kay. <a href=\"http://www.w3.org/TR/2010/WD-xslt-21-20100511/\"><cite>XSL Transformations (XSLT) Version 2.1.</cite></a> 11 May 2011. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2010/WD-xslt-21-20100511/\">http://www.w3.org/TR/2010/WD-xslt-21-20100511/</a> ",
    "XSLT20REQ" : "Steve Muench; Mark Scardina. <a href=\"http://www.w3.org/TR/2001/WD-xslt20req-20010214\"><cite>XSLT Requirements Version 2.0.</cite></a> 14 February 2001. W3C Working Draft. (Work in progress.) URL: <a href=\"http://www.w3.org/TR/2001/WD-xslt20req-20010214\">http://www.w3.org/TR/2001/WD-xslt20req-20010214</a> ",
    "YACC" : "S. C. Johnson. <cite>YACC - Yet another compiler compiler.</cite> Murray Hill. 1975. Technical Report.",
-   "ZHMARK" : "<cite>&#26631;&#28857;&#31526;&#21495;&#29992;&#27861; (Punctuation Mark Usage).</cite> 1995. &#20013;&#21326;&#20154;&#27665;&#20849;&#21644;&#22269;&#22269;&#23478;&#26631;&#20934; ",
+   "ZHMARK" : "<cite>&#26631;&#28857;&#31526;&#21495;&#29992;&#27861; (Punctuation Mark Usage).</cite> 1995. &#20013;&#21326;&#20154;&#27665;&#20849;&#21644;&#22269;&#22269;&#23478;&#26631;&#20934; "
 };
Binary file rdf-concepts/Graph-ex.gif has changed
--- a/rdf-concepts/index.html	Wed May 02 07:19:20 2012 -0700
+++ b/rdf-concepts/index.html	Tue May 15 10:10:48 2012 -0700
@@ -4,8 +4,9 @@
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     <title>RDF 1.1 Concepts and Abstract Syntax</title>
     <style type="text/css">
-.figure { font-weight: bold; text-align: center; }
-table.xsd-types td, table.xsd-types th { border: 1px solid #ddd; padding: 0.1em 0.5em; }
+.figure { text-align: center; }
+.figure a[href]:hover { background: transparent; }
+table td, table th { border: 1px solid #ddd; padding: 0.2em 0.5em; }
     </style>
     <script src='../ReSpec.js/js/respec.js' class='remove'></script>
     <script class='remove'>
@@ -138,13 +139,6 @@
 <section id="section-Introduction" class="informative">
     <h2>Introduction</h2>
 
-    <p class="issue">This document reflects current progress of the RDF Working
-      Group towards updating the
-      <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/">2004
-      version of <em>RDF Concepts and Abstract Syntax</em></a>. The
-      editors expect to work on a number of issues, some of which are
-      listed in boxes like this throughout the document.</p>
-
     <p>The <em>Resource Description Framework</em> (RDF) is a framework
     for representing information in the Web.</p>
 
@@ -180,7 +174,7 @@
     node-arc-node link; hence the term “graph”.</p>
 
     <div class="figure">
-      <img src="Graph-ex.gif" alt="image of the RDF triple comprising (subject, predicate, object)" />
+      <a href="rdf-graph.png"><img src="rdf-graph.svg" alt="An RDF graph with two nodes (Subject and Object) and a triple connecting them (Predicate)" /></a>
     </div>
 
     <p>There may be three kinds of <a title="node">nodes</a> in an
@@ -253,12 +247,18 @@
     <code>http://www.w3.org/2000/01/rdf-schema#</code>.</li>
 
     <li>A good way of communicating the intended referent to the world
-    is to set up the IRI so that it resolves to such a document.</li>
+    is to set up the IRI so that it
+    <a href="http://www.w3.org/TR/webarch/#uri-dereference">dereferences</a>
+    [[WEBARCH]] to such a document.</li>
 
     <li>Such a document can, in fact, be an <a>RDF document</a>
     that describes the denoted resource by means of
     <a title="RDF statement">RDF statements</a>.</li>
     </ul>
+</section>
+
+<section id="vocabularies">
+    <h3>RDF Vocabularies and Namespace IRIs</h3>
 
     <p>An <dfn>RDF vocabulary</dfn> is a collection of <a title="IRI">IRIs</a>
     with clearly established <a title="referent">referents</a>
@@ -267,6 +267,36 @@
     RDF Schema can itself be used to define and document additional
     RDF vocabularies. Some such vocabularies are mentioned in the
     Primer [[RDF-PRIMER]].</p>
+
+    <p class="issue">The material below may be moved to the new
+    <em>RDF 1.1 Primer</em> document once it becomes available.</p>
+
+    <p>The <a title="IRI">IRIs</a> in an <a>RDF vocabulary</a> often share
+    a common substring known as a <dfn>namespace IRI</dfn>.
+    Some namespace IRIs are associated by convention with a short name
+    known as a <dfn>namespace prefix</dfn>. Some examples:
+
+    <table rules="all" summary="Some example namespace prefixes and IRIs">
+      <tr><th>Namespace prefix</th><th>Namespace IRI</th><th>RDF vocabulary</th></tr>
+      <tr><td>rdf</td><td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td><td>The RDF built-in vocabulary [[RDF-SCHEMA]]</td></tr>
+      <tr><td>rdfs</td><td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td><td>The RDF Schema vocabulary [[RDF-SCHEMA]]</td></tr>
+      <tr><td>xsd</td><td><a href="http://www.w3.org/2001/XMLSchema#"><code>http://www.w3.org/2001/XMLSchema#</code></a></td><td>The <a>RDF-compatible XSD types</a></td></tr>
+    </table>
+
+    <p>In some contexts it is common to abbreviate <a title="IRI">IRIs</a>
+    that start with <a title="namespace IRI">namespace IRIs</a> by using the
+    associated <a>namespace prefix</a>. For example, the IRI
+    <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>
+    would be abbreviated as <code>rdf:XMLLiteral</code>.
+    Note however that these abbreviations are <em>not</em> valid IRIs,
+    and MUST NOT be used in contexts where IRIs are expected.
+    Namespace IRIs and namespace prefixes are <em>not</em> a formal part of the
+    RDF data model. They are merely a syntactic convenience for
+    abbreviating IRIs.</p>
+
+    <p>The term “<dfn>namespace</dfn>” on its own does not have a
+    well-defined meaning in the context of RDF, but is sometimes informally
+    used to mean “<a>namespace IRI</a>” or “<a>RDF vocabulary</a>”.</p>
 </section>
 
 
@@ -287,8 +317,9 @@
 <section id="managing-graphs">
     <h3>Merging and Managing RDF Graphs</h3>
 
-    <p class="issue">This section should explain terminology around working
-    with multiple graphs, and explain the fact that graphs merge easily.
+    <p class="issue">This section should explain terminology around
+    <a href="#section-multigraph">working with multiple graphs</a>,
+    and explain the fact that graphs merge easily.
     This will be added once the Working Group has finalised a design.</p>
 
     <p>An <dfn>RDF document</dfn> is a document that encodes an
@@ -302,48 +333,23 @@
 
 
 <section id="conformance">
-    Implementations are free to represent <a title="RDF graph">RDF graphs</a> in
-    any other equivalent form. As an example: in an RDF graph,
-    literals with datatype <tt><a>rdf:XMLLiteral</a></tt> can be represented
-    in a non-canonical
-    format, and canonicalization performed during the comparison between two
-    such literals. In this example the comparisons may be
-    being performed either between syntactic structures or
-    between their denotations in the domain of discourse.
-    Implementations that do not require any such comparisons can
-    hence be optimized.</p>
-</section>
-
-
-<section id="section-URIspaces">
-    <h2>RDF Vocabulary IRI and Namespace</h2>
-
-    <p class="issue">This section should be removed from
-    <em>RDF Concepts</em> and folded into [[RDF-SCHEMA]] which
-    actually defines the terms in question. This is
-    <a href="http://www.w3.org/2011/rdf-wg/track/actions/121">ACTION-121</a>.</p>
+    <p>This specification, <em>RDF 1.1 Concepts and Abstract Syntax</em>,
+    defines a data model and related terminology for use in
+    other specifications, such as
+    <a title="concrete RDF syntax">concrete RDF syntaxes</a>,
+    API specifications, and query languages.
+    Implementations cannot directly conform to
+    <em>RDF 1.1 Concepts and Abstract Syntax</em>,
+    but can conform to such other specifications that are based on the
+    RDF data model.</p>
 
-    <p>RDF uses <a title="IRI">IRIs</a> to identify resources
-    and properties. Certain
-    IRIs with the following leading substring are defined by the
-    RDF specifications to denote specific concepts:</p>
-
-    <ul>
-      <li><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
-      (conventionally associated with namespace prefix <code>rdf:</code>)</li>
-    </ul>
-
-    <p>Vocabulary terms in the <code>rdf:</code>
-    namespace are listed and described in detail in the
-    RDF Schema specification [[!RDF-SCHEMA]].</p>
-
-    <p class="note">The RDF namespace is also used as an
-    XML namespace [[XML-NAMES]] to define a number of additional
-    element and attribute names for purely syntactic purposes within
-    the RDF/XML syntax ([[RDF-SYNTAX-GRAMMAR]],
-    <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section-Namespace">section 5.1</a>).
-    These terms (e.g., <code>rdf:about</code> and <code>rdf:ID</code>)
-    do not denote concepts.</p>
+    <p>Another specification conforms to
+    <em>RDF 1.1 Concepts and Abstract Syntax</em> if it defines operations
+    in terms of <a title="RDF graph">RDF graphs</a>
+    or <a title="RDF dataset">RDF datasets</a>, and if any use of
+    terminology defined in normative sections of
+    <em>RDF 1.1 Concepts and Abstract Syntax</em>
+    is consistent with its definitions and conformance requirements.</p>
 </section>
 
 
@@ -353,9 +359,9 @@
     <p>An <dfn>RDF graph</dfn> is a set of
     <a title="RDF triple">RDF triples</a>.</p>
 
-    <p><a name="section-graph-equality"></a><dfn>Graph equivalence</dfn>:
+    <p><a name="section-graph-equality"></a><dfn>Graph isomorphism</dfn>:
     Two <a title="RDF graph">RDF graphs</a>
-    <var>G</var> and <var>G'</var> are equivalent if there
+    <var>G</var> and <var>G'</var> are <em>isomorphic</em> if there
     is a bijection <var>M</var> between the sets of nodes of the two graphs,
     such that:</p>
 
@@ -373,19 +379,9 @@
     </ol>
     <p>With this definition, <var>M</var> shows how each blank node 
     in <var>G</var> can be replaced with
-    a new blank node to give <var>G'</var>. A definition of graph equivalence
+    a new blank node to give <var>G'</var>. Graph isomorphism
     is needed to support the RDF Test Cases [[RDF-TESTCASES]] specification.</p>
 
-    <p class="issue">
-    This definition of “graph equivalence” only coincides with the
-    [[RDF-MT]] definition of
-    “<a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#glossEquivalent">equivalent</a>”
-    under
-    <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/#entail">simple entailment</a>.
-    A possible solution would be to rename “graph equivalence” to
-    “graph isomorphism”. This is
-    <a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>.</p>
-
 
 <section id="section-triples">
     <h3>Triples</h3>
@@ -658,6 +654,10 @@
     and provides one additional built-in datatype,
     <code><a>rdf:XMLLiteral</a></code>.</p>
 
+    <p class="issue">The Working Group is planning to add an HTML datatype
+    to better address the use case of including text with markup. This is
+    <a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>.</p>
+
     <p>A <dfn>datatype</dfn> consists of a <a>lexical space</a>,
     a <a>value space</a> and a <a>lexical-to-value mapping</a>, and
     is denoted by one or more <a title="IRI">IRIs</a>.</p>
@@ -739,8 +739,7 @@
     <p>The <a title="literal">literals</a> that can be defined using this
     datatype are:</p>
 
-    <table border="1" cellpadding="5" summary=
-    "This table lists the literals of type xsd:boolean.">
+    <table rules="all" summary="This table lists the literals of type xsd:boolean.">
       <tr>
         <th>Literal</th>
         <th>Value</th>
@@ -767,18 +766,6 @@
 <section id="xsd-datatypes">
     <h3>The XML Schema Built-in Datatypes</h3>
 
-    <p class="issue">XML Schema 1.1 added a number of new datatypes:
-    <code><a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a></code>,
-    <code><a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a></code>,
-    <code><a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a></code>, and
-    <code><a href="http://www.w3.org/TR/xmlschema11-2/#precisionDecimal">xsd:precisionDecimal</a></code>.
-    Some of them are already used in RIF and OWL2. They should possibly be added
-    here as well. Also,
-    <code><a href="http://www.w3.org/TR/xmlschema11-2/#duration">xsd:duration</a></code>
-    is noted below as being unsuitable for use in RDF. The design of the type
-    has changed, so this should be reviewed. This is
-    <a href="http://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>.</p>
-
     <p><a title="IRI">IRIs</a> of the form
     <code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
     where <code><em>xxx</em></code>
@@ -788,7 +775,7 @@
     listed in the following table are the
     <dfn>RDF-compatible XSD types</dfn>. Their use is RECOMMENDED.</p>
  
-    <table class="xsd-types" rules="all">
+    <table rules="all" summary="A list of the RDF-compatible XSD types, with short descriptions">
     <tr><th></th><th>Datatype</th><th>Value space (informative)</th></tr>
 
     <tr><th rowspan="4">Core types</th><td><a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a></td><td>Character strings</td></tr>
@@ -800,17 +787,20 @@
         <td><a href="http://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a></td><td>64-bit floating point numbers incl. ±Inf, ±0, NaN</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#float"><code>xsd:float</code></a></td><td>32-bit floating point numbers incl. ±Inf, ±0, NaN</td></tr>
 
-    <tr><th rowspan="3">Time and date</th>
+    <tr><th rowspan="4">Time and date</th>
         <td><a href="http://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a></td><td>Dates (yyyy-mm-dd) with or without timezone</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#time"><code>xsd:time</code></a></td><td>Times (hh:mm:ss.sss…) with or without timezone</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a></td><td>Date and time with or without timezone</td></tr>
+    <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp"><code>xsd:dateTimeStamp</code></a></td><td>Date and time with required timezone</td></tr>
 
-    <tr><th rowspan="5">Recurring and<br />partial dates</th>
+    <tr><th rowspan="7">Recurring and<br />partial dates</th>
         <td><a href="http://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a></td><td>Gregorian calendar year</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gMonth"><code>xsd:gMonth</code></a></td><td>Gregorian calendar month</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gDay"><code>xsd:gDay</code></a></td><td>Gregorian calendar day of the month</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a></td><td>Gregorian calendar year and month</td></tr>
     <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#gMonthDay"><code>xsd:gMonthDay</code></a></td><td>Gregorian calendar month and day</td></tr>
+    <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration"><code>xsd:yearMonthDuration</code></a></td><td>Duration of time (months and years)</td></tr>
+    <tr><td><a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration"><code>xsd:dayTimeDuration</code></a></td><td>Duration of time (days, hours, minutes, seconds)</td></tr>
 
     <tr><th rowspan="12">Limited-range<br />integer numbers</th>
         <td><a href="http://www.w3.org/TR/xmlschema11-2/#byte"><code>xsd:byte</code></a></td><td>-128…+127 (8 bit)</td></tr>
@@ -848,9 +838,7 @@
     <div class="note">
     <ul>
     <li><a href="http://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a>
-    does not have a well-defined value space (this may be corrected
-    in later revisions of XML Schema datatypes, in which case the
-    revised datatype would be suitable for use in RDF datatyping).</li>
+    does not have a well-defined value space.</li>
     <li><a href="http://www.w3.org/TR/xmlschema11-2/#QName"><code>xsd:QName</code></a> 
     and
     <a href="http://www.w3.org/TR/xmlschema11-2/#ENTITY"><code>xsd:ENTITY</code></a> 
@@ -870,31 +858,22 @@
     </ul>
     </div>
 
+    <p class="issue">
+    <code><a href="http://www.w3.org/TR/xmlschema11-2/#duration">xsd:duration</a></code>
+    is noted above as being unsuitable for use in RDF. The design of the type
+    has changed in XSD 1.1, so this should be reviewed. This is
+    <a href="http://www.w3.org/2011/rdf-wg/track/issues/88">ISSUE-88</a>.</p>
+
 </section>
 
 
 <section id="section-XMLLiteral">
     <h3>The <code>rdf:XMLLiteral</code> Datatype</h3>
 
-    <p class="issue">The canonicalization rules required for XML literals
-    are quite complicated. Increasingly, RDF is produced and consumed in
-    environments where no XML parser and canonicalization engine is
-    available. A possible change to relax the requirements for the
-    lexical space, while retaining the value space, is under discussion.
-    This is <a href="http://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>.</p>
-
     <p>RDF provides for XML content as a possible <a>literal value</a>.
     Such content is indicated in an <a>RDF graph</a> using a <a>literal</a>
     whose <a>datatype</a> is a special built-in datatype
-    <code>rdf:XMLLiteral</code>.
-    This allows the inclusion of text that contains markup, such as
-    XHTML [[XHTML11]].</p>
-
-    <p class="issue">Should RDF define an HTML datatype? Arguably this would
-    be more useful for including markup in text. This is
-    <a href="http://www.w3.org/2011/rdf-wg/track/issues/63">ISSUE-63</a>.</p>
-
-    <p><code><dfn>rdf:XMLLiteral</dfn></code> is defined as follows.</p>
+    <code><dfn>rdf:XMLLiteral</dfn></code>, which is defined as follows:</p>
    
     <dl>
       <dt><a name="XMLLiteral-uri" id="XMLLiteral-uri">An IRI denoting
@@ -905,73 +884,60 @@
 
       <dt><a name="XMLLiteral-lexical-space" id="XMLLiteral-lexical-space">The lexical space</a></dt>
 
-<dd>is the set of all
-strings:
-<ul>
-<li>which are well-balanced, self-contained 
-<a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">
-XML content</a> 
-[[!XML10]];
-</li>
-<li>for which encoding as UTF-8 
-[[!UTF-8]] yields 
-<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-canonical-XML">
-exclusive
-Canonical XML </a> (with comments, with empty  
-<a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList">
-InclusiveNamespaces PrefixList
-</a>) [[!XML-EXC-C14N]];
-</li>
-<li>for which embedding between an arbitrary XML start tag and an end tag
-yields a document conforming to <a href=
-      "http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML
-      Namespaces</a> [[!XML-NAMES]]</li>
-</ul>
-</dd>
+      <dd>is the set of all strings which are well-balanced, self-contained 
+      <a href="http://www.w3.org/TR/2000/REC-xml-20001006#NT-content">XML content</a> 
+      [[!XML10]]; and for which embedding between an arbitrary
+      XML start tag and an end tag yields a document conforming to
+      <a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">XML Namespaces</a>
+      [[!XML-NAMES]].</dd>
 
-
-   <dt><a name="XMLLiteral-value-space" id="XMLLiteral-value-space">The value space</a></dt>
+      <dt><a name="XMLLiteral-value-space" id="XMLLiteral-value-space">The value space</a></dt>
 
-      <dd>is a set of entities, called XML values, which is:
-<ul>
-<li>disjoint from the lexical space;</li>
-<li>disjoint from the value space of any other datatype that is not explicitly defined as a sub- or supertype of this datatype;</li>
-<li>disjoint from the set of Unicode character strings [[!UNICODE]];</li>
-<li>and in 1:1 correspondence with the lexical space.</li>
-</ul>
-</dd>
+      <dd>is a set of DOM
+      <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-B63ED1A3"><code>DocumentFragment</code></a>
+      nodes [[!DOM-LEVEL-3-CORE]]. Two
+      <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-B63ED1A3"><code>DocumentFragment</code></a>
+      nodes <em>A</em> and <em>B</em> are considered equal
+      if and only if the DOM method
+      <code><em>A</em>.<a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Node3-isEqualNode">isEqualNode</a>(<em>B</em>)</code>
+      returns <code>true</code>.</dd>
 
       <dt><a name="XMLLiteral-mapping" id="XMLLiteral-mapping">The lexical-to-value mapping</a></dt>
 
-      <dd>
-is a one-one mapping from the lexical space onto the value space,
-    i.e. it is both injective and surjective.
-</dd> 
+      <dd><ul>
+      <li>Let <code>domfrag</code> be a DOM
+      <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-B63ED1A3"><code>DocumentFragment</code></a>
+      node [[!DOM-LEVEL-3-CORE]] corresponding to the literal's
+      <a>lexical form</a></li>
+      <li>Return <code>domfrag.<a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-normalize">normalize</a>()</code></li>
+      </ul></dd>
 
+      <dt><a name="XMLLiteral-canonical" id="XMLLiteral-canonical">The canonical mapping</a></dt>
+      <dd>defines a
+      <a href="http://www.w3.org/TR/xmlschema11-2/#dt-canonical-mapping">canonical lexical form</a>
+      [[!XMLSCHEMA11-2]] for each member of the value space.
+      The <code>rdf:XMLLiteral</code> canonical mapping is the
+      <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-exclusive-XML-canonicalization-method">exclusive
+      XML canonicalization method</a> (<em>with comments, with empty  
+      <a href="http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/#def-InclusiveNamespaces-PrefixList">
+      InclusiveNamespaces PrefixList</a></em>) [[!XML-EXC-C14N]].
 
+      </dl>
 
-    </dl>
+      <p class="note">Any XML namespace declarations (<code>xmlns</code>)
+      and language annotation (<code>xml:lang</code>) desired in the
+      XML content must be included explicitly in the XML literal.
+      Note that some concrete RDF syntaxes may define mechanisms
+      for inheriting them from the context
+      (e.g., <a href="http://www.w3.org/TR/rdf-syntax-grammar/#parseTypeLiteralPropertyElt"><code>@parseType="literal"</code></a>
+      in RDF/XML [[RDF-SYNTAX-GRAMMAR]]).</p>
 
       <p class="note">Not all values of this datatype are compliant
       with XML 1.1 [[XML11]]. If compliance
       with XML 1.1 is desired, then only those values that are
-<a href="http://www.w3.org/TR/2002/CR-xml11-20021015/#sec2.13">fully
+<a href="http://www.w3.org/TR/xml11/#dt-fullnorm">fully
       normalized</a> according to XML 1.1 should be used.</p>
 
-      <p class="note">XML values can be thought of as the 
-[[XML-INFOSET]] or the [[XPATH]]
-nodeset corresponding to the lexical form, with an appropriate equality
-function.</p>
-
-    <p class="note">RDF applications may use additional equivalence relations,
-    such as that which relates an 
-    <a href="http://www.w3.org/TR/xmlschema11-2/#string"><code>xsd:string</code></a>
-    with an <code>rdf:XMLLiteral</code> corresponding to a single text node
-    of the same string.</p>
-
-    <p class="note">If language annotation of XML literals is required, 
-    it must be explicitly included as markup, usually by means of an 
-    <code>xml:lang</code> attribute.</p>
 </section>
 
 <section id="datatype-maps">
@@ -981,16 +947,18 @@
     &lt;<a>IRI</a>, <a>datatype</a>&gt; pairs such that no
     IRI appears twice in the set and the IRI denotes the datatype.
     It can be seen as a function from IRIs
-    to datatypes. Every datatype map contains the pair
-    &lt;<code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>,
-    <code><a>rdf:XMLLiteral</a></code>&gt;.</p>
+    to datatypes.</p>
 
-    <p>The <dfn>XSD datatype map</dfn> is the <a>datatype map</a>
-    which also contains the set of all pairs of the form
-    &lt;<code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
-    <code>xsd:<em>xxx</em></code>&gt;, where <code>xsd:<em>xxx</em></code>
-    is the name of an
-    <a title="RDF-compatible XSD types">RDF-compatible XSD type</a>.</p>
+    <p>If a <a>datatype map</a> contains the IRI
+    <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code>,
+    then it MUST be paired with the datatype
+    <code><a>rdf:XMLLiteral</a></code>.</p>
+
+    <p>If a <a>datatype map</a> contains an IRI of the form
+    <code>http://www.w3.org/2001/XMLSchema#<em>xxx</em></code>,
+    then it MUST be paired with the
+    <a title="RDF-compatible XSD types">RDF-compatible XSD type</a>
+    named <code>xsd:<em>xxx</em></code>.<p>
 
 </section>
 
@@ -1025,7 +993,7 @@
     (<a>literal equality</a>).
     Similarly, for comparing <a title="RDF graph">RDF graphs</a>,
     semantic notions of <a>entailment</a> are usually more helpful
-    than syntactic <a>graph equivalence</a>.</p>
+    than syntactic <a>graph isomorphism</a>.</p>
 
 </section>
 
@@ -1145,9 +1113,8 @@
 <section id="section-Acknowledgments" class="informative">
     <h2>Acknowledgments</h2>
 
-    <p class="issue">This section does not yet list those who made
-    contributions to the RDF 1.1 version, nor does it list the
-    current RDF WG members.</p>
+    <p class="issue">This section does not yet acknowledge
+    contributions to the RDF 1.1 version.</p>
 
     <p>The RDF 2004 editors acknowledge valuable contributions from
     Frank Manola, Pat Hayes, Dan Brickley, Jos de Roo, 
@@ -1162,7 +1129,7 @@
 
     <p>This specification is a product of extended deliberations by the
     <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/#section-Acknowledgments">members
-    of the RDFcore Working Group and the RDF and RDF Schema Working Group</a>.</p>
+    of the RDFcore Working Group and the Schema Working Group</a>.</p>
 </section>
 
 
@@ -1170,6 +1137,16 @@
   <h2>Changes from RDF 2004</h2>
 
   <ul>
+    <li>2012-05-14: Replaced the example graph diagram in <a href="#data-model">Section 1.1</a> with a re-drawn SVG version, with support from Dominik Tomaszuk</li>
+    <li>2012-05-10: New <a href="#conformance">Conformance section</a> to explain that this specification is not implemented directly, but through other specifications that use our definitions</li>
+    <li>2012-05-10: Simplified <code><a>rdf:XMLLiteral</a></code>'s new value space slightly after feedback from Ivan Herman and Arnaud Le Hors.</li>
+    <li>2012-05-10: Added an informative subsection on <a href="#vocabularies">RDF vocabularies and namespace IRIs</a>.</li>
+    <li>2012-05-09: Removed an example from the conformance section that didn't make sense any more with the modified <code>rdf:XMLLiteral</code>. Added some new issue boxes.</li>
+    <li>2012-05-09: <code><a>rdf:XMLLiteral</a></code> no longer requires lexical forms to be canonicalized, and the value space is now defined in terms of [[DOM-LEVEL-3-CORE]] (<a href="https://www.w3.org/2011/rdf-wg/track/issues/13">ISSUE-13</a>)</li>
+    <li>2012-05-09: Removed Section 3 <em>RDF Vocabulary IRI and Namespace</em>; its contents will be folded into the RDF Schema document</li>
+    <li>2012-05-02: Renamed “graph equivalence” to “<a>graph isomorphism</a>” (<a href="https://www.w3.org/2011/rdf-wg/track/issues/86">ISSUE-86</a>)</li>
+    <li>2012-05-02: Updated [[XMLSCHEMA11-1]] and [[XMLSCHEMA11-2]] references to the new REC versions</li>
+    <li>2012-05-02: Added the new XSD 1.1 datatypes <a href="http://www.w3.org/TR/xmlschema11-2/#dayTimeDuration">xsd:dayTimeDuration</a>, <a href="http://www.w3.org/TR/xmlschema11-2/#yearMonthDuration">xsd:yearMonthDuration</a> and <a href="http://www.w3.org/TR/xmlschema11-2/#dateTimeStamp">xsd:dateTimeStamp</a> to the list of <a>RDF-compatible XSD types</a> (<a href="https://www.w3.org/2011/rdf-wg/track/issues/66">ISSUE-66</a>)</li>
     <li>2012-04-26: Remove normative definition of “property” as it disagreed with RDF Semantics; small editorial changes.</li>
     <li>2011-11-21: Updated XHTML 1.0 reference to XHTML 1.1</li>
     <li>2011-11-20: Added table of <a>RDF-compatible XSD types</a>, and definition of <a>datatype map</a>, both adapted from previous content in [[RDF-MT]]
@@ -1198,11 +1175,6 @@
 
 
 <section id="references">
-    <p class="issue">This specification normatively references version 1.1
-    of XML Schema [[XMLSCHEMA11-1]] and [[XMLSCHEMA11-2]].
-    These documents have not yet reached W3C Recommendation status,
-    but are expected to do so before <em>RDF 1.1 Concepts and
-    Abstract Syntax</em> goes to Last Call.</p>
 </section>
 
   </body>
Binary file rdf-concepts/rdf-graph.png has changed
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/rdf-concepts/rdf-graph.svg	Tue May 15 10:10:48 2012 -0700
@@ -0,0 +1,19 @@
+<svg viewBox="0 -20.5 329 41" width="329" height="41" xmlns="http://www.w3.org/2000/svg">
+  <style type="text/css">
+ellipse, polyline { stroke-width: 1; stroke: black; }
+ellipse { fill: white; }
+polyline { fill: none; }
+text { fill: black; text-anchor: middle; font-family: Helvetica, sans-serif; }
+  </style>
+  <g transform="translate(55 0)">
+    <ellipse rx="54" ry="20"/><text y="5" font-size="16">Subject</text>
+  </g>
+  <g transform="translate(274 0)">
+    <ellipse rx="54" ry="20"/><text y="5" font-size="16">Object</text>
+  </g>
+  <g transform="translate(109 0)">
+    <text x="52" y="-5" font-size="16">Predicate</text>
+    <polyline points="0,0 109,0"/>
+    <polyline points="98,-5 110,0 98,5"/>
+  </g>
+</svg>
--- a/rdf-layers/index.html	Wed May 02 07:19:20 2012 -0700
+++ b/rdf-layers/index.html	Tue May 15 10:10:48 2012 -0700
@@ -1,789 +1,9 @@
-<!DOCTYPE html>
-<html lang="en">
-  <head>
-    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>RDF Data Layers and Datasets</title>
-    <style type="text/css">
-.figure { font-weight: bold; text-align: center; }
-table.xsd-types td, table.xsd-types th { border: 1px solid #ddd; padding: 0.1em 0.5em; }
-    </style>
-    <script src='../ReSpec.js/js/respec.js' class='remove'></script>
-    <script class='remove'>
-      var respecConfig = {
-          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "ED",
-          
-          // the specification's short name, as in http://www.w3.org/TR/short-name/
-          shortName:            "rdf-layers",
-
-          // if your specification has a subtitle that goes below the main
-          // formal title, define it here
-          // subtitle   :  "an excellent document",
-
-          // if you wish the publication date to be other than today, set this
-          // publishDate:  "2009-08-06",
-
-          // if the specification's copyright date is a range of years, specify
-          // the start date here:
-          //          copyrightStart: "2012",
-
-          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
-          // and its maturity status
-//          previousPublishDate:  "2004-02-10",
-//          previousMaturity:  "REC",
-
-          // if there a publicly available Editor's Draft, this is the link
-//@@@
-          edDraftURI:           "http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-layers/index.html",
-
-          // if this is a LCWD, uncomment and set the end of its review period
-          // lcEnd: "2009-08-05",
-
-          // if there is an earler version of this specification at the Recommendation level,
-          // set this to the shortname of that version. This is optional and not usually
-          // necessary.
-          //          prevRecShortname: "rdf-concepts",
-
-          // if you want to have extra CSS, append them to this list
-          // it is recommended that the respec.css stylesheet be kept
-          extraCSS:             ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
-
-          // editors, add as many as you like
-          // only "name" is required
-          editors:  [
-              { name: "TBD", url: "",
-                company: "", companyURL: "",
-              },
-          ],
-          otherContributors: {
-              "Contributor": [
-	      { name: "Sandro Hawke", url:"http://www.w3.org/People/Sandro",
-	      company:"W3C", companyURL: "http://www.w3.org", note:"Initial text"},
-	      { name: "Dan Brickley", note:"Initial diagram" }
-	      ]
-          },
-
-          // authors, add as many as you like. 
-          // This is optional, uncomment if you have authors as well as editors.
-          // only "name" is required. Same format as editors.
-
-          //authors:  [
-          //    { name: "Your Name", url: "http://example.org/",
-          //      company: "Your Company", companyURL: "http://example.com/" },
-          //],
-          
-          // name of the WG
-          wg:           "RDF Working Group",
-          
-          // URI of the public WG page
-          wgURI:        "http://www.w3.org/2011/rdf-wg/",
-          
-          // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "public-rdf-comments",
-          
-          // URI of the patent status for this WG, for Rec-track documents
-          // !!!! IMPORTANT !!!!
-          // This is important for Rec-track documents, do not copy a patent URI from a random
-          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
-          // Team Contact.
-          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46168/status",
-
-          // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
-          // throughout the generated specification. The triples generated use vocabulary items
-          // from the dcterms, foaf, and bibo. The parameter defaults to false.
-          doRDFa: true,
-      };
-
-// @@@ A number of references have been patched into the local berjon.biblio and need to be added to the global biblio in CVS:
-    </script>
-  </head>
-
-  <body>
-
-<section id="abstract">
-  <p>This specification introduces the notion of RDF <i>data
-  layers</i>&mdash;places to store RDF triples&mdash;and defines a set
-  of languages for expressing information about them.  Examples of
-  data layers include: an HTML page with embedded RDFa or microdata, a
-  file containing RDF/XML or Turtle data, and a SQL database viewable
-  as RDF using R2RML.  The term "layer" is a metaphor: we imagine a
-  layer as transparent surfaces on which RDF graphs can be drawn and
-  then easily combined, still retaining their own identity and
-  properties.  RDF data layers are a generalization of SPARQL's named
-  graphs, providing a standard model with formal semantics for systems
-  which manage multiple collections of RDF data. </p>
-</section>
-
-
-<section class="informative">
-    <h2>Introduction</h2>
-
-    <p>@@@ background, context, and general motivation ... </p>
-
-    <p>The name "layer" is chosen to evoke the image of a transparent
-    surface on which an RDF Graph can be temporarily drawn and then
-    easily aligned with other layers to make a larger, combined
-    graph. Sometimes we work with the combined graph, but when we want
-    to, we can still separate the layers. This is particularly
-    important if the data come from different sources which might
-    potentially update their contribution; we need to be able to erase
-    and redraw just their layer.</p>
-
-    <img src="layers.jpg" />
-
-    <p class="note">Eric suggests that only the arcs should be drawn
-    on the layers; the nodes are fundamental, underneath, projecting
-    up through all the layers.</p>
-
-
-</section>
-
-<section>
-  <h2>Concepts</h2>
-
-  <section>
-    <h2>Layer</h2>
-
-    <p class="issue">The term "Layer" is a placeholder.  The final
-    term has not yet been selected by the Working Group.  Other
-    candidates include "G-Box", "(Data) Surface", "(Data) Space".  The
-    Editors do not consider <a
-    href="http://www.w3.org/2011/rdf-wg/meeting/2011-10-12#resolution_1">F2F2
-    Resolultion 1</a> still binding, given the degree to which the concept
-    and its role has shifted since that meeting.</p>
-
-    <p>An RDF <dfn>data layer</dfn> or just <dfn>layer</dfn> is a
-    conceptual place where RDF triples can stored.  Examples include:
-    </p>
-    
-    <ul>
-
-      <li>a human-readable Web page, such as an HTML page containing
-      RDFa markup, microdata markup, or embedded turtle.</li>
-
-      <li>a file, in a computer's filesystem, containing RDF data
-      expressed in RDF/XML, N-Triples, Turtle, etc.</li>
-
-      <li>a machine-readable Web page containing RDF data expressed in
-      RDF/XML, N-Triples, Turtle, etc.</li>
-
-      <li>a SQL database which provides an RDF view of its data,
-      perhaps using R2RML</li>
-
-      <li>the default graph or any of the named graphs available via a
-      SPARQL endpoint</li>
-    </ul>
-
-    <p>Formally, a layer is a function from points in time to RDF
-    Graphs.  This matches the notion of a container or a place or a
-    writing surface: at any given point in time (for which the
-    function is defined), there is a set of RDF triples in that spot.
-    Since an RDF Graph is defined as a set of RDF triples, the triples
-    there at time t form the graph which is the output of the function
-    for input t.</p>
-
-    <p>Web resources which do not behave as a function of time &mdash;
-    such as pages which provide different data to different users at
-    the exact same time &mdash; are not layers.  See also <a>static
-    layer</a> and <a>layer switch</a>.</p>
-
-  </section>
-
-  <section>
-    <h2>Dataset</h2>
-
-    <p>A <dfn>dataset</dfn> is defined by <a
-    href="http://www.w3.org/TR/sparql11-query/#rdfDataset">SPARQL
-    1.1</a> as a structure consisting of:</p>
-    
-    <ol>
-      
-      <li>A distinguished RDF Graph called the <dfn>default graph</dfn></li>
-      
-      <li>A set of (<i>name</i>, <i>graph</i>) pairs, where
-      <i>name</i> is an IRI and the <i>graph</i> is an RDF Graph.  No
-      two pairs in a dataset may have the same <i>name</i>.</li>
-      
-    </ol>
-    
-    <p>This definition forms the basis of the SPARQL Query semantics;
-    each query is performed against the information in a specific
-    dataset.</p>
-    
-    <p>A dataset is a pure mathematical structure, like an RDF Graph
-    or a set of integers, with no identity apart from its contents.
-    Two datasets with the same contents are in fact the same dataset,
-    and one dataset cannot change over time.  Logically, a dataset
-    cannot have different contents tomorrow; if it is changed, it is a
-    different dataset.  By analogy, one cannot change the set of prime
-    numbers or the set {1,3,5}; datasets, like these sets of integers,
-    are immutable, eternal concepts.</p>
-
-    <p>The word <strong>"default"</strong> in the term "default graph"
-    refers to the fact that in SPARQL, this is the graph a server uses
-    to perform a query when the client does not specify the name of a
-    graph to use.  The term is not related to the idea of a graph
-    containing default (overridable) information.  Logically, the role
-    of the default graph is such that it could reasonably be thought
-    of as containing the dataset's metadata.</p>
-
-  </section>
-
-  <section>
-    <h2>Graph Store</h2>
-    
-    <p>SPARQL 1.1 Update defines a mutable (time-dependent) structure
-    corresponding to a <a>dataset</a>, called <dfn>graph store</dfn>.
-    It is defined as:</p>
-
-    <ol>
-
-      <li>A distinguished slot for an RDF Graph</li>
-      
-      <li>A set of (<i>name</i>, <i>slot</i>) pairs, where the slot holds an RDF Graph
-      and the name is an IRI.  No two pairs in a graph store may have the same <i>name</i>.</li>
-      
-    </ol>
-    
-    <p>The term "slot" is synonymous with "layer".</p>
-
-    <p>Formally, a graph store can be seen as a function from points
-    in time to <a>dataset</a>s.</p>
-
-  </section>
-
-  <section>
-    <h2>Named Graph</h2>
-
-    <p>SPARQL formally defines the term <dfn>named graph</dfn>,
-    following [Carroll], as one of the (name, graph) pairs in a
-    <a>dataset</a>.</p>
-
-    <p>In practice, the term is used more loosely to refer to the
-    graph part of those pairs or to the slot part of the pairs in a
-    <a>graph store</a>.  The text of <a
-    href="http://www.w3.org/TR/2012/WD-sparql11-update-20120105/">SPARQL
-    1.1 Update</a> does this, for example, as seen in phrases like,
-    "This example copies triples from one named graph to another named
-    graph".</p>
-
-    <p>We continue that practice, using "named graph" to refer
-    to either the graph part of the (name, graph) pairs of a dataset,
-    or the corresponding slot part of graph store.  Note that even in
-    this loose usage, the default graph of a dataset and its
-    corresponding slot in a graph store are never called named
-    graphs.</p>
-
-  </section>
-
-  <section>
-    <h2>Quad</h2>
-
-    <p>We define an RDF <dfn>quad</dfn> as the 4-tuple
-    (<i>subject</i>, <i>predicate</i>, <i>object</i>,
-    <i>layer</i>).</p>
-
-    <p>Informally, a quad should be understand as a statement that the
-    RDF triple (<i>subject</i>, <i>predicate</i>, <i>object</i>) is in
-    the <a>layer</a> <i>layer</i>.</p>
-
-  </section>
-
-  <section>
-    <h2>Quadset</h2>
-
-    <p>We define an RDF <dfn>quadset</dfn> as a set containing (zero or more) RDF Quads and (zero or more) RDF Triples.</p>
-
-    <p>Quadsets and <a>dataset</a>s are isomorphic and semantically
-    equivalent:</p>
-
-    <ul>
-
-      <li>the triples in the quadset correspond to the triples in default
-     graph of the dataset;</li>
-
-     <li>each quad corresponds to a triple in a named graph: the quad (S P
-     O L) corresponds to the triple (S P O) in the graph with the name
-     L.</li>
-
-    </ul>
-
-    <p>Datasets and quadsets can thus be used interchangeably, with
-    the more appropriate one being use in any particular context.</p>
-
-  </section>
-
-  <section>
-    <h2>Static Layer</h2>
-
-    <p>A <dfn>static layer</dfn> is a <a>layer</a> which, by definition,
-    contains the same triples at all points in time.</p>
-    
-  </section>
-
-
-  <section>
-    <h2>Layer Switch</h2>
-
-    <p>A <dfn>layer switch</dfn> is a Web Resource which acts as a
-    different <a>layer</a> when responding to different client
-    information, such as the value of a cookie or the client IP
-    address.</p>
-
-    <p>Systems which use layer switches SHOULD also define working
-    URLs for each of the layers the switch can act as, and they SHOULD
-    provide that URL to the client via the Content-Location
-    header.</p>
-
-    <p>For example, the URL
-    <tt>http://example.org/my-account-balance</tt> might return the
-    account balance of the logged-in user.  If the user is logged in
-    as "alice", the system might return a Content-Location of
-    <tt>http://example.org/my-account-balance?user=alice</tt>.  The
-    system could reasonably be designed to allow Alice to use that URL as
-    well; for other users it would give <tt>403 Forbidden</tt>.</p>
-
-  </section>
-</section>
-
-<section>
-  <h2>Use Cases</h2>
-
-  <p>TBD.  See <a href="#detailed-example" class="sectionRef"></a> for now.</p>
-
-</section>
-
-
-<section id="syntax">
-  <h2>Dataset Languages</h2>
-
-  <section>
-    <h3>N-Quads</h3>
-
-  </section>
-
-
-  <section>
-    <h3>TriG</h3>
-
-  </section>
-
-
-  <section>
-    <h3>Turtle in HTML</h3>
-
-    <div class="note">
-      <p>This is higly speculative.  An interesting idea.</p>
-
-      <p>The key challenge is: can we get everyone to agree that when
-      the script tag has an id attribute, those contents are
-      <em>not</em> asserted?  Or maybe we need something like
-      class="unasserted"...  but do we have the right to say either of
-      those things?  Maybe in the Turtle spec...</p>
-    </div>
-    
-    <p>When text/turtle is used inside HTML script tags, if the script
-    tag has an id attribute, then that content goes into a named graph
-    (with its name being that section URL).  The rest goes into the
-    default graph.</p>
-
-  </section>
-
-
-
-</section>
-
-<section>
-  <h2>Semantics</h2>
-
-  <p>formalize what's been said above.</p>
-
-  <p>We now give <a>dataset</a>s declarative semantics, allowing
-  dataset to be used as logical statements (like RDF Graphs).  We
-  define a dataset as being true if and only if (1) its default graph
-  is true, and (2) for every (<i>name</i>, <i>graph</i>) pair in the
-  dataset, the layer denoted by <i>name</i> contains every triple in
-  <i>graph</i>.</p>
-
-</section>
-
-<section>   <!-- I don't like what respec does with id=conformance -->
-  <h2>Conformance</h2>
-
-  <p>Something like: If a layer has a URL, and you get a 200 response
-  dereferencing that URL, the the response MUST be a serialization of
-  the triples on that layer, give or take synchronization (caching)
-  issues. </p>
-
-  <p>What else?</p>
-
-</section>
-
-<section class="informative">
-  <h2>Detailed Example</h2>
-
-  <p>This section presents a design for using layers in constructing a
-  federated information system.  It is intended to help explain and
-  motivate RDF <a>data layer</a>s.</p>
-
-  <section>
-    <h3>A Federated Phonebook</h3>
-
-    <p>As a first example of how to use layers, consider an
-    organization which has 25 different divisions around the world,
-    each with its own system for managing the list of its employees
-    and their phone numbers.  The parent organization wants to create
-    a unified "HQ" directory with all this information.  With their HQ
-    directory, they will be able to look up an employee's phone number
-    without first knowing the employee's division. </p>
-
-    <p>They decide to use RDF layers.  Each division is asked to
-    publish its phonebook on an internal website, in a W3C-Recommended
-    RDF syntax, using <a href="http://www.w3.org/TR/vcard-rdf/">the
-    vcard-rdf vocabulary</a>.  Each division submits the URL at which
-    this file will appear.  For example, the uswest division might
-    publish the RDF version of its phonebook at
-    <tt>http://uswest.internal.example.com/employees.rdf</tt> and the
-    Japan division might publish theirs at
-    <tt>http://ja.example.com/hr/data/export371</tt>.  The URL itself
-    doesn't matter, but the division must be able to maintain the
-    content served there and HQ must be able to easily fetch the
-    content. </p>
-
-    <p>The HQ staff assembles this list of 25 feed URLs and puts them
-    into the default graph of a SPARQL database, so the database looks
-    like this: </p>
-
-<pre>   @prefix hq: &lt;<a href="http://example.com/hq-vocab#">http://example.com/hq-vocab#</a>&gt;.
-   # default graph
-   {
-      hq:parentCo hq:division hq:div1, hq:div2, hq:div3, ...
-      &lt;<a href="http://uswest.internal.example.com/employees.rdf">http://uswest.internal.example.com/employees.rdf</a>&gt; 
-         hq:feedFrom hq:div1.
-      &lt;<a href="http://ja.example.com/hr/data/export371">http://ja.example.com/hr/data/export371</a>&gt;
-         hq:feedFrom hq:div2.
-      ...
-   }
-</pre>
-<p>Then they write a simple Web client which looks in the database for
-those feed URLs, dereferences them, and parses the RDF.  It then puts
-the parse-result into the database in a layer whose name is the same as the
-name of the feed.  This makes sense, because in this deployment each
-feed is considered to be a layer; the name of the feed is the same as
-the name of the layer.  The HQ client is copying data about the layer
-from the division databases to the HQ database, but it's still the
-same information about the same layers.
+<html>
+<head>
+<title>Redirect to SPACES</title>
+</head>
+<body>
+<p>We've changed the term "Layers" to "Spaces" for now, so see <a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-spaces/index.html#">rdf-spaces</a>.
 </p>
-
-<p>For performance reasons, the client is designed to use HTTP
-caching information.  This will allow it to efficiently re-fetch the
-information only when it has changed.  To make this work, the client will need
-to store the value of the "Last-Modified" HTTP header and also store
-(or compute, in some configurations) the value of the "Expires" header.
-</p>
-
-<p>In the end, the database looks something like this:
-</p>
-<pre> @prefix hq: &lt;<a href="http://example.com/hq-vocab#">http://example.com/hq-vocab#</a>&gt;.
- @prefix v:  &lt;<a href="http://www.w3.org/2006/vcard/ns#">http://www.w3.org/2006/vcard/ns#</a>&gt;.
- @prefix ht: &lt;<a href="http://example.org/http-vocab#">http://example.org/http-vocab#</a>&gt;.
- &lt;<a href="http://uswest.internal.example.com/employees.rdf">http://uswest.internal.example.com/employees.rdf</a>&gt; {
-    # an employee
-    [ a v:VCard
-      v:fn "John Wayne"&nbsp;;
-      v:email "[email protected]" .
-      v:tel [ a v:Work, v:Pref&nbsp;;
-              rdf:value "+213 555 5555" ]
-    ]
-    # another employee
-    ...
- }
- &lt;<a href="http://ja.example.com/hr/data/export371">http://ja.example.com/hr/data/export371</a>&gt; {
-    # an employee
-    [ a v:VCard
-      v:fn "Toshiro Mifune"&nbsp;;
-      v:email "[email protected]" .
-      v:tel [ a v:Work, v:Pref&nbsp;;
-              rdf:value "+81 75 555 5555" ]
-    ]
-    # another employee
-    ...
- }
- ...    other divisions
- # default graph, with all our metadata
- {
-   hq:parentCo hq:division hq:div1, hq:div2, hq:div3, ...
-   # stuff we need to know the efficiently keep our copy in sync
-   &lt;<a href="http://uswest.internal.example.com/employees.rdf">http://uswest.internal.example.com/employees.rdf</a>&gt; 
-     hq:feedFrom hq:div1;
-     ht:last-modified "2012-03-14T02:22:10"^^xs:datetime;
-     ht:expires "2012-04-29T00:15:00"^^xs:datetime.
-   &lt;http://ja.example.com/hr/data/export371&gt; 
-     hq:feedFrom hq:div2;
-     ht:last-modified "2012-04-01T22:00:00"^^xs:datetime;
-     ht:expires "2012-04-29T00:35:00"^^xs:datetime.
- }
-</pre>
-<p>The URL of each layer appears in four different roles in this example:
-</p>
-
-<p>1.  It is used as a label for a graph.  Here, it says which layer the
-triples in that graph are in.  That is, the triples about employee
-"John Wayne" are in the layer named
-"http://uswest.internal.example.com/employees.rdf".  Information about
-what triples are in that layer originates in the master database for
-each division, then is copied to the slave database at HQ.
-</p>
-
-<p>2.  It is used as the subject of an hq:feedFrom triple.  This
-information is manually maintained (or maintained through a corporate
-WebApp) and used to help guide the HQ fetching client.  Because in
-this deployment we are equating layers and feeds, the name of the
-layer is also the URL of the feed.
-</p>
-
-<p>3.  It is used as the subject of an ht:last-modified triple.  The
-information in this triples comes from the HTTP Last-Modified header.
-The meaning of this header in HTTP lines up well with its intuitive
-meaning here: this is the most recent time the set of triples in this
-layer changed.  (This header can be used during a refresh, with the
-If-Modified-Since headers, to make a client refresh operation very
-simple and fast if the data has not changed.)
-</p>
-
-<p>4.  It is used as the subject of an ht:expires triple.  This
-information also comes from HTTP headers, although some computation
-may be needed to turn it into the absolute datetime form used here.
-Strictly speaking, what is expiring at that time is this copy of the
-information about the layer, not the layer itself.  This slight
-conflation seems like a useful and unproblematic simplification.
-</p>
-
-<p>Given this design, it is straightforward to write SPARQL queries to
-find the phone number of an employee, no matter what their division.
-It is also easy to find out which layer is about to
-expire or has expired and should be refreshed soon.  
-</p>
-
-<p>Some alternative designs:
-</p>
-<ul><li> Divisions could push their data, instead of waiting to be polled.  That is, the divisions could be given write access to the HQ database and do SPARQL UPDATE operations to their own layers.  This is simpler in some ways but may require more expertise from people in each division.  It also requires trusting people in each division or having a SPARQL server that can be configure to grant certain users write access to only certain layers.   This also turns HQ into more of a bottleneck and single-point of failure.  With the polling approach, other systems could be given the list of feed URLs and then offer an alternative combined directory, or use the same data for other purposes, without any involvement from the divisions.
-</li></ul>
-<ul><li> The HQ client could fetch or query all the divisions at query time, rather that gathering the data in advance.  This might use the <a href="http://www.w3.org/TR/sparql11-federated-query/">SPARQL 1.1 Federated Query</a> features.  Which approach is superior will depend on the particulars of the situation, including how large the data is, how often it changes, and the frequency of queries which need data from different divisions.  Federated Query would probably not be ideal for the situation described here, but should be considered by people building systems like this.
-</li></ul>
-
-  </section>
-  <section>
-    <h3>Cache Management Using HTTP</h3>
-
-    <p class="note">Factor out the Last-Modified and Expires stuff,
-    from the previous section, and put it here.</p>
-
-    <p class="note">Show that instead of expires like this, it could
-    be done with [an Expiration; inDataset &lt;>; atTime ...;
-    ofLayer]</p>
-
-
-  </section>
-
-
-  <section>
-    <h3>Keeping Derived Information Separate</h3>
-
-    <p>The Federated Phonebook example shows several features of
-    layers, but leaves out a few.  In this example we will show the
-    use of privately-named layers and of sharing blank nodes between
-    layers.</p>
-
-    <p>The scenario is this: some divisions use only vcard:n to
-    provide structured name information (keeping given-name and
-    family-name separate), while others use only vcard:fn to provide a
-    formatted-name (with both parts combined).  The politics of the
-    organization make it impractical to tell the divisions to all use
-    vcard:n or all use vcard:fn, or both.  Meanwhile, several
-    different tools are being written to use this employee directory,
-    including a WebApp, a command-line app, and apps for several
-    different mobile platforms.  Does each app have to be written to
-    understand both vcard:n and vcard:fn? </p>
-
-    <p>HQ decides the solution is for them to run a single process
-    (which they call "namefill") to normalize the data, making
-    sure that every entry has both vcard:n and vcard:fn data, no
-    matter what the division provided.  The process is fairly simple;
-    after any layer is reloaded, a program runs which looks at that
-    layer and fills in the missing name data. </p>
-
-    <p>Because of the tricky politics of the situation, however, HQ
-    decides it would be best to keep this "filled in" data separate.
-    In some cases their program might not fill in the data properly.
-    For example, how can a program tell from the formatted name
-    "Hillary Rodham Clinton" that "Rodham Clinton" is the family-name?
-    The solution is to keep the output of the program in a separate
-    layer, so clients (and people trying to debug the system) can tell
-    this filled-in data did not come from the division itself. </p>
-
-    <p>The result is a dataset like this:
-    </p>
-
-    <pre class="example">@prefix hq: &lt;http://example.com/hq-vocab#>.
[email protected] v:  &lt;http://www.w3.org/2006/vcard/ns#>.
[email protected] ht: &lt;http://example.org/http-vocab#>.
- &lt;http://uswest.internal.example.com/employees.rdf> {
-    # an employee
-    _:u331 a v:VCard
-           v:fn "John Wayne"&nbsp;;
-           v:email "[email protected]" .
-           v:tel [ a v:Work, v:Pref&nbsp;;
-                   rdf:value "+213 555 5555" ].
-    ...
- }
- hq:namefill602 {
-    _:u331 v:n [
-           v:family-name "Wayne";
-           v:given-name "John"
-    ]
- }
- ...
- # default graph has metadata
- {
-   hq:parentCo hq:division hq:div1, hq:div2, hq:div3, ...
-   &lt;http://uswest.internal.example.com/employees.rdf>; 
-     hq:feedFrom hq:div1;
-     hq:namefillLayer hq:namefill602
-  ...
- } 
-</pre>
-
-<p>In serializing this, we needed to introduce a blank node label
-("_:u331"), because that blank node (representing the employee) occurs
-in two different layers.
-</p>
-
-<p>The example also shows the creation of a new layer name
-(hq:namefill602) for the layer filled in by our namefill program.  We
-use one new layer for each feed, instead of one layer for all the
-output of the namefill program, so we have less work to do when a
-single feed layer is reloaded.
-</p>
-
-<p>The techniques in this example apply equally well to information that
-is derived as part of logical inference, such as done by an RDFS, OWL,
-or RIF reasoner.  In these more general cases, it may be that one
-layer can be used for all derived information, or, at the other end of
-the granularity spectrum, that a new layer is used for the triples
-derived in each step of the process.
-</p>
-
-  </section>
-  <section>
-    <h3>Archiving Data With Static Layers</h3>
-
-    <p>One more variation on the federated phonebook scenario: what if
-    HQ wants to be able to look up old information?  For instance,
-    what happens when an employee leaves and is no longer listed in a
-    division phonebook?  It could be nice if the search client could
-    report that the employee is gone, rather than leaving people
-    wondering it they've made a mistake with the name. </p>
-
-    <p>To address this, HQ's data-loading client will not simply
-    delete a layer before reloading it.  Instead, it will first copy
-    the data to a new, archival layer.  After three reloads, the
-    database might look something like this: </p>
-
-<pre class="example">@prefix hq: &lt;http://example.com/hq-vocab#&gt;.
[email protected] hqa: &lt;http://example.com/hq/archive/&gt;
[email protected] v:  &lt;http://www.w3.org/2006/vcard/ns#&gt;.
[email protected] ht: &lt;http://example.org/http-vocab#&gt;.
-hqa:0001 {
-    ... oldest version
-}
-hqa:0002 {
-   ... middle version
-}
-&lt;http://uswest.internal.example.com/employees.rdf&gt; {
-    ... current version
-}
-# default graph
-{
-   hqa:0001 hq:startValidTime ...time... &nbsp;;
-            hq:endValidTime  ...time... .
-   hqa:0002 hq:startValidTime ...time... &nbsp;;
-            hq:endValidTime  ...time... .
-   &lt;http://uswest.internal.example.com/employees.rdf&gt; 
-       hq:snapshot hqa:0001, hqa:0002.
-   ....
-}
-</pre>
-
-<p>This model uses static layers, whose contents are never supposed to
-change.  (They are still different from RDF Graphs in that they retain
-their own identity; two static layers containing the same triples can
-have different metadata.)  For each static layer, we record the time
-interval for which it was current (its
-<a href="http://en.wikipedia.org/wiki/Valid_time">valid time</a>) and what it is a
-snapshot of.
-</p>
-
-<p>The URL for each static layer is generated by incrementing a sequence
-counter.  To follow Linked Data principles, HQ should provide RDF
-serializations of the contents of each layer in response to
-dereferences of these URLs.  (When the state of layers is
-obtained like this, with separate HTTP responses for each one, a blank
-node appearing on multiple layers will appear as multiple blank nodes.
-For blank node sharing to work, the dataset which serializes the
-contents of all the relevant layers must be transmitted or queried as
-a unit.)
-</p>
-
-<p>There is nothing about this architecture that prevents the archival
-data from being modified. The people maintaining the system simply agree
-not to change it.  If this is not sufficient, other approaches could
-be designed, such as generating the URL using a cryptographic hash of
-the layer contents.
-</p>
-
-<p>Another variant on this design is to put the feed data directly into
-an archival layer, instead of having the current data in a the same
-layer as the feed..  If the data is likely to grow stale (not be kept
-in sync with the feed master data), this may be a better approach,
-reducing the possibility of people unknowingly using outdated
-information.
-</p>
-
-</section>
-</section>
-
-<section>
-  <h2>Issues</h2>
-
-  <p>Do the named graphs in a dataset include all the triples in the
-  layers with those names, or only some of them?  Aka partial-graph or
-  complete-graph semantics.</p>
-
-  <p>Can blank nodes be shared between layers?</p>
-
-  <p>What do we do about RDF reification.  Should we try to fix it to
-  be talking about layers?</p>
-
-  <p>How should we talk about change-over-time?  The archiving example
-  gets into it right now.</p>
-  
-
-</section>
-
-
-<section class="appendix informative" id="changes">
-  <h2>Changes</h2>
-  <ul>
-    <li>2012-05-02: Removed obsolete text from the introduction, removed the section on datasets borrowed from RDF Concepts, and added many entries to Concepts (and renamed it from Terminology).</li>
-    <li>2012-05-01: Starting with a little text from RDF Concepts, a few ideas, and the text from <a href="http://www.w3.org/2011/rdf-wg/wiki/Layers">Layers</a></li>
-  </ul>
-</section>
-
-
-<section id="references">
-</section>
-
-  </body>
-</html>
-
+</body>
+</html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/rdf-spaces/index.html	Tue May 15 10:10:48 2012 -0700
@@ -0,0 +1,1533 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+    <title>RDF Spaces and Datasets</title>
+    <style type="text/css">
+.figure { font-weight: bold; text-align: center; }
+table.xsd-types td, table.xsd-types th { border: 1px solid #ddd; padding: 0.1em 0.5em; }
+    </style>
+    <script src='../ReSpec.js/js/respec.js' class='remove'></script>
+    <script class='remove'>
+      var respecConfig = {
+          // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+          specStatus:           "ED",
+          
+          // the specification's short name, as in http://www.w3.org/TR/short-name/
+          shortName:            "rdf-spaces",
+
+          // if your specification has a subtitle that goes below the main
+          // formal title, define it here
+          // subtitle   :  "an excellent document",
+
+          // if you wish the publication date to be other than today, set this
+          // publishDate:  "2009-08-06",
+
+          // if the specification's copyright date is a range of years, specify
+          // the start date here:
+          //          copyrightStart: "2012",
+
+          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+          // and its maturity status
+//          previousPublishDate:  "2004-02-10",
+//          previousMaturity:  "REC",
+
+          // if there a publicly available Editor's Draft, this is the link
+//
+          edDraftURI:           "http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-spaces/index.html",
+
+          // if this is a LCWD, uncomment and set the end of its review period
+          // lcEnd: "2009-08-05",
+
+          // if there is an earler version of this specification at the Recommendation level,
+          // set this to the shortname of that version. This is optional and not usually
+          // necessary.
+          //          prevRecShortname: "rdf-concepts",
+
+          // if you want to have extra CSS, append them to this list
+          // it is recommended that the respec.css stylesheet be kept
+          extraCSS:             ["http://dvcs.w3.org/hg/rdf/raw-file/default/ReSpec.js/css/respec.css"],
+
+          // editors, add as many as you like
+          // only "name" is required
+          editors:  [
+              { name: "TBD", url: "",
+                company: "", companyURL: "",
+              },
+          ],
+          otherContributors: {
+              "Contributor": [
+	      { name: "Sandro Hawke", url:"http://www.w3.org/People/Sandro",
+	      company:"W3C", companyURL: "http://www.w3.org", note:"Initial text"},
+	      ]
+          },
+
+          // authors, add as many as you like. 
+          // This is optional, uncomment if you have authors as well as editors.
+          // only "name" is required. Same format as editors.
+
+          //authors:  [
+          //    { name: "Your Name", url: "http://example.org/",
+          //      company: "Your Company", companyURL: "http://example.com/" },
+          //],
+          
+          // name of the WG
+          wg:           "RDF Working Group",
+          
+          // URI of the public WG page
+          wgURI:        "http://www.w3.org/2011/rdf-wg/",
+          
+          // name (with the @w3c.org) of the public mailing to which comments are due
+          wgPublicList: "public-rdf-comments",
+          
+          // URI of the patent status for this WG, for Rec-track documents
+          // !!!! IMPORTANT !!!!
+          // This is important for Rec-track documents, do not copy a patent URI from a random
+          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+          // Team Contact.
+          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46168/status",
+
+          // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
+          // throughout the generated specification. The triples generated use vocabulary items
+          // from the dcterms, foaf, and bibo. The parameter defaults to false.
+          doRDFa: true,
+      };
+
+//  A number of references have been patched into the local berjon.biblio and need to be added to the global biblio in CVS:
+    </script>
+
+    
+    <style type="text/css">
+
+     .alert {
+         padding: 1em; 
+         margin: 0em; 
+         margin-bottom: 2em; 
+
+         border:2px solid blue; 
+
+         box-shadow: 10px 10px 5px #888;
+         -moz-box-shadow: 10px 10px 5px #888;
+         -webkit-box-shadow: 10px 10px 5px #888;
+
+         -moz-border-radius: 5px;
+         -webkit-border-radius: 5px;
+         -khtml-border-radius: 5px;
+         border-radius: 5px;
+     }
+
+    .separated thead tr th { border:1px solid black; padding: .2em; }
+    .separated tbody tr td { border:1px solid black; text-align: center; }
+    .separated tbody tr td.r { text-align: right; padding: .5em; }
+    .grammar td { font-family: monospace;}
+    .grammar-literal { color: gray;}
+    
+    .example-def { border:1px solid black; padding: 1em; }
+
+    /* --- borrowed from  EXAMPLES --- */
+.exvoc {
+    border: 1px solid #90A0B0;
+    padding:    1em;
+    margin-top: 1em;
+}
+
+.exvoc::before {
+    content:    "Vocabulary Defined For This Example";
+    display:    block;
+    width:      450px;
+    background: #90A0B0;
+    color:  #fff;
+    font-family:    initial;
+    padding:    3px;
+    font-weight:    bold;
+    margin: -1em 0 1em -1em;
+}
+
+.schema {
+   color: #8090A0;
+}
+    </style> 
+	
+  </head>
+
+  <body>
+
+<section id="abstract">
+  <p>This specification introduces the notion of RDF
+  <a>space</a>s&mdash;places to store RDF triples&mdash;and defines a
+  set of mechanisms expressing and manipulating information about
+  them.  Examples of RDF spaces include: an HTML page with embedded
+  RDFa or microdata, a file containing RDF/XML or Turtle data, and a
+  SQL database viewable as RDF using R2RML.  RDF spaces are a
+  generalization of SPARQL's <a>named graph</a>s, providing a standard
+  model with formal semantics for systems which manage multiple
+  collections of RDF data. </p>
+</section>
+
+<section id="sotd">
+  <div class="alert">
+    <h2>Editor's Draft Status</h2>
+    
+    <p>Closing in on FPWD IMHO, but not there yet.  The
+    "@@@" flags mark the places where I'm pretty sure something is
+    needed before FPWD.</p>
+
+    <p>This text might be re-factored into other the other RDF
+    documents.  The Use Cases and Example would probably end up in a
+    WG Note.</p>
+
+  </div>
+</section>
+
+<section class="informative">
+    <h2>Introduction</h2>
+
+
+    <p>The <a href="http://www.w3.org/TR/rdf11-concepts/">Resource
+    Description Framework (RDF)</a> provides a simple declarative way
+    to store and transmit information.  It also provides a trivial but
+    effective way to combine information from multiple sources, with
+    graph merging.  This allows information from different people,
+    different organizations, different units within an organization,
+    different servers, different algorithms, etc, to all be combined
+    and used together, without any special processing or understanding
+    of the relationships among the providers.</p>
+
+    <p>For some applications, the basic RDF merge operation is overly
+    simplistic, as extra processing and an understanding of the
+    relationships among the providers may be useful.  This document
+    specifies a way to conveniently handle information coming from
+    multiple sources, by modeling each one as a separate
+    <em>space</em>, and using RDF to express information about these
+    spaces.  In addition to this important concept, we provide a pair
+    of languages&mdash;extensions to existing RDF syntaxes&mdash;
+    which can be used to store or transmit in one document the
+    contents of multiple spaces as well as information about them.
+
+    <p>This approach allows for a variety of use cases (immediately
+    below) to be addressed in a straightforward manner, as shown in <a
+    href="#detailed-example" class="sectionRef"></a>.</p>
+
+</section>
+
+<section>
+  <h2>Use Cases</h2>
+
+  <p>Each of these use cases is initally described in terms of the
+  following scenario.  Details of how each use case might be addressed
+  using the technologies specified in this document are in <a
+  href="#detailed-example" class="sectionRef"></a>.</p>
+
+  <blockquote style="font-style: italic">
+
+    <p>The Example Foundation is a large organization with more than
+    ten thousand employees and volunteers, spread out over five
+    continents.  It has branches in <b>25 different countries</b>, and
+    those divisions have considerable autonomy; they are only loosely
+    controlled by the parent organization (called "headquarters" or
+    "HQ") in Geneva.</p>
+
+    <p>HQ wants to help the divisions work together better.  It
+    decides a first step is to provide a simple but complete directory
+    of all the Example personnel.  Until now, each division has
+    maintained its own directory, using its own technology.  HQ wants to gather them all together, building a <b>federated phonebook</b>.  They want
+    to be able to find someone's phone number, mailing address,
+    and job title, knowing only their name or email addresses.  Later,
+    they hope to extend the system to allow finding people based on
+    their areas of interest and expertise.</p>
+
+    <p>HQ understands that people will want access to the phonebook in
+    many different computing environments and with different
+    languages, social norms, and application styles.  Users are going
+    to want at least one Web based user interface (UI), but they will
+    also want mobile UIs for different platforms, desktop UIs for
+    different platforms, and even to look up information via text
+    messaging.  HQ does not have the resources to build all of these,
+    so they intend to provide <b>direct access to the data</b> so that the
+    divisions can do it themselves as needed.</p>
+
+  </blockquote>
+  
+  <p>Each of the sections below, after the first, contains a new
+  requirement, something additional that users in this scenario want
+  the system to do.  Each of these will motivate the features of the
+  technologies specified in this rest of document.</p>
+
+  <section id="uc-start">
+    <h2>Baseline Solution (Just Triples)</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>As a starting point, HQ needs to gather data from each
+      division and re-publish it, in one place, for use by the
+      different UIs.</p>
+
+    </blockquote>
+    
+    <p>This is a general use case for RDF, with no specific need for
+    using <a>space</a>s or <a>dataset</a>s.  It simply involves
+    divisions pubishing RDF data on the web (with some common
+    vocabulary and with access control), then HQ merging it and
+    putting it on their website (with access control).</p>
+
+    <p>For an example of how this baseline could be implemented, see
+    <a href="#example-start" class="sectionRef"></a></p>
+
+  </section>
+
+  <section id="uc-web">
+    <h2>Showing Provenance</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>A user says: I'm looking at an incorrect phonebook entry.  It
+      has the name of the person I'm looking for, but it's missing
+      most of the record.  I can't even tell which division the person
+      works for.  I need to know who is responsible for this
+      information, so I can get it corrected.
+      </p>
+
+      <p>While this might be address by including a "report-errors-to"
+      field in each phonebook entry, HQ is looking ahead to the day
+      when other information is in the phonebook &mdash; like which
+      projects the person has worked on &mdash; which might be come
+      from a variety of others sources, possibly other divisions.</p>
+
+    </blockquote>
+    
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-web" class="sectionRef"></a></p>
+
+  </section>
+
+  <section id="uc-process">
+    <h2>Maintaining Derived Data</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>It turns out different divisions are using somewhat different
+      vocabularies for publishing their data.  HQ writes a program to
+      translate, but they need the output of that program to be
+      correctly attributed, in case it turns out to be wrong.
+      </p>
+
+    </blockquote>
+    
+    <p>This use case motivates sharing of blank nodes between named
+    graphs, as seen in the example.</p>
+
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-process" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section id="uc-reported">
+    <h2>Distributed Harvesting</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>It turns out some divisions do not have centralized
+      phonebooks.  Division 3 has twelve different departments, each
+      with its own phonebook.  Divsion 3 can do the harvesting from
+      its departments, but it does not want to be in the loop for
+      corrections; it wants those to go straight back to the relevant
+      department.
+      </p>
+
+    </blockquote>
+    
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-reported" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section id="uc-untrusted">
+    <h2>Loading Untrusted Datasets</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>A user reports: There's information here that says it's from
+      our department, but it's not.  Somehow your provenance
+      information is wrong.  We need to see the provenance of the
+      provenance!</p>
+
+    </blockquote>
+    
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-untrusted" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section id="uc-transtime">
+    <h2>Showing Revision History</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>Division 14's legal department says: "We're doing an
+      investigation and we need to be able to connect people's names
+      and phone numbers as they used to be.  Can you include archival
+      data in the data feed, so we we can search the phonebook as it
+      was on each day of September, last year?"
+      </p>
+
+    </blockquote>
+    
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-transtime" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section id="uc-validtime">
+    <h2>Expressing Past or Future States</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>Division 5 says: "We're planning a major move in three
+      months, to a neighboring city.  Everybody's office and phone
+      number will have to change.  Can we start putting that
+      information in the phonebook now, but mark it as not effective
+      until 20 July?  After the move, we'll also need to see the old
+      (no-longer-in-effect) data for a while, until we get everything
+      straightened out.</p>
+
+    </blockquote>
+    
+    <p>This use case, contrasted with the previous one, shows the
+    difference between <em>Transaction Time</em> and <em>Valid
+    Time</em> in bitemporal databases.  After Division 5's move, the
+    "old" phone numbers are not just the old state of the database;
+    they reflect the old state of the world.  It is possible that some
+    time after the move, an error in the pre-move data might need to
+    be corrected.  This would require a new transaction time, even
+    though the valid-time has already ended.</p>
+
+    <p>Use case sightings:</p>
+    <ul>
+      <li><a href="http://www.jenitennison.com/blog/node/101">Temporal Scope for RDF Triples</a>, Jeni Tennison's report of attempting to solve this problem in UK Government data.
+      </li>
+      <li><a
+    href="http://lists.w3.org/Archives/Public/public-rdf-wg/2012May/0099.html">Vocab
+    terms for owner, validFrom and validUntil</a>, Manu Sporny
+    reports PaySwarm wants to record ownership information for
+    particular time ranges.</li>
+    </ul>
+
+    <p>For a discussion of how this use case could be addressed, see
+    <a href="#example-validtime" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section>
+    <h2>Vendor-Neutral SPARQL Backup</h2>
+
+    <blockquote style="font-style: italic">
+
+      <p>
+      </p>
+
+    </blockquote>
+    
+
+
+    <p>@@@ we want to be able to dump the database and load it in a different system</p>
+
+    <p>@@@ This doesn't seem to belong here.   Maybe we have Federated Phonebook use cases, and *other* ones, too?</p>
+  </section>
+
+
+</section>
+
+
+
+<section>
+  <h2>Concepts</h2>
+
+
+  <section>
+    <h2>Space</h2>
+
+    <p class="issue">The term "space" might change.  The final
+    terminology has not yet been selected by the Working Group.  Other
+    candidates include "g-box", "data space", "graph space", "(data)
+    surface", "(data) layer", "sheet", and "(data) page".</p>
+
+    <p>An RDF <dfn>space</dfn> is anything that can reasonably be said
+    to explicitly contain zero or more RDF triples and has an identity distinct
+    from the triples it contains.  Examples include:
+    </p>
+    
+    <ul>
+
+      <li>a human-readable Web page, such as an HTML page containing
+      RDFa markup, microdata markup, or embedded turtle.</li>
+
+      <li>a file, in a computer's filesystem, containing RDF data
+      expressed in RDF/XML, N-Triples, Turtle, etc.</li>
+
+      <li>a machine-readable Web page containing RDF data expressed in
+      RDF/XML, N-Triples, Turtle, etc.</li>
+
+      <li>a SQL database which provides an RDF view of its data,
+      perhaps using R2RML</li>
+
+      <li>the default graph or any of the named graphs available via a
+      SPARQL endpoint</li>
+    </ul>
+
+    <p>Examples of things that are not spaces:</p>
+
+    <ul>
+
+      <li>Natural language text.  While it might be possible extract
+      some of the meaning of the text and express that meaning in RDF
+      triples, those triples are not explicit and in practice might
+      vary from one extractor to the next.</li>
+
+      <li>RDF Graphs.  Since they are just mathematical sets of RDF
+      triples, they have no distinct identity apart from their
+      contents.  For example, if two systems have in memory the RDF
+      graph { &lt;a> &lt;b> &lt;c> }, any metadata about the graph in
+      one system logically applies to the graph in the other system,
+      since technically it is the same graph.  (If this seems
+      counter-intuitive, you may be among the many who have been using
+      the term "graph" to refer to what we now call a space.  It may
+      help to think about a "graph space" (a place to put a graph) and
+      a "graph state" (the state of that space).  That "graph state"
+      is what the existing specifications call an "RDF Graph").</li>
+
+      <li>Web pages containing embedded RDF but which do not contain a
+      well-defined set of triples at any given point in time.  For
+      example: a Web Service which returns RDF data including the
+      client's IP address, or a site which customizes the data
+      presented based on client login cookies.  Such resources might
+      be called "hyperspaces".</li>
+
+    </ul>
+
+  </section>
+
+  <section>
+    <h2>Quad and Quadset</h2>
+
+    <p>We define an RDF <dfn>quad</dfn> as the 4-tuple
+    (<i>subject</i>, <i>predicate</i>, <i>object</i>,
+    <i>space</i>).</p>
+
+    <p>Informally, a quad should be understood as a statement that the
+    RDF triple (<i>subject</i>, <i>predicate</i>, <i>object</i>) is in
+    the <a>space</a> <i>space</i>.</p>
+
+    <p>We define an RDF <dfn>quadset</dfn> as a set containing (zero
+    or more) RDF Quads and (zero or more) RDF Triples.  A quadset is
+    thus an extension to the concept of an RDF Graph (a set containing
+    zero or more RDF triples) to also potentially include statements
+    about triples being in particular spaces.</p>
+
+  </section>
+
+
+  <section>
+    <h2>Dataset</h2>
+
+    <p>A <dfn>dataset</dfn> is defined by <a
+    href="http://www.w3.org/TR/sparql11-query/#rdfDataset">SPARQL
+    1.1</a> as a structure consisting of:</p>
+    
+    <ol>
+      
+      <li>A distinguished RDF Graph called the <dfn>default graph</dfn></li>
+      
+      <li>A set of (<i>name</i>, <i>graph</i>) pairs, where
+      <i>name</i> is an IRI and the <i>graph</i> is an RDF Graph.  No
+      two pairs in a dataset may have the same <i>name</i>.</li>
+      
+    </ol>
+    
+    <p>This definition forms the basis of the SPARQL Query semantics;
+    each query is performed against the information in a specific
+    dataset.</p>
+    
+    <p>Although the term is sometimes used more loosely, a dataset is
+    a pure mathematical structure, like an RDF Graph or a set of
+    integers, with no identity apart from its contents.  Two datasets
+    with the same contents are in fact the same dataset, and one
+    dataset cannot change over time.</p>
+
+    <p>The word <strong>"default"</strong> in the term "default graph"
+    refers to the fact that in SPARQL, this is the graph a server uses
+    to perform a query when the client does not specify which graph to
+    use.  The term is not related to the idea of a graph containing
+    default (overridable) information.  The role and purpose of the
+    default graph in a dataset varies with application.</p>
+
+  </section>
+
+  <section>
+    <h2>Named Graph</h2>
+
+    <p>SPARQL formally defines a <em>named graph</em>
+    following <b>[Carroll]</b>, to be any of the (name, graph) pairs in a
+    <a>dataset</a>.</p>
+
+    <p>In practice, the term is often used to refer to the graph part
+    of those pairs.  This is the usage we follow in this document,
+    saying that a graph is a <dfn>named graph</dfn> in some dataset if
+    and only if it appears as the graph part of a (name, graph) pair
+    in that dataset.  Note that "named graph" is a relation, not a
+    class: we say that something is a named graph <em>of a
+    dataset</em>, not simply that it is a named graph.</p>
+
+    <p>The term is also sometimes used to refer to the slot part of
+    the (name, slot) pairs in a <a>graph store</a>.  For example, the
+    text of <a
+    href="http://www.w3.org/TR/2012/WD-sparql11-update-20120105/">SPARQL
+    1.1 Update</a> says, "This example copies triples from one named
+    graph to another named graph".  For clarity, we avoid calling
+    these "named graphs" and instead call them "named slots" of the
+    graph store.</p>
+
+  </section>
+
+    
+  <section id="qdmap">
+    <h2>Quadset/Dataset Relationship</h2>
+
+    <p>A <dfn>quad-equivalent dataset</dfn> is a <a>dataset</a> with
+    no empty named graphs.  A <dfn>non-quad-equivalent dataset</dfn>
+    is a dataset in which one or more of its named graphs is empty.
+    Every non-quad-equivalent dataset has a corresponding
+    quad-equivalent dataset formed by removing the (name, graph) pairs
+    where the graph is empty.</p>
+
+    <p><a>Quadset</a>s and quad-equivalent datasets are isomorphic,
+    and given identical declarative semantics in <a href="#semantics"
+    class="sectionRef"></a>.  The isomorphism is:</p>
+
+    <ul>
+
+      <li>the triples in the quadset correspond to the triples in default
+     graph of the dataset;</li>
+
+     <li>each quad corresponds to a triple in named graph: the quad (S
+     P O Sp) corresponds to the triple (S P O) in the graph paired
+     with the name Sp.</li>
+
+    </ul>
+
+    <p>The phrasing <dfn>quads in a dataset</dfn> is thus shorthand
+    for: quads in some quadset which is isomorphic to a given dataset.
+    If the dataset is a <a>non-quad-equivalent dataset</a>, then the
+    isomorphism is to the dataset produced by removing all its empty
+    named graphs.</p>
+
+    <p>In order to promote interoperability and flexibility in
+    implementation techniques &mdash; to allow datasets and quadsets
+    to be used interchangably &mdash; systems which handle datasets
+    SHOULD NOT give significance to empty named graphs.</p>
+
+    <p class="issue">
+      Can we take a stronger stand against non-quad-equivalent
+      datasets?  Maybe we can use the terms "proper" and "improper",
+      or something like that.  Improper datasets might also include
+      ones which use the same name in more than one pair.  Combining
+      these, like removing empty named graphs, is how you convert an
+      improper dataset to a proper one.
+    </p>
+
+  </section>
+
+  <section>
+    <h2>Graph Store</h2>
+    
+    <p>SPARQL 1.1 Update defines a mutable (time-dependent) structure
+    corresponding to a <a>dataset</a>, called <dfn>graph store</dfn>.
+    It is defined as:</p>
+
+    <ol>
+
+      <li>A distinguished slot for an RDF Graph</li>
+      
+      <li>A set of (<i>name</i>, <i>slot</i>) pairs, where the slot holds an RDF Graph
+      and the name is an IRI.  No two pairs in a graph store may have the same <i>name</i>.</li>
+      
+    </ol>
+    
+    <p>A "slot" in this definition is an RDF space.</p>
+
+    <p>A dataset can be thought of as the state of a <a>graph
+    store</a>, just like an RDF graph can be thought of as the state
+    of a <a>space</a>.</p>
+
+  </section>
+
+
+  <section>
+    <h2>Merge and Union</h2>
+
+    <p>RDF graphs are usually combined in one of two ways:</p>
+
+    <ul>
+      <li>The <dfn>union</dfn> of two graphs is the set-union of the set of triples in each graph.</li>
+      <li>The <dfn>merge</dfn> of two graphs is the set-union of the set of triples in each graph, after any blank nodes that occur in both graphs are "renamed apart".</li>
+    </ul>
+
+    <p>This difference is not noticable when graphs are being
+    expressed in an orginary RDF syntax, like RDF/XML, RDFa, or
+    Turtle, because they provide no mechanism for transmitted two
+    graphs which have a blank node in common.  The difference can
+    appear, however, in systems and languages which handle datasets or
+    in APIs which allow blank nodes to be shared between graphs.</p>
+
+    <p>We define a <dfn>union dataset</dfn> to be a <a>dataset</a> in
+    which its <a>default graph</a> is the <a>union</a> of all its
+    <a>named graph</a>s.  Some systems provide special, simplified
+    handling of union datasets.</p>
+
+    <p>We define a <dfn>merge dataset</dfn> to be a <a>dataset</a> in
+    which its <a>default graph</a> is the <a>merge</a> of all its
+    <a>named graph</a>s.</p>
+
+    <p>We define the union and merge of quadsets (and thus datasets)
+    as the set merge of their constituent triples and quads; in the
+    case of a merge, it is after any shared blank nodes have been
+    renamed apart.</p>
+
+  </section>
+
+
+  <section>
+    <h2>Untrusting Merge</h2>
+
+    <p>The act of <dfn>renaming the graphs</dfn> in a dataset is to
+    create another dataset which differs from the first only in that
+    all the IRIs used as graph names are replace by fresh "Skolem"
+    IRIs.  This replacement occurs in the name slot of the
+    (name,graph) pairs, and in the triples in the default graph, but
+    <em>not</em> in the triples in the named graphs.</p>
+
+    <p>Logically, this operation is equivalent to partially
+    un-labeling an RDF Graph (turning some IRIs into blank nodes),
+    then Skolemizing those blank nodes.  As an operation, it discards
+    some of the information and adds more true information; it is a
+    sound but not complete reasoning step.  It can be made complete by
+    <dfn>recording</dfn> the relationship between the old graph names
+    and the new ones, using some vocabulary such as owl:sameAs.</p>
+
+    <p>For example, a recording graph_rename operation might take as input:</p>
+    <pre>@prefix : &lt;http://example.com/>
+:g1 { :a :b :c }
+:d :e :f</pre>
+    <p>and produce:</p>
+    <pre>@prefix : &lt;http://example.com/>
+:fe2b9765-ba1d-4644-a335-80a8c3786c8d { :a :b :c }
+:d :e :f
+:fe2b9765-ba1d-4644-a335-80a8c3786c8d owl:sameAs :g1
+</pre>
+
+    <p>Given the semantics of datasets, informally described above and
+    formally stated in <a href="#semantics" class="sectionRef"></a>,
+    and the semantics of OWL, where { ?a owl:sameAs ?b } means that
+    the terms ?a and ?b both denote the same thing, the second dataset
+    above entails the first and includes only additional information
+    that is known to be true.  (Slight caveat: the new information is
+    only true if the assumptions of the name-generation function are
+    correct, that the name is previously unused and this naming agent
+    has the right to claim it.)</p>
+
+    <p>A relatated operation, <dfn>sequestering</dfn> the default
+    graph, is to create a new dataset which differs from the first
+    only in that the the triples in the default graph of the input
+    appear instead in a new, freshly-named, <a>named graph</a> of the
+    output.  Sequestering returns both the new dataset and the name
+    generated for the new graph: <code>sequester(D1) -> (D2,
+    generatedIRI)</code>.</p>
+
+    <p>Used together, the operations of <a>renaming the graphs</a>,
+    <a>sequestering</a> the default graphs, and then <a>merging
+    datasets</a>, constitutes an <dfn>untrusting merge</dfn> of
+    datasets.  This operation provides the functionality required for
+    addressing the use case described in <a href="#uc-untrusted"
+    class="sectionRef"></a> and is illustrated in <a
+    href="#example-untrusted" class="sectionRef"></a>.  It uses quads
+    to address some&mdash;perhaps all&mdash;of the need for quints
+    or nested graphs.</p>
+
+    <p>More precisely:</p>
+    
+    <div style="margin-left: 2em;">
+      <pre>function untrusted_merge(D1, ... Dn):
+   for i in 1..n:
+      RDi = rename_graphs(Di)
+      (SRDi, DGNi) = sequester(RDi)
+   return (merge(SRD1, ... SRDn), (DGN1, ... DGNn))</pre>
+    </div>
+
+   <p>Here, <tt>untrusted_merge</tt> returns a single dataset and a list of
+   the names of the graphs (in that dataset) which contain the triples
+   that were in the default graphs, possibly augmented with
+   <a>recording</a> triples.  Whether recording is done or not is
+   hidden inside the rename_graphs function, and is
+   application-dependent.</p>
+
+  </section>
+
+  
+</section>
+
+<section>
+  <h2>Semantics</h2>
+
+  <p>This section specifies a declarative semantics for <a>quad</a>s,
+  <a>quadset</a>s, and <a>dataset</a>s, allowing them to be used to
+  express knowledge, especially knowledge about spaces.  This makes
+  the languages defined in <a href="#syntax"
+  class="sectionRef"></a> suitable for conveying knowledge about
+  spaces and providing a foundation for addressing the challenges
+  described in <a href="#use-cases" class="sectionRef"></a>.</p>
+
+  <p>@@@ the section needs some revision by someone with a good ear
+  for formal semantics, and probably some references to the old and/or new versions of RDF Semantics.</p>
+
+  <p>The fundamental notion of RDF spaces is that they can contain
+  triples.  This is formalized with the relation CT(S, T) which is
+  informally understood to hold true for any triple T and space S such
+  that S explicitely contains T.</p>
+
+  <p>The basic declarative meaning (that is, the truth condition) of
+  RDF quads is this:</p>
+
+  <div style="padding: 1em; border: 1px solid blue;">
+
+    <p>The RDF <a>quad</a> (s, p, o, sp) is true in I if and only if CT(I(sp), triple(s, p, o)).</p>
+
+  </div>
+
+  <p>The declarative meaning of a quadset is to simply read the
+  quadset as a conjunction of its quads and its triples.  Given <a
+  href="#qdmap">the structural mapping between quadsets and
+  datasets</a>, the truth condition for datasets follows:</p>
+
+  <div style="padding: 1em; border: 1px solid blue;">
+
+    <p>The RDF <a>dataset</a> (DG, (N1,G1),... (Ni,Gi), ...(Nn,Gn)) is
+    true in I if and only if:</p>
+
+    <ol>
+    <li>DG is true in I, and</li>
+    <li>For every (Ni,Gi) (1&lt;=i&lt;=n):
+    <ul>
+      <li>For every triple T in Gi:
+      <ul>
+	<li>CT(I(Ni),T)</li>
+      </ul>
+      </li>
+    </ul>
+    </li>
+    </ol>
+
+  </div>
+
+  <p>Some implications of these truth conditions: </p>
+
+  <ul>
+
+    <li><p>A dataset with no named graphs has the same declarative
+    meaning as its default graph.  A quadset with no quads has the
+    same declarative meaning as the RDF graph consisting of the
+    triples in the quadset.  </p><p>This fits the intuition that datasets and
+    quadsets are extensions of RDF Graphs and applies to the syntax as
+    well: a Trig document without any named graphs is syntactically
+    and semantically a Turtle document; an N-QUads document without
+    any quads is syntactically and semantically an N-Triples
+    document.</p></li>
+
+    <li>
+    <p>The empty named graphs in a <a>non-quad-equivalent dataset</a>
+    have no effect on its meaning.  Replacing such a dataset with its
+    equivalent without the empty named graphs does not change its
+    meaning.</p>
+    </li>
+
+  </ul>
+
+  <p class="note">
+    We say nothing here about the fact that the truth value of a quad
+    is likely to change over time.  Time is orthogonal to RDF
+    semantics, and quads present no fundamentally different issue
+    here.  When the world changes state, the truth value of RDF
+    triples or quads might change.  This occurs when a triple is put
+    in or taken out of a space, but it also occurs with "normal" RDF
+    when, for instance, someone changes their address and different
+    vcard triples about them become true.  Some approaches to handling
+    change-over-time are discussed in <a href="#example-valid-time"
+    class="sectionRef"></a> and <a href="#example-transaction-time"
+    class="sectionRef"></a>.
+  </p>
+
+  <p>@@@ explain why we use partial-graph semantics, and how in most
+  applications its bad to drop information, but sometimes it's
+  necessary, and sometimes you only have incomplete information.</p>
+
+</section>
+
+
+<section id="syntax">
+  <h2>Dataset Languages</h2>
+
+  <p>This section contains specifications of languages for serializing
+  <a>quad-equivalent dataset</a>s.  N-Quads documents and Trig
+  documents have identical semantics, since they each serialize the
+  same structure and follow <a href="#semantics"
+  class="sectionRef"></a>.</p>
+
+  <p>Dataset information may also be conveyed and manipulated using
+  SPARQL or using RDF triple-based tools and languages as per <a
+  href="#folding" class="sectionRef"></a>.</p>
+
+  <section>
+    <h3>N-Quads</h3>
+
+    <p>The syntax of N-Quads is the same as the syntax of N-Triples,
+    except that a fourth term, identifying an RDF space, may
+    optionally be included on each line, after the "object" term.</p>
+
+    <p>Formally, the N-Quads grammar is <a href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#n-triple-grammar">the N-Triples
+    Grammar</a> modified by removing productions [1] and [2], and
+    adding the following productions:</p>
+
+<div style="margin: 1em; margin-top: 0; padding: 1em; border: 1px solid gray;">
+    
+<table border="0" class="grammar">
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-sandro-nquads-nquadsDoc" name="prod-sandro-nquads-nquadsDoc"></a>[<span class="prodNo">1q</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">nquadsDoc</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-statement">statement</a></span>? (<span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-EOL">EOL</a></span> <span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-statement">statement</a></span>)* <span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-EOL">EOL</a></span>?</code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-sandro-nquads-statement" name="prod-sandro-nquads-statement"></a>[<span class="prodNo">2q</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">statement</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-subject">subject</a></span> <span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-predicate">predicate</a></span> <span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-object">object</a></span> <span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-space">space</a></span>? <span class="grammar-literal">"."</span></code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-sandro-nquads-space" name="prod-sandro-nquads-space"></a>[<span class="prodNo">3q</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">space</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-sandro-nquads-IRIREF">IRIREF</a></span></code></td>
+</tr>
+</tbody>
+
+</table>
+
+<p>The grammar symbols 
+<code class="production prod" id="prod-sandro-nquads-EOL">EOL</code>,
+<code class="production prod" id="prod-sandro-nquads-subject">subject</code>
+<code class="production prod" id="prod-sandro-nquads-predicate">predicate</code>
+<code class="production prod" id="prod-sandro-nquads-object">object</code>, and 
+<code class="production prod" id="prod-sandro-nquads-IRIREF">IRIREF</code> are defined in the <a
+href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#n-triple-grammar">the
+N-Triples Grammar</a></p>
+
+</div>
+
+    <p>The following example shows a <a>quadset</a> consisting of two
+    triples and two <a>quads</a>.  The quads both use the same triple,
+    but express the fact that it is in two spaces, "space1" and
+    "space2".</p>
+
+    <pre class="example">&lt;http://example.org/subject> &lt;http://example.org/predicate> &lt;http://example.org/object1>.
+&lt;http://example.org/subject> &lt;http://example.org/predicate> &lt;http://example.org/object2>.
+&lt;http://example.org/subject> &lt;http://example.org/predicate> &lt;http://example.org/object1> &lt;http://example.org/space1>.
+&lt;http://example.org/subject> &lt;http://example.org/predicate> &lt;http://example.org/object1> &lt;http://example.org/space2>.</pre>
+
+  </section>
+
+
+  <section>
+    <h3>Trig</h3>
+
+    <p>The syntax of Trig is the same as the syntax of Turtle except
+    that (name, graph) pairs can be specified by giving an optional
+    <tt>GRAPH</tt> keyword, a "name" term, and a nested Turtle graph expression
+    in curly braces.</p>
+
+
+    <p>Formally, the Trig grammar is <a
+    href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-grammar-grammar">the
+    Turtle Grammar</a> modified by removing productions [1] and [2],
+    and adding the following productions:</p>
+
+    <div style="margin: 1em; margin-top: 0; padding: 1em; border: 1px solid gray;">
+    <table border="0">
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-trig-trigDoc" name="prod-trig-trigDoc"></a>[<span class="prodNo">1g</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">trigDoc</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-trig-statement">statement</a></span>*</code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-trig-statement" name="prod-trig-statement"></a>[<span class="prodNo">2g</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">statement</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-trig-directive">directive</a></span> <span class="grammar-literal">"."</span> | <span class="prod"><a class="grammarRef" href="#prod-trig-triples">triples</a></span> <span class="grammar-literal">"."</span> | <span class="prod"><a class="grammarRef" href="#prod-trig-naming">naming</a></span> | <span class="prod"><a class="grammarRef" href="#prod-trig-wrappedDefault">wrappedDefault</a></span></code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-trig-naming" name="prod-trig-naming"></a>[<span class="prodNo">3g</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">naming</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content">
+  <span class="grammar-literal">"GRAPH"</span>? 
+  <span class="prod"><a class="grammarRef" href="#prod-trig-spaceName">spaceName</a></span> 
+<!--  (  -->
+  ( <span class="grammar-literal">"," </span>
+  <span class="prod"><a class="grammarRef" href="#prod-trig-spaceName">spaceName</a></span> 
+  )* <span class="grammar-literal">"{"</span>
+  <span class="prod"><a class="grammarRef" href="#prod-trig-triples">triples</a></span> 
+  <span class="grammar-literal">"."</span>? 
+  <span class="grammar-literal">"}"</span>  <!--) 
+  |
+  ( "{" 
+  <span class="prod"><a class="grammarRef" href="#prod-trig-triples">triples</a></span> 
+  <span class="grammar-literal">"."</span>? "}" 
+  ( <span class="grammar-literal">";"</span> 
+  <span class="prod"><a class="grammarRef" href="#prod-trig-verb">verb</a></span>
+  <span class="prod"><a class="grammarRef" href="#prod-trig-objectList">objectList</a></span>
+  )? ) -->
+</code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-trig-spaceName"></a>[<span class="prodNo">4g</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">spaceName</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content"> 
+    <span class="prod"><a class="grammarRef" href="#prod-trig-iri">iri</a></span>
+    | <span class="grammar-literal">"DEFAULT"</span>
+</code></td>
+</tr>
+</tbody>
+
+<tbody class="prod">
+<tr valign="baseline">
+<td><a id="prod-trig-wrappedDefault" name="prod-trig-wrappedDefault"></a>[<span class="prodNo">5g</span>]&nbsp;&nbsp;&nbsp;</td>
+<td><code class="production prod">wrappedDefault</code></td>
+<td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td>
+<td><code class="content">
+<span class="grammar-literal">"{"</span> <span class="prod"><a class="grammarRef" href="#prod-trig-triples">triples</a></span> <span class="grammar-literal">"."</span>? <span class="grammar-literal">"}"</span></code></td>
+</tr>
+</tbody>
+
+
+    </table>
+
+
+<p>The grammar symbols 
+
+<code class="production prod" id="prod-trig-directive">directive</code>,
+<code class="production prod" id="prod-trig-triples">triples</code>, and
+<code class="production prod" id="prod-trig-iri">iri</code>
+<!--
+<code class="production prod" id="prod-trig-verb">verb</code>, and
+<code class="production prod" id="prod-trig-objectList">objectList</code>
+-->
+are defined in <a
+href="http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-grammar-grammar">the
+Turtle Grammar</a>
+</p>
+
+
+    </div>
+
+
+    <p>Parsing a Trig document is like parsing a Turtle document
+    except:</p>
+    <ol>
+
+      <li>The result is a <a>dataset</a>, not an RDF Graph</li>
+
+      <li>The triples generated during parsing of the <code
+      class="prod production">naming</code> production go into each
+      <a>named graph</a> and/or the default graph as given in the
+      <code class="prod production">spaceName</code> productions.</li>
+
+      <li>The triples generated during other parsing go into the
+      default graph.</li>
+
+    </ol>
+      
+    <p>
+    <p>Note that the grammar forbids directives between curly braces
+    and empty curly-brace expressions.  Also, note that blank node
+    processing is not affected by curly braces, so conceptually blank
+    node identifiers are scoped to the entire document.</p>
+
+    <p>There is no requirement that <a>named graph</a> names be unique
+    in a document, or that triples in the default graph be
+    continguous. For example, these two Trig document parse to exactly
+    the same Dataset:</p>
+
+    <pre class="example"># Trig Example 1
+    @prefix : &lt;http://example.org/>.
+    :a :b 1.
+    :s1 { :a :b 10 }
+    :s2 { :a :b 20 }
+    :s1 { :a :b 11 }
+    :s2 { :a :b 21 }
+    :a :b 2.
+</pre>
+
+    <pre class="example"># Trig Example 2
+    @prefix : &lt;http://example.org/>.
+    :a :b 1,2.
+    :s1 { :a :b 10,11. }
+    :s2 { :a :b 20,21. }
+</pre>
+
+    <p>The same dataset could be expressed in N-Quads as:</p>
+
+    <pre style="overflow-x:scroll; width:800px;" class="example"># N-Quads for TriG Example 1 and 2
+&lt;http://example/org/a> &lt;http://example/org/b> "1"^^&lt;http://www.w3.org/2001/XMLSchema#integer>.
+&lt;http://example/org/a> &lt;http://example/org/b> "2"^^&lt;http://www.w3.org/2001/XMLSchema#integer>.
+&lt;http://example/org/a> &lt;http://example/org/b> "10"^^&lt;http://www.w3.org/2001/XMLSchema#integer> &lt;http://example/org/s1>.
+&lt;http://example/org/a> &lt;http://example/org/b> "11"^^&lt;http://www.w3.org/2001/XMLSchema#integer> &lt;http://example/org/s1>.
+&lt;http://example/org/a> &lt;http://example/org/b> "20"^^&lt;http://www.w3.org/2001/XMLSchema#integer> &lt;http://example/org/s2>.
+&lt;http://example/org/a> &lt;http://example/org/b> "21"^^&lt;http://www.w3.org/2001/XMLSchema#integer> &lt;http://example/org/s2>.
+</pre>
+
+    <div class="issue">
+      <p>There are several open issues concernting Trig syntax:</p>
+      <ul>
+	<li>Should we call this something other than Trig, since it's a bit different?   Qurtle?  Mugr (multi-graph-rdf)?   Turtle2?  </li>
+	<li>Are braces around default-graph triples required,
+    optional, or disallowed?    Assuming "optional" for now.</li>
+        <li>Is the name prefixed by a keyword?  If so, is the
+    keyword "@graph" or "GRAPH"?   Assuming optional "GRAPH" for now.</li>
+        <li>     Are blank node labels scoped to the document, the
+    curly-brace expression, or the graph name?  Assuming
+    document-scope for now.   This is <a href="http://www.w3.org/2011/rdf-wg/track/issues/21">Issue-21</a>.</li>
+    <li>Can blank node labels be used as space names?
+    Assuming not, for now.</li>
+    <li>Can we provide a way to say a graph is in multiple spaces without repeating it?  Something like [GRAPH] g1, g2, DEFAULT { ... } (where default is a keyword stand-in for the default graph; assuming yes.</li>
+    <li>Can we allow allow people to re-use subject, like:  g1 { ... }; :lastModified .... ?  assuming no; it interacts a bit confusingly with repeated spaceName, and it's not clear what it means for spaceName DEFAULT.</li>
+      </ul>
+    </div>
+
+
+  </section>
+</section>
+
+<section>   <!-- I don't like what respec does with id=conformance -->
+  <h2>Conformance</h2>
+
+  <p>@@@ what to say here?  What kind of think might conform or not
+  conform to this spec?</p>
+
+</section>
+
+<section class="informative appendix">
+
+  <h2>Detailed Example</h2>
+
+  <p>This section presents a design for using <a>space</a>s in constructing a
+  federated information system.  It is intended to help explain and
+  help motivate the designs specified in this document.</p>
+
+  <p>The example covers the same federated phonebook scenario used in
+  <a href="#use-cases" class="sectionRef"></a>, with each specific use
+  case having an example here.</p>
+
+  <div class="alert">
+    <p>@@@ An obsolete but complete version was in the <a
+  href="http://dvcs.w3.org/hg/rdf/raw-file/ee60c6dc8ad4/rdf-spaces/index.html#">May 10 Version</a>.
+  </p>
+  </div>
+
+
+  <section id="example-start">
+    <h2>Showing Triples (v1)</h2>
+
+    <p>@@@ Shows the baseline in <a href="#uc-start" class="sectionRef"></a></p>
+
+  </section>
+
+
+  <section id="example-web">
+    <h2>Showing Web Provenance (v2)</h2>
+
+    <p>@@@ Shows how to address<a href="#uc-web" class="sectionRef"></a></p>
+
+  </section>
+
+
+
+  <section id="example-process">
+    <h2>Showing Process Provenance(v3)</h2>
+
+    <p>@@@ Shows how to address <a href="#uc-process" class="sectionRef"></a></p>
+
+  </section>
+
+
+
+  <section id="example-reported">
+    <h2>Showing Reported Provenance (v4)</h2>
+
+    <p>@@@ Shows how to address <a href="#uc-reported" class="sectionRef"></a></p>
+
+  </section>
+
+
+
+  <section id="example-untrusted">
+    <h2>Showing Untrusted Quads(v5)</h2>
+
+    <p>@@@ Show how to address <a href="#uc-untrusted" class="sectionRef"></a></p>
+    <p>@@@ uses <a>renaming the graphs</a>.</p>
+
+
+  </section>
+
+
+
+  <section id="example-transtime">
+    <h2>Showing Change History (v6)</h2>
+
+    <p>To keep versions, as required by <a href="#uc-transtime"
+    class="sectionRef"></a>, we simply copy the old data into a new
+    named graph and record some metadata about it.</p>
+
+    <p>In this example, we handle this by defining the following vocabulary:</p>
+
+    <div class="exvoc">
+
+      @@@ tdb   can we define each property separately with any sense, or just the block, together?
+
+    </div>
+      
+    <p>If Marvin changes, rather absurdly, changes his email address
+    every day, to include the date, we might have a dataset like
+    this:</p>
+
+    <pre class="example">@prefix transt: &lt;http://example.org/ns/transaction-time>.
[email protected] hq: &lt;http://example.org/ns/phonebook>.
[email protected] v:  &lt;http://www.w3.org/2006/vcard/ns#>.
[email protected] : &lt;>.
+
+:g32201 {  
+   #... various data, then:
+   [] a v:VCard
+      v:fn "Marvin Mover" ;
+      v:email "[email protected]". 
+   #... more data from other people
+}
+[] a transt:Snapshot;
+   transt:source &lt;http://div14.example.org/phonefeed>;
+   transt:result :g32201;
+   transt:starts "2012-01-01T00:00:00"^^xs:dateTime;
+   transt:ends "2012-01-02T00:00:00"^^xs:dateTime.
+
+:g32202 {  
+   #... various data, then:
+   [] a v:VCard
+      v:fn "Marvin Mover" ;
+      v:email "[email protected]". 
+   #... more data from other people
+}
+[] a transt:Snapshot;
+   transt:source &lt;http://div14.example.org/phonefeed>;
+   transt:result :g32202;
+   transt:starts "2012-01-02T00:00:00"^^xs:dateTime;
+   transt:ends "2012-01-03T00:00:00"^^xs:dateTime.
+
+# the current data
+&lt;http://div14.example.org/phonefeed> {
+   #... various data, then:
+   [] a v:VCard
+      v:fn "Marvin Mover" ;
+      v:email "[email protected]". 
+   #... more data from other people
+}
+
+</pre>
+
+<p>@@@ or should we put the data directly into a genid graph, so that
+metadata about it is less likely to change or be wrong...?  On the other hand, there's ALSO some nice potential for metadata about the feed space.</p>
+
+  </section>
+
+
+
+  <section id="example-validtime">
+    <h2>Showing Past and Future States (v7)</h2>
+
+
+    <p>The challenge expressed in <a href="#uc-validtime"
+    class="sectionRef"></a> is to segregate some of the triples,
+    marking them as being in-effect only at certain times.  The study
+    of how to do this is part of the field of temporal databases.</p>
+
+    <p>In this example, we handle this by defining the following vocabulary:</p>
+
+    <div class="exvoc">
+      
+      <p>This "valid-time" vocabulary allows a data publisher to
+      express a time range during which the triples in some space are
+      considered valid.  This acts like a time-dependent version of
+      owl:import, where the import is only made during the given time
+      range.</p>
+
+      <dl>
+	<dt><span class="schema">(rdf:space Sp)</span> vt:starts <span class="schema">(xs:dateTime T1)</span></dt>
+	<dd>Claims that all the triples in Sp are valid starting at T1, ending at some unspecified period of time.</dd>
+	<dt><span class="schema">(rdf:space Sp)</span> vt:end <span class="schema">(xs:dateTime T2)</span></dt>
+	<dd>Claims that all the triples in Sp are valid until just before T2, starting at some unspecified time.</dd>
+      </dl>
+
+      <p>In general, these two predicates need to be used together,
+      providing both vt:starts and vt:ends values for a space.  In
+      this case, { ?sp vt:starts ?t1; vt:ends ?t2 } claims that all
+      the triples in ?sp are in effect for all points in time t such
+      that t1 &lt;= t &lt; t2.  A consumer who only knows one of the
+      two times is unable to make use of data; there are no
+      default values.</p>
+
+      <p>These predicates say nothing about the validity (or "truth") of
+      the triples in Sp outside of the valid-time range.  Each of the
+      triples might or might not hold outside of the range &mdash;
+      these vt triples simply make no claim about them.</p>
+
+    </div>
+
+    <p>Given this definition, it is almost trivial for Division 5 to share their "before" and "after phonebooks:</p>
+
+    <pre class="example">@prefix vt: &lt;http://example.org/ns/valid-time>.
[email protected] hq: &lt;http://example.org/ns/phonebook>.
[email protected] : &lt;>.
+
+:pre-move {  
+    # all the pre-move data  
+    ...
+}
+:post-move {
+    # all the post-move data  
+    ...
+}
+
+:pre-move  vt:starts "2010-01-01T00:00:00"^^xs:dateTime;
+           vt:ends   "2012-07-12T00:00:00"^^xs:dateTime.
+:post-move vt:starts "2012-07-12T00:00:00"^^xs:dateTime;
+           vt:ends   "2020-01-01T00:00:00"^^xs:dateTime.
+
+</pre>
+
+     <p>This design requires every client to be modified to understand
+     and use the valid-time vocabulary.  There may be designs that do
+     not require this.</p>
+
+
+  </section>
+
+
+
+
+</section>
+
+
+  <section class="appendix" id="folding">
+    <h2>Folding</h2>
+
+    <p class="note">This section is experimental.</p>
+
+    <p>This section specifies a mechanism and an RDF vocabulary for
+    conveying <a>quad</a>s/<a>dataset</a>s using ordinary RDF Graphs
+    instead of special syntaxes and/or interfaces.  The mechanism is
+    somewhat similar to reflection or reification.  The idea is to
+    express each quad using a set of triples using a specialized
+    vocabulary.</p>
+
+    <p>Folding allows quads and thus datasets to be conveyed and
+    manipulated using normal triple-based RDF machinery, including
+    RDF/XML, Turtle, and RDFa, but at the cost of some complexity,
+    storage space, and performance.  In general, in systems where
+    languages or APIs are available which directly support datasets,
+    folding is neither required nor useful.</p>
+
+    <p>As an example, the dataset 
+
+    <pre class="example">
[email protected] : &lt;http://example.org/>.
+:space { eg:subject eg:predicate eg:object }
+    </pre>
+
+    would fold to these triples:
+
+    <pre class="example">@prefix : &lt;http://example.org/>.
+:space rdf:containsTriple [   
+   a rdf:Triple;
+   rdf:subjectIRI "http://example.org/subject";
+   rdf:predicateIRI "http://example.org/predicate";
+   rdf:objectIRI "http://example.org/object";</pre>
+
+   <p>The terms in the triple are encoded (turned into literal
+   strings, in this example), to provide referential opacity.  In the
+   semantics of quads, it does not follow from (a b c d) and a=aa that
+   (aa b c d).  Without this encoding of terms as strings, that
+   conclusion would erroneously follow from the folded quad..</p>
+
+   <p>Terms in this vocabulary:</p>
+
+   <dl>
+
+     <dt>rdf:Triple</dt>
+     <dd>The class of RDF Triples, each of which is just a triple
+     (3-tuple) of a three RDF terms, called its "subject",
+     "predicate", and "object".  Triples have no identity apart from
+     their three components.</dd>
+
+     <dt>rdf:subjectIRI</dt>
+     <dd>A predicate expressing the relationship to the triple's subject term,
+     when the subject term is an IRI.  The value is the IRI (a string)
+     which is the subject-term part of the triple.</dd>
+
+     <dt>rdf:subjectNode</dt>
+     <dd>A predicate expressing the relationship to the triple's
+     subject term, when the subject term is a blank node.  The value
+     is any RDF Resource; it simply serves as a placeholder,
+     representing the blank node which serves as the subject-term part
+     of the triple.</dd>
+
+     <dt>rdf:predicateIRI</dt>
+     <dd>A predicate expressing the relationship to the triple's
+     predicate term.  The value is the IRI (a string) which serves as
+     the predicate-term part of the triples.</dd>
+
+     <dt>rdf:objectIRI</dt>
+     <dd>A predicate expressing the relationship to the triple's
+     object term, when the object term is an IRI.  The value is the
+     IRI (a string) which is the object-term part of the triple.</dd>
+
+     <dt>rdf:objectNode</dt>
+     <dd>A predicate expressing the relationship to the triple's
+     object term, when the object term is a blank node.  The value
+     is any RDF Resource; it simply serves as a placeholder,
+     representing the blank node which serves as the object-term part
+     of the triple.</dd>
+
+     <dt>rdf:objectValue</dt>
+     <dd>A predicate expressing the relationship to the triple's
+     object term, when the object term is literal.  The value is the
+     value which serves as the object-term part of the triple.</dd>
+
+     <dt>rdf:containsTriple</dt>
+     <dd>A predicate expressing the relationship between an RDF
+     <a>space</a> and a triple which it contains.</dd>
+
+   </dl>
+
+   <p>This vocabulary is used in a specific template form, always
+   matching this SPARQL graph pattern: </p>   
+
+   <pre>?sp rdf:containsTriple [ 
+   a rdf:Triple;
+   rdf:subjectIRI|rdf:subjectNode ?s;
+   rdf:predicateIRI ?p;
+   rdf:objectIRI|rdf:objectNode|rdf:objectValue ?o 
+]</pre>
+
+   <p>This one template uses SPARQL 1.1 property paths, with
+   alternation using the "|" character.  It could also be expressed as
+   six different SPARQL 1.0 (non-property-path) graph patterns.</p>
+
+   <p>The terms in this vocabulary only have fully-defined meaning
+   when they occur in the template pattern.  When they do, the set of
+   triples matching the template has the same meaning as the
+   <a>quad</a> [ ?s ?p ?o ?sp ].</p>
+
+   <p><dfn>Folding a dataset</dfn> is the act of completely
+   conveying the facts in a dataset in RDF triples, using this
+   vocabulary.  The procedure is: (1) check for occurances
+   of the fold template in the default graph -- if they occur,
+   abort, since folding is not defined for this dataset; (2) copy
+   the triples in the default graph of the input to the output; (3)
+   for each quad in the input, generate a matching instance of the
+   fold template and put the resulting five triples in the
+   output.</p>
+
+   <p><dfn>Unfolding a dataset</dfn> is the act of turning an RDF
+   graph into a dataset, using this vocabulary.  The
+   procedure is: (1) make a mutable copy of the input graph, (2) for
+   each match of the fold template, add the resulting quad to the
+   output dataset and delete the five triples which matched the
+   template, (3) copy the remaining triples to the output as the
+   default graph of the dataset.</p>
+
+   <p>The fold and unfold functions are inverses of each other.
+   That is, for all datasets D on which fold is defined, D =
+   unfold(fold(D)) and for all graphs G, G =
+   (fold(unfold(G)).</p>
+
+   <p>The functions cannot be composed with themselves (called
+   recursively), since for each of them the domain and range are
+   disjoint.  If we were to implicitely convert graphs to datasets
+   (with the graph as the default graph), then fold(fold(D)) would
+   either be an error (if D had any named graphs) or be the same as
+   fold(D).  If we were to define unfold2 as an unfold operating on
+   datasets using their default graphs, unfold2(D) = union(D,
+   unfold(default_graph(D)), then unfold2 would be idempotent:
+   unfold2(D) = unfold2(unfold2(D)).</p>
+
+</section>
+
+
+
+
+
+
+
+<section id="references">
+<p>@@@ tbd</p>
+</section>
+
+<section class="appendix informative" id="changes">
+  <h2>Changes</h2>
+  <ul>
+    <li>2012-05-15: Added section on "Untrusting Merge".</li>
+    <li>2012-05-14: Fill in the use cases, removing some of the text that was there and which can go into the example.  Redid the trig grammar, adding spaceName, changing formatting.  Added valid-time example.  Added some of transaction-time example.</li>
+    <li>2012-05-13: Fill in the example's skeleton, add a few issues/ideas on trig</li>
+    <li>2012-05-11: Rewriting and reorganizing Concepts; some more work on Usecases and Example; removed the Detailed Example since it needs to be so re-written; renamed 'reflection' to 'folding'; reworked the Semanics</li>
+    <li>2012-05-10: Wrote a short intro.  Started writing the Use Cases section for real.   Added grammar for N-Quads and Trig.  Did a first draft of the semantics.</li>
+    <li>2012-05-09: Renamed "layers" as "spaces"; some word-smithing in Concepts and the Abstract; removed "Turtle in HTML" as a dataset syntax; added some text about trig and nquads; added a note about change-over-time; added an appendix with a reflection vocabulary</li>
+    <li>2012-05-02: Removed obsolete text from the introduction, removed the section on datasets borrowed from RDF Concepts, and added many entries to Concepts (and renamed it from Terminology).</li>
+    <li>2012-05-01: Starting with a little text from RDF Concepts, a few ideas, and the text from <a href="http://www.w3.org/2011/rdf-wg/wiki/Layers">Layers</a></li>
+  </ul>
+</section>
+
+
+
+</body>
+</html>
+