--- a/glossary/index.html Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/index.html Fri Mar 08 18:02:03 2013 +0100
@@ -158,7 +158,7 @@
</section>
<section>
-<h4>Domain Name System</h4> The Internet's mechanism for mapping between a human-readable host name (e.g. www.example.com) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
+<h4>Domain Name System (DNS)</h4> The Internet's mechanism for mapping between a human-readable host name (e.g. www.example.com) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
</section>
<section>
@@ -197,12 +197,12 @@
</section>
<section>
-<h4>Hypertext Markup Language</h4>
+<h4>HyperText Markup Language (HTML)</h4>
The predominant markup language for hypertext pages on the Web. HTML defines the structure of Web pages. A family of W3C standards.
</section>
<section>
-<h4>Hypertext Transfer Protocol</h4>
+<h4>HyperText Transfer Protocol (HTTP)</h4>
The standard transmission protocol used on the World Wide Web to transfer hypertext requests and information between Web servers and Web clients (such as browsers). An IETF standard.
</section>
@@ -228,7 +228,7 @@
<section>
<h4>JSON-LD</h4>
-JSON-LD (JavaScript Object Notation for Linking Data) is an attempt to harmonize the representation of Linked Data in JSON. JSON-LD is a specification that outlines a common JSON representation format for expressing directed graphs, mixing both Linked Data and non-Linked Data in a single document. JSON-LD is a lightweight Linked Data format that provides data context. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/"> JSON-LD Syntax</a> is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is based on the JSON format and provides a way to allow JSON data interoperate at Web-scale. JSON-LD is an appropropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
+JSON-LD (JavaScript Object Notation for Linking Data)[[JSON-LD]] is an attempt to harmonize the representation of Linked Data in JSON. JSON-LD is a specification that outlines a common JSON representation format for expressing directed graphs, mixing both Linked Data and non-Linked Data in a single document. JSON-LD is a lightweight Linked Data format that provides data context. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/"> JSON-LD Syntax</a> is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is based on the JSON format and provides a way to allow JSON data interoperate at Web-scale. JSON-LD is an appropropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
</section>
<section>
@@ -271,8 +271,8 @@
A family of formats for the representation of bibliographic information in libraries (ISO 2709, ANSI/NISO Z39.2).
</section>
+<!--commented for now
<section>
-<!--
<h4>Management, Resources and Results Structure</h4>
Government of Canada policy linking the management of government resources and program results to their organizational structures. It provides a representation of how a department is managed through a) strategic outcomes; b) program activity architecture (PAA); and c) governance structure.
</section>
@@ -361,12 +361,12 @@
<section>
<h4>Raw Data</h4>
-Machine-readable files from tje wilderness released without any specific effort to make them applicable to a particular application. The advantage of "raw" data is that it can be reused in multiple applications created by multiple communities; but this requires some means of processing it.
+Machine-readable files from the wilderness released without any specific effort to make them applicable to a particular application. The advantage of "raw" data is that it can be reused in multiple applications created by multiple communities; but this requires some means of processing it.
</section>
<section>
<h4>Resource</h4>
-Anything that can be addressed by a URI.
+A resource is anything that can be addressed by a <a href="#uniform-resource-identifiers">Unified Resource Identifier (URI)</a>.
</section>
<section>
@@ -404,11 +404,13 @@
A network data object or service that can be identified by an HTTP URI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways. See details from RFC 2616bis for details on <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#uri.303" target="blank">Uniform Resource Identifiers</a>.
</section>
+<!--
<section>
<h4>Response</h4>
-After receiving and interpreting a request message, a server responds with an HTTP response message. See details from RFC 2616bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
+After receiving and interpreting a request message, a server responds with an HTTP response message. See details from [[RFC2616]] bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
</section>
+-->
<section>
<h4>REST</h4>
REST (Representational State Transfer) is a style of software architecture for distributed systems that describes six constraints: uniform interface, stateless, cacheable, client-server, layered system, and code on demand (optional). REST is the foundation of the World Wide Web and the dominant Web service design model.
@@ -436,7 +438,7 @@
<section>
<h4>Semantic Web Standards</h4>
- Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF[[!RDF]], RDFa[[!RDFa-PRIMER]], SKOS[[!SKOS-REFERENCE]] and OWL[[!OWL2]].
+ Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]] and OWL [[!OWL2]].
</section>
<section>
@@ -480,7 +482,7 @@
<section>
<h4>Subject</h4>
-Who or what the RDF statement is about.
+A subject in the context of a <a href="#triple">triple</a> <?s ?p ?o> refers to who or what the RDF statement is about.
</section>
<section >
@@ -495,7 +497,7 @@
<section >
<h4>Term</h4>
- A term is an entry in a controlled vocabulary, schema, taxonomy or ontology.
+ A term is an entry in a controlled vocabulary, schema, <a href="#taxonomy">taxonomy</a> or <a href="#ontology">ontology</a>.
</section >
<section >
@@ -530,7 +532,7 @@
<section >
<h4>Uniform Resource Identifiers (URIs)</h4>
-URI’s play a key role in enabling Linked Data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture, the Web architecture term "resource" is used to refer to these things of interest, which are, in turn, identified by HTTP URIs.
+URI’s [[!RFC3986]] play a key role in enabling Linked Data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture, the Web architecture term "resource" is used to refer to these things of interest, which are, in turn, identified by HTTP URIs.
URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers, and finally the combination of Uniform Resource Indetifiers. As far as HTTP is concerned, Uniform Resource Identifiers (URI's) are simply formatted strings which identify via name, location, or any other characteristic, a resource. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," [[!RFC2396]]
</section >
@@ -548,7 +550,7 @@
<section>
<h4>Vocabulary</h4>
-A vocabulary defines the concepts and relationships (also referred to as "terms") to describe and represent a given topic. A vocabulary is used to classify the terms that are used for a particular application, characterize relationships, and define possible constraints on the use of the terms. Vocabularies can range from simple such as the widely used Dublin Core Vocabulary to the very complex with thousands of terms, such as those used in healthcare to describe symptoms, diseases and treatments. Vocabularies play a very important role in Linked Data, specifically to help with data integration. Vocabularies also help to organize knowledge and are extensively used by libraries, museums, newspapers and government agencies that manage large collections of data.
+A vocabulary defines the concepts and relationships (also referred to as <a href="#term">"terms"</a>) to describe and represent a given topic. A vocabulary is used to classify the terms that are used for a particular application, characterize relationships, and define possible constraints on the use of the terms. Vocabularies can range from simple such as the widely used Dublin Core Vocabulary to the very complex with thousands of terms, such as those used in healthcare to describe symptoms, diseases and treatments. Vocabularies play a very important role in Linked Data, specifically to help with data integration. Vocabularies also help to organize knowledge and are extensively used by libraries, museums, newspapers and government agencies that manage large collections of data.
</section>
<section>
@@ -583,16 +585,16 @@
<section>
<h4>eXtensible Markup Language (XML)</h4>
- XML[[!XML]] is a specification for creating structured textual computer documents, subset of SGML enabling such documents to be served, received and process on the Web in the same way as HTML documents . There are many thousands of XML formats, including XHTML. It is part of a family of standards from the W3C.
+ XML [[!XML]] is a specification for creating structured textual computer documents, subset of SGML enabling such documents to be served, received and process on the Web in the same way as HTML documents . There are many thousands of XML formats, including XHTML. It is part of a family of standards from the W3C.
</section >
<section>
-<!--
+
<h4>XML Schema</h4>
-Limitations on the content of an XML document that defines what structural elements are allowed.
+XML Schemas provide a means for defining the structure, content and semantics of XML documents as defined in [[!XMLS-SCHEMA0]].
</section >
--->
+
<section>
<h4>eXtensible Stylesheet Language Transformations (XSLT)</h4>
Declarative programs to transform one XML document into another XML document.
@@ -602,7 +604,7 @@
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
-<p>The editors are very thankful for the glossary terms contributed from <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> by David Wood, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>), and all the members of the Government Linked Data Working Group.
+<p>The editors are very thankful for the glossary terms contributed from <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> book by David Wood, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>), and all the members of the Government Linked Data Working Group.
</p>
</section>
--- a/glossary/index.html~ Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/index.html~ Fri Mar 08 18:02:03 2013 +0100
@@ -158,7 +158,7 @@
</section>
<section>
-<h4>Domain Name System</h4> The Internet's mechanism for mapping between a human-readable host name (e.g. www.example.com) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
+<h4>Domain Name System (DNS)</h4> The Internet's mechanism for mapping between a human-readable host name (e.g. www.example.com) and an Internet Protocol (IP) Address (e.g. 203.20.51.10).
</section>
<section>
@@ -197,12 +197,12 @@
</section>
<section>
-<h4>Hypertext Markup Language</h4>
+<h4>HyperText Markup Language (HTML)</h4>
The predominant markup language for hypertext pages on the Web. HTML defines the structure of Web pages. A family of W3C standards.
</section>
<section>
-<h4>Hypertext Transfer Protocol</h4>
+<h4>HyperText Transfer Protocol (HTTP)</h4>
The standard transmission protocol used on the World Wide Web to transfer hypertext requests and information between Web servers and Web clients (such as browsers). An IETF standard.
</section>
@@ -228,7 +228,7 @@
<section>
<h4>JSON-LD</h4>
-JSON-LD (JavaScript Object Notation for Linking Data) is an attempt to harmonize the representation of Linked Data in JSON. JSON-LD is a specification that outlines a common JSON representation format for expressing directed graphs, mixing both Linked Data and non-Linked Data in a single document. JSON-LD is a lightweight Linked Data format that provides data context. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/"> JSON-LD Syntax</a> is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is based on the JSON format and provides a way to allow JSON data interoperate at Web-scale. JSON-LD is an appropropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
+JSON-LD (JavaScript Object Notation for Linking Data)[[JSON-LD]] is an attempt to harmonize the representation of Linked Data in JSON. JSON-LD is a specification that outlines a common JSON representation format for expressing directed graphs, mixing both Linked Data and non-Linked Data in a single document. JSON-LD is a lightweight Linked Data format that provides data context. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/"> JSON-LD Syntax</a> is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is based on the JSON format and provides a way to allow JSON data interoperate at Web-scale. JSON-LD is an appropropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
</section>
<section>
@@ -271,8 +271,8 @@
A family of formats for the representation of bibliographic information in libraries (ISO 2709, ANSI/NISO Z39.2).
</section>
+<!--commented for now
<section>
-<!--
<h4>Management, Resources and Results Structure</h4>
Government of Canada policy linking the management of government resources and program results to their organizational structures. It provides a representation of how a department is managed through a) strategic outcomes; b) program activity architecture (PAA); and c) governance structure.
</section>
@@ -361,12 +361,12 @@
<section>
<h4>Raw Data</h4>
-Machine-readable files from tje wilderness released without any specific effort to make them applicable to a particular application. The advantage of "raw" data is that it can be reused in multiple applications created by multiple communities; but this requires some means of processing it.
+Machine-readable files from the wilderness released without any specific effort to make them applicable to a particular application. The advantage of "raw" data is that it can be reused in multiple applications created by multiple communities; but this requires some means of processing it.
</section>
<section>
<h4>Resource</h4>
-Anything that can be addressed by a URI.
+A resource is anything that can be addressed by a <a href="#uniform-resource-identifiers">Unified Resource Identifier (URI)</a>.
</section>
<section>
@@ -404,11 +404,13 @@
A network data object or service that can be identified by an HTTP URI. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways. See details from RFC 2616bis for details on <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#uri.303" target="blank">Uniform Resource Identifiers</a>.
</section>
+<!--
<section>
<h4>Response</h4>
-After receiving and interpreting a request message, a server responds with an HTTP response message. See details from RFC 2616bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
+After receiving and interpreting a request message, a server responds with an HTTP response message. See details from [[RFC2616]] bis for an <a ref="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#response" target="blank">HTTP Response</a> message.
</section>
+-->
<section>
<h4>REST</h4>
REST (Representational State Transfer) is a style of software architecture for distributed systems that describes six constraints: uniform interface, stateless, cacheable, client-server, layered system, and code on demand (optional). REST is the foundation of the World Wide Web and the dominant Web service design model.
@@ -436,7 +438,7 @@
<section>
<h4>Semantic Web Standards</h4>
- Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF[[!RDF]], RDFa[[!RDFa-PRIMER]], SKOS[[!SKOS-REFERENCE]] and OWL[[!OWL2]].
+ Standards of the World Wide Web Consortium (W3C) relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]] and OWL [[!OWL2]].
</section>
<section>
@@ -455,7 +457,7 @@
<section>
<h4>Simple Knowledge Organisation System</h4>
-Simple Knowledge Organisation System (SKOS) [[!SKOS]] is a vocabulary description language for RDF designed for representing traditional knowledge organization systems such as enterprise taxonomies in RDF.
+Simple Knowledge Organisation System (SKOS) [[!SKOS-REFERENCE]] is a vocabulary description language for RDF designed for representing traditional knowledge organization systems such as enterprise taxonomies in RDF.
</section>
<section>
@@ -480,7 +482,7 @@
<section>
<h4>Subject</h4>
-Who or what the RDF statement is about.
+A subject in the context of a <a href="#triple">triple</a> <?s ?p ?o> refers to who or what the RDF statement is about.
</section>
<section >
@@ -495,7 +497,7 @@
<section >
<h4>Term</h4>
- A term is an entry in a controlled vocabulary, schema, taxonomy or ontology.
+ A term is an entry in a controlled vocabulary, schema, <a href="#taxonomy">taxonomy</a> or <a href="#ontology">ontology</a>.
</section >
<section >
@@ -530,7 +532,7 @@
<section >
<h4>Uniform Resource Identifiers (URIs)</h4>
-URI’s play a key role in enabling Linked Data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture, the Web architecture term "resource" is used to refer to these things of interest, which are, in turn, identified by HTTP URIs.
+URI’s [[!RFC3986]] play a key role in enabling Linked Data. To publish data on the Web, the items in a domain of interest must first be identified. These are the things whose properties and relationships will be described in the data, and may include Web documents as well as real-world entities and abstract concepts. As Linked Data builds directly on Web architecture, the Web architecture term "resource" is used to refer to these things of interest, which are, in turn, identified by HTTP URIs.
URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers, and finally the combination of Uniform Resource Indetifiers. As far as HTTP is concerned, Uniform Resource Identifiers (URI's) are simply formatted strings which identify via name, location, or any other characteristic, a resource. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers (URI): Generic Syntax and Semantics," [[!RFC2396]]
</section >
@@ -548,7 +550,7 @@
<section>
<h4>Vocabulary</h4>
-A vocabulary defines the concepts and relationships (also referred to as "terms") to describe and represent a given topic. A vocabulary is used to classify the terms that are used for a particular application, characterize relationships, and define possible constraints on the use of the terms. Vocabularies can range from simple such as the widely used Dublin Core Vocabulary to the very complex with thousands of terms, such as those used in healthcare to describe symptoms, diseases and treatments. Vocabularies play a very important role in Linked Data, specifically to help with data integration. Vocabularies also help to organize knowledge and are extensively used by libraries, museums, newspapers and government agencies that manage large collections of data.
+A vocabulary defines the concepts and relationships (also referred to as <a href="#term">"terms"</a>) to describe and represent a given topic. A vocabulary is used to classify the terms that are used for a particular application, characterize relationships, and define possible constraints on the use of the terms. Vocabularies can range from simple such as the widely used Dublin Core Vocabulary to the very complex with thousands of terms, such as those used in healthcare to describe symptoms, diseases and treatments. Vocabularies play a very important role in Linked Data, specifically to help with data integration. Vocabularies also help to organize knowledge and are extensively used by libraries, museums, newspapers and government agencies that manage large collections of data.
</section>
<section>
@@ -583,7 +585,7 @@
<section>
<h4>eXtensible Markup Language (XML)</h4>
- XML[[!XML]] is a specification for creating structured textual computer documents, subset of SGML enabling such documents to be served, received and process on the Web in the same way as HTML documents . There are many thousands of XML formats, including XHTML. It is part of a family of standards from the W3C.
+ XML [[!XML]] is a specification for creating structured textual computer documents, subset of SGML enabling such documents to be served, received and process on the Web in the same way as HTML documents . There are many thousands of XML formats, including XHTML. It is part of a family of standards from the W3C.
</section >
<section>
@@ -602,7 +604,7 @@
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
-<p>The editors are very thankful for the glossary terms contributed from <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> by David Wood, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>), and all the members of the Government Linked Data Working Group.
+<p>The editors are very thankful for the glossary terms contributed from <a href="http://3roundstones.com/linking-government-data/">Linking Government Data</a> book by David Wood, (<a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8">Springer 2011</a>), and all the members of the Government Linked Data Working Group.
</p>
</section>
--- a/glossary/respec-config.js Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/respec-config.js Fri Mar 08 18:02:03 2013 +0100
@@ -1,7 +1,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "WD",
- publishDate: "2013-03-07",
+ specStatus: "WG-NOTE",
+ publishDate: "2013-03-14",
//copyrightStart: "2011",
// the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/glossary/respec-config.js~ Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/respec-config.js~ Fri Mar 08 18:02:03 2013 +0100
@@ -1,6 +1,6 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "WD",
+ specStatus: "WG-NOTE",
publishDate: "2013-03-07",
//copyrightStart: "2011",
@@ -31,7 +31,7 @@
// only "name" is required
editors: [
{ name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/", company: "3 Round Stones", companyURL: "http://3roundstones.com/"},
- { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin", company: "INSTITUT TELECOM, Eurecom", companyURL: "http://www.eurecom.fr"}
+ { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin", company: "Eurecom", companyURL: "http://www.eurecom.fr"}
],
// authors, add as many as you like.
--- a/glossary/respec-ref.js Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/respec-ref.js Fri Mar 08 18:02:03 2013 +0100
@@ -12,6 +12,7 @@
berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html.";
+ berjon.biblio["RFC3986"] = "<cite><a href=\"http://tools.ietf.org/html/rfc3986\">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, Berners-Lee, et al. January 2005. Internet RFC 3986. URL: <a href=\"http://tools.ietf.org/html/rfc3986\">http://tools.ietf.org/html/rfc3986</a>.";
berjon.biblio["RFC2396"] = "<cite><a href=\"http://tools.ietf.org/html/rfc2396\">Uniform Resource Identifiers (URI): Generic Syntax</a></cite>, Berners-Lee, T., Fielding, R.T., and L. Masinter, August 1998. Internet RFC 2396. URL: http://tools.ietf.org/html/rfc2396";
berjon.biblio["TURTLE-TR"] = "<cite><a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle: Terse RDF Triple Language</a></cite>,Eric Prud'hommeaux, Gavin Carothers, 19 February 2013. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>";
berjon.biblio["SPARQL"] = "<cite><a href=\"http://www.w3.org/TR/rdf-sparql-query/\">SPARQL Query Language for RDF</a></cite>,Eric Prud'hommeaux, Andy Seaborne, 15 January 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf-sparql-query/\">http://www.w3.org/TR/rdf-sparql-query/</a>";
@@ -26,8 +27,8 @@
berjon.biblio["RFC4627"] = "<cite><a href=\"http://www.ietf.org/rfc4627.txt/\">The application/json Media Type for JavaScript Object Notation (JSON)</a></cite>, D. Crockford, July 2006. Network Working Group. URL: <a href=\"http://www.ietf.org/rfc4627.txt/\">http://www.ietf.org/rfc4627.txt/</a>";
berjon.biblio["RDF"] = "<cite><a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">RDF/XML Syntax Specification (Revised)</a></cite>, Dave Beckett (eds), 10 February 2004, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">http://www.w3.org/TR/REC-rdf-syntax/</a>";
berjon.biblio["SKOS-REFERENCE"] = "<cite><a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">SKOS: Simple Knowledge Organization System Reference</a></cite>, Sean Bechhofer, Alistair Miles (eds), 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>";
-
-
+ berjon.biblio["JSON-LD"] = "<cite><a href=\"http://www.w3.org/TR/json-ld-syntax/\">JSON-LD Syntax 1.0</a></cite>, Many Sporny, Gregg Kellogg, Markus Lanthaler (eds), 12 July 2012, W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/json-ld-syntax/\">http://www.w3.org/TR/json-ld-syntax/</a>";
+ berjon.biblio["XMLS-SCHEMA0"] = "<cite><a href=\"http://www.w3.org/TR/xmlschema-0/\">XML Schema Part 0: Primer Second Edition</a></cite>, David C. Fallside, Priscilla Walmsley (eds), 28 October 2004, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/xmlschema-0/\">http://www.w3.org/TR/xmlschema-0/</a>";
// process the document before anything else is done
--- a/glossary/respec-ref.js~ Fri Mar 08 16:48:23 2013 +0100
+++ b/glossary/respec-ref.js~ Fri Mar 08 18:02:03 2013 +0100
@@ -12,6 +12,7 @@
berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html.";
+ berjon.biblio["RFC3986"] = "<cite><a href=\"http://tools.ietf.org/html/rfc3986\">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, Berners-Lee, et al. January 2005. Internet RFC 3986. URL: <a href=\"http://tools.ietf.org/html/rfc3986\">http://tools.ietf.org/html/rfc3986</a>.";
berjon.biblio["RFC2396"] = "<cite><a href=\"http://tools.ietf.org/html/rfc2396\">Uniform Resource Identifiers (URI): Generic Syntax</a></cite>, Berners-Lee, T., Fielding, R.T., and L. Masinter, August 1998. Internet RFC 2396. URL: http://tools.ietf.org/html/rfc2396";
berjon.biblio["TURTLE-TR"] = "<cite><a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle: Terse RDF Triple Language</a></cite>,Eric Prud'hommeaux, Gavin Carothers, 19 February 2013. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>";
berjon.biblio["SPARQL"] = "<cite><a href=\"http://www.w3.org/TR/rdf-sparql-query/\">SPARQL Query Language for RDF</a></cite>,Eric Prud'hommeaux, Andy Seaborne, 15 January 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf-sparql-query/\">http://www.w3.org/TR/rdf-sparql-query/</a>";
@@ -25,9 +26,8 @@
berjon.biblio["RDF-CONCEPTS"] = "<cite><a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/\">Resource Description Framework (RDF): Concepts and Abstract Syntax</a></cite>, Graham Klyne, Jeremy J. Carroll, 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/\">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/</a>";
berjon.biblio["RFC4627"] = "<cite><a href=\"http://www.ietf.org/rfc4627.txt/\">The application/json Media Type for JavaScript Object Notation (JSON)</a></cite>, D. Crockford, July 2006. Network Working Group. URL: <a href=\"http://www.ietf.org/rfc4627.txt/\">http://www.ietf.org/rfc4627.txt/</a>";
berjon.biblio["RDF"] = "<cite><a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">RDF/XML Syntax Specification (Revised)</a></cite>, Dave Beckett (eds), 10 February 2004, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">http://www.w3.org/TR/REC-rdf-syntax/</a>";
- berjon.biblio["SKOS-REFERENCE"] = "<cite><a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">RDF/XML Syntax Specification (Revised)</a></cite>, Dave Beckett (eds), 10 February 2004, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">http://www.w3.org/TR/REC-rdf-syntax/</a>";
-
-
+ berjon.biblio["SKOS-REFERENCE"] = "<cite><a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">SKOS: Simple Knowledge Organization System Reference</a></cite>, Sean Bechhofer, Alistair Miles (eds), 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>";
+ berjon.biblio["JSON-LD"] = "<cite><a href=\"http://www.w3.org/TR/json-ld-syntax/\">JSON-LD Syntax 1.0</a></cite>, Many Sporny, Gregg Kellogg, Markus Lanthaler (eds), 12 July 2012, W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/json-ld-syntax/\">http://www.w3.org/TR/json-ld-syntax/</a>";
// process the document before anything else is done