Folded in Web Resource definition, updated 5 star LOD definition per list comments, fixed normative references. Ready for PubRules & publication!
--- a/glossary/index.html Mon May 20 17:47:24 2013 +0100
+++ b/glossary/index.html Tue May 21 21:55:05 2013 -0400
@@ -29,25 +29,23 @@
</section>
<section>
-<h4>5 Star Linked Data</h4>
-5 Star Linked Data refers to an incremental framework for deploying data. Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://linkeddata.org" target="_blank">Linked Data project</a>, suggested a 5 star deployment scheme for Linked Data. The 5 Star Linked Data system is cumulative. Each additional star presumes the data meets the criteria of the previous step(s).
+<h4>5 Star Linked Open Data</h4>
+5 Star Linked Data refers to an incremental framework for deploying data. Tim Berners-Lee, the inventor of the Web and initiator of the <a href="http://linkeddata.org" target="_blank">Linked Data project</a>, suggested a 5 star deployment scheme for Linked Data. The 5 Star Linked Data system is cumulative. Each additional star presumes the data meets the criteria of the previous step(s). The following 5 Star <a href="#linked-open-data">Linked Open Data</a> definition builds on that originally proposed, however adds an Open License (expression of rights).
-<p class="highlight">☆ <b>Data is available on the Web, in whatever format.</b>
-</p>
-
-<p class="highlight">☆☆ <b>Available as machine-readable structured data, (i.e., not a scanned image).</b>
+<p class="highlight">☆ <b>Publish data on the Web in any format (e.g., PDF, JPEG) accompanied by an explicit Open License (expression of rights).</b>
</p>
-<p class="highlight">☆☆☆ <b>Available in a non-proprietary format, (i.e, CSV, not Microsoft Excel).</b>
+<p class="highlight">☆☆ <b>Publish structured data on the Web in a machine-readable format (e.g., XML).</b>
</p>
-<p class="highlight">☆☆☆☆ <b>Published using open standards from the W3C (RDF and SPARQL).</b>
+<p class="highlight">☆☆☆ <b>Publish data on the Web in a documented, non-proprietary format (e.g., CSV, KML).</b>
</p>
-<p class="highlight">☆☆☆☆☆ <b>All of the above and links to other Linked Open Data.</b>
+<p class="highlight">☆☆☆☆ <b>Publish data on the Web using links (HTTP URIs) that return useful information.</b>
</p>
-<p>
-An easy to read graphic for explaining the 5 Star Linked Data model may be seen on the <a href="http://www.cafepress.com/w3c_shop" target="_blank">5 Star Linked Open Data mug</a>. One reads both green labels for <a href="#linked-open-data">Linked Open Data</a>, or neither green label for <a href="#linked-data">Linked Data</a>. The <a href="http://5stardata.info/" target="_blank">5 Open Data diagram</a> is a graphical representation of each of the 5 Star techniques as described by Tim Berners-Lee.
+
+<p class="highlight">☆☆☆☆☆ <b>All of the above and includes links to other Linked Open Data published on the Web.</b>
+</p>
</section>
<section>
@@ -257,7 +255,7 @@
<section>
<h4>International Organization for Standards (ISO)</h4>
-ISO refers to a network of the national standards institutes of over 160 countries that cooperate to define international standards. It defines many standards including, in the linked data context, formats for dates and currency. See also <a href="http://www.iso.org/iso/home.html" target="_blank">[ISO website]</a>.
+ISO refers to a network of the national standards institutes of over 160 countries that cooperate to define international standards. It defines many standards including, in the linked data context, formats for dates and currency. See also <a href="http://www.iso.org/iso/home.html" target="_blank">ISO website</a>.
</section>
<section>
@@ -272,12 +270,12 @@
<section>
<h4>JSON</h4>
-JavaScript Object Notation (JSON) is syntax for storing and exchanging text based information. JSON has proven to be a highly useful and popular object serialization and messaging format for the Web. See [[!RFC4627]] for details.
+JavaScript Object Notation (JSON) is syntax for storing and exchanging text based information. JSON has proven to be a highly useful and popular object serialization and messaging format for the Web. See also: the application/json Media Type for JavaScript Object Notation (JSON) [[!RFC4627]].
</section>
<section>
<h4>JSON-LD</h4>
-JavaScript Object Notation for Linking Data (JSON-LD) [[JSON-LD]] is a language-independent data format for representing Linked Data, based on JSON. JSON-LD is capable of serializing any RDF graph or dataset and most, but not all, JSON-LD documents can be directly transformed to RDF. <a href="http://json-ld.org/spec/FCGS/json-ld-syntax/20120626/" target="_blank"> 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 an appropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases.
+JavaScript Object Notation for Linking Data (JSON-LD) [[!JSON-LD]] is a language-independent data format for representing Linked Data, based on JSON. JSON-LD is capable of serializing any RDF graph or dataset and most, but not all, JSON-LD documents can be directly transformed to RDF. JSON-LD Syntax is easy for humans to read and write as well as, easy for machines to parse and generate. JSON-LD is an appropriate Linked Data interchange language for JavaScript environments, Web service and NoSQL databases. See also: [[!JSON-LD]] JSON-LD Syntax 1.0
</section>
<section>
@@ -297,7 +295,7 @@
<section>
<h4>Linked Data Platform</h4>
-A specification that defines a REST API to read and write Linked Data for the purposes of enterprise application integration. The Linked Data Platform describes the use of a REST API for accessing, updating, creating and deleting resources from servers. See also [[LDP-ONE]]
+A specification that defines a REST API to read and write Linked Data for the purposes of enterprise application integration. The Linked Data Platform describes the use of a REST API for accessing, updating, creating and deleting resources from servers. See also [[!LDP-ONE]]
</section>
<section>
@@ -313,8 +311,7 @@
<section>
<h4>Linked Open Data</h4>
-Linked Data published on the public Web and licensed under one of several open content licenses permitting reuse.
-Publishing Linked Open Data enables distributed <a href="#sparql">SPARQL</a> queries of the data sets and a "browsing" or "discovery" approach to finding information, as compared to a search strategy. See also: [[LD-FOR-DEVELOPERS]], [[HOWTO-LODP]]
+Linked Data published on the public Web and licensed under one of several open licenses permitting reuse. Publishing Linked Open Data enables distributed <a href="#sparql">SPARQL</a> queries of the data sets and a "browsing" or "discovery" approach to finding information, as compared to a search strategy. See also: "Linked Data: Structured Data on the Web" [[!LD-FOR-DEVELOPERS]] and "Linked Data: Evolving the Web into a Global Data Space" [[!HOWTO-LODP]]
</section>
<section>
@@ -479,7 +476,7 @@
<section>
<h4>RDF-JSON</h4>
-A name for one of the early proposals for how to serialized RDF in JSON. RDF-JSON is still widely used. Originally proposed as a <a href="http://docs.api.talis.com/platform-api/output-types/rdf-json" target="_blank">Talis Platform API Output Type</a>. See also a concrete syntax in JavaScript Object Notation (JSON) [[!RFC4627]] for RDF as defined in the RDF Concepts and Abstract Syntax [[!RDF-CONCEPTS]] W3C Recommendation and <a href="#json-ld">JSON-LD</a> which are more recent W3C documents.
+A name for one of the early proposals for serializing RDF in JavaScript Object Notation (JSON) [[!RFC4627]]. RDF-JSON is still widely used. Originally proposed as the <a href="http://docs.api.talis.com/platform-api/output-types/rdf-json" target="_blank">Talis Platform API Output Type</a>. See also a concrete syntax in JSON [[!RFC4627]] for RDF as defined in the RDF Concepts and Abstract Syntax [[!RDF-CONCEPTS]] W3C Recommendation and <a href="#json-ld">JSON-LD</a> which are more recent W3C documents.
</section>
<section>
@@ -494,7 +491,7 @@
<section>
<h4>Representational State Transfer (REST)</h4>
-An architectural style for information systems used on the Web. It explains some of the Web's key features, such as extreme scalability and robustness to change. REST is the foundation of the World Wide Web and the dominant Web service design model.
+An architectural style for information systems used on the Web. It explains some of the Web's key features, such as extreme scalability and robustness to change. REST is the foundation of the World Wide Web and the dominant Web service design model. The term "Representational State Transfer" was introduced and defined in 2000 by Roy Thomas Fielding in his doctoral dissertation. See also <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm" target="_blank">"Architectural Styles and the Design of Network-based Software Architectures" by Roy Thomas Fielding.
</section>
<section>
@@ -504,7 +501,7 @@
<section>
<h4>Resource</h4>
-In an RDF context, a resource can be anything that an RDF graph describes. A resource can be addressed by a <a href="#uniform-resource-identifier">Unified Resource Identifier (URI)</a>.
+In an RDF context, a resource can be anything that an RDF graph describes. A resource can be addressed by a <a href="#uniform-resource-identifier">Unified Resource Identifier (URI)</a>. See also Resource Description Framework (RDF) 1.1 Concepts and Abstract Syntax [[!RDF11-CONCEPTS]]
</section>
<section>
@@ -514,7 +511,7 @@
<section>
<h4>Resource Description Framework in attributes (RDFa)</h4>
-An RDF syntax encoded in HTML documents. RDFa provides a set of markup attributes to augment the visual information on the Web with machine-readable hints. It is a standard of the World Wide Web Consortium. [[!RDFa-PRIMER]]
+An RDF syntax encoded in HTML documents. RDFa provides a set of markup attributes to augment the visual information on the Web with machine-readable hints. It is a standard of the World Wide Web Consortium. See also RDFa Primer - Rich Structured Data Markup for Web Documents [[!RDFa-PRIMER]]
</section>
<section>
@@ -554,7 +551,7 @@
<section>
<h4>Semantic Web Standards</h4>
-Standards of the World Wide Web Consortium relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]], OWL [[!OWL2]] and SPARQL [[!SPARQL]].
+Standards of the World Wide Web Consortium relating to the Semantic Web, including RDF [[!RDF]], RDFa [[!RDFa-PRIMER]], SKOS [[!SKOS-REFERENCE]], OWL [[!OWL2]] and SPARQL 1.1 Overview [[!SPARQL-11]].
</section>
<section>
@@ -580,7 +577,7 @@
<section>
<h4>SPARQL</h4>
-SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also <a href="http://www.w3.org/TR/sparql11-overview/" target="_blank">http://www.w3.org/TR/sparql11-overview/</a>.
+SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also SPARQL 1.1 Overview [[!SPARQL-11]].
</section>
<section>
@@ -620,15 +617,15 @@
<section >
<h4>Turtle</h4>
-An RDF serialization format designed to be easier to read than others such as RDF/XML. The term "Turtle" was derived from Terse RDF Triple Language. Turtle allows an RDF graph to be written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle [[!TURTLE-TR]] provides levels of compatibility with the existing N-Triples format, as well as the triple pattern syntax of the SPARQL W3C Recommendation.
+An RDF serialization format designed to be easier to read than others such as RDF/XML. The term "Turtle" was derived from Terse RDF Triple Language. Turtle allows an RDF graph to be written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. Turtle provides levels of compatibility with the existing N-Triples format, as well as the triple pattern syntax of the SPARQL W3C Recommendation. See Terse RDF Triple Language [[!TURTLE-TR]].
</section >
<section >
<h4>Uniform Resource Identifier</h4>
-A global identifier standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force. A Uniform Resource Identifier (URI) may or may not be resolvable on the Web. URIs play a key role in enabling Linked Data. URIs can be used to uniquely identify virtually anything including a physical building or more abstract concepts such as colors. See also <a href="#information-resource-identifier">Information Resource Identifier</a> and <a href="#uniform-resource-locator">Uniform Resource Locator</a>. See also <a href="http://tools.ietf.org/html/rfc3986" target="_blank">http://tools.ietf.org/html/rfc3986</a> and <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">http://www.w3.org/DesignIssues/Architecture.html</a>.
+A global identifier standardized by joint action of the World Wide Web Consortium and Internet Engineering Task Force. A Uniform Resource Identifier (URI) may or may not be resolvable on the Web. URIs play a key role in enabling Linked Data. URIs can be used to uniquely identify virtually anything including a physical building or more abstract concepts such as colors. See also <a href="#information-resource-identifier">Information Resource Identifier</a> and <a href="#uniform-resource-locator">Uniform Resource Locator</a>. See also Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]] and <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">http://www.w3.org/DesignIssues/Architecture.html</a>.
</p>
<p>
-URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers. If you are interested in the history of the many names, read Tim Berners-Lee's design document <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">Web Architecture from 50,000 feet</a>. See also "Uniform Resource Identifier (URI): Generic Syntax," [[!RFC3986]]
+URIs have been known by many names: Web addresses, Universal Document Identifiers, Universal Resource Identifiers. If you are interested in the history of the many names, read Tim Berners-Lee's design document <a href="http://www.w3.org/DesignIssues/Architecture.html" target="_blank">Web Architecture from 50,000 feet</a>. See also Uniform Resource Identifier (URI): Generic Syntax [[!RFC3986]].
</p>
</section >
@@ -649,7 +646,7 @@
<section>
<h4>Validation Service</h4>
-The W3C offers an RDF validation service to check and validate RDF files. It is considered a best practice to validate RDF files prior to publishing them on the Web. See <a href="http://www.w3.org/RDF/Validator/" target="_blank">http://www.w3.org/RDF/Validator/</a>. There are other RDF parsers available, see <a href="http://www.w3.org/People/Barstow/" target="_blank">http://www.w3.org/People/Barstow/#online_parsers</a>.
+The W3C offers an RDF validation service to check and validate RDF files. It is considered a best practice to validate RDF files prior to publishing them on the Web. See <a href="http://www.w3.org/RDF/Validator/" target="_blank">http://www.w3.org/RDF/Validator/</a>. See also <a href="http://www.w3.org/People/Barstow/" target="_blank">http://www.w3.org/People/Barstow/#online_parsers</a>.
</section>
<section>
@@ -664,7 +661,7 @@
<section>
<h4>VoID</h4>
-Vocabulary of Interlinked Datasets, an <a href="#rdf-schema" target="_blank">RDF Schema</a> vocabulary for expressing metadata about RDF datasets and a standard of the World Wide Web Consortium. VoID is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. [[VOID-GUIDE]]
+Vocabulary of Interlinked Datasets, an <a href="#rdf-schema" target="_blank">RDF Schema</a> vocabulary for expressing metadata about RDF datasets and a standard of the World Wide Web Consortium. VoID is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. See also Describing Linked Datasets with the VoID Vocabulary [[!VOID-GUIDE]]
</section>
<section>
@@ -679,32 +676,37 @@
<section>
<h4>Web of Data</h4>
-A subset of the World Wide Web which contains Linked Data.
+A subset of the World Wide Web which contains machine readable data represented as <a href="#linked-data">Linked Data</a>.
</section>
<section>
<h4>Web of Documents</h4>
-The original, or traditional, World Wide Web in which published resources were nearly always documents.
+The original, or traditional, World Wide Web in which published resources were nearly always documents as opposed to machine readable data.
</section>
<section>
<h4>Web Ontology Language (OWL)</h4>
-OWL is a family of knowledge representation and vocabulary description languages for authoring ontologies, based on RDF and standardized by the W3C [[!OWL2]].
+OWL is a family of knowledge representation and vocabulary description languages for authoring ontologies, based on RDF and standardized by the W3C. See also OWL 2 Web Ontology Language Document Overview (Second Edition) [[!OWL2]].
</section >
<section>
+<h4>Web Resource</h4>
+A web page addressed by a URL. Examples include: an HTML web page, an image offered by a web server, or a dataset accessible by a URL. A Web Resource may have different representations. For example, an RDF database might be accessed at a single URL using multiple syntaxes, such as RDFa, JSON-LD, and Turtle. See also Hypertext Transfer Protocol HTTP/1.1 [[!RFC2616]].
+</section>
+
+<section>
<h4>World Wide Web Consortium (W3C)</h4>
An international community that develops and promotes protocols and guidelines for the long-term growth for the Web. W3C's standards define key parts of the World Wide Web, including <a href="http://www.w3.org/standards/webdesign/" target="_blank">Web Design</a>, <a href="http://www.w3.org/standards/webarch/" target="_blank">Web Architecture</a> and the <a href="http://www.w3.org/standards/semanticweb/" target="_blank">Semantic Web</a>. See also <a href="http://www.w3.org/Consortium/mission" target="_blank"> W3C Mission</a>.
</section >
<section>
<h4>eXtensible Hypertext Markup Language (XHTML)</h4>
-eXtensible Hypertext Markup Language (XHTML) is a family of versions of HTML based on XML and standardized by the W3C [[!XHTML1]].
+eXtensible Hypertext Markup Language (XHTML) is a family of versions of HTML based on XML and standardized by the W3C. See also XHTML 1.0 The Extensible HyperText Markup Language (Second Edition) [[!XHTML1]].
</section >
<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. See also [[!XHTML1]].
</section >
<section>
@@ -721,7 +723,7 @@
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
-<p>The editors are grateful to <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> for contributing the initial glossary terms from <a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8" target="_blank">Linking Government Data</a>, (Springer 2011). The editors wish to also thank members of the <a href="http://www.w3.org/2011/gld/" target="_blank">Government Linked Data Working Group</a> with special thanks to the reviewers and contributors: Thomas Baker, Hadley Beeman, Richard Cyganiak, Michael Hausenblas, Benedikt Kaempgen, James McKinney, Marios Meimaris, Jindrich Mynarz, Michael Pendleton and Dave Reynolds who diligently iterated the W3C Linked Data Glossary in order to create a foundation of terms upon which to discuss and better describe the Web of Data. Thank you!
+<p>The editors are grateful to <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> for contributing the initial glossary terms from <a href="http://www.springer.com/computer/database+management+%26+information+retrieval/book/978-1-4614-1766-8" target="_blank">Linking Government Data</a>, (Springer 2011). The editors wish to also thank members of the <a href="http://www.w3.org/2011/gld/" target="_blank">Government Linked Data Working Group</a> with special thanks to the reviewers and contributors: Thomas Baker, Hadley Beeman, Richard Cyganiak, Michael Hausenblas, Sandro Hawke, Benedikt Kaempgen, James McKinney, Marios Meimaris, Jindrich Mynarz and Dave Reynolds who diligently iterated the W3C Linked Data Glossary in order to create a foundation of terms upon which to discuss and better describe the Web of Data. Thank you!
</p>
</section>
</body>
--- a/glossary/respec-config.js Mon May 20 17:47:24 2013 +0100
+++ b/glossary/respec-config.js Tue May 21 21:55:05 2013 -0400
@@ -1,7 +1,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "WD",
- publishDate: "2013-05-09",
+ publishDate: "2013-05-21",
//copyrightStart: "2011",
// the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/glossary/respec-ref.js Mon May 20 17:47:24 2013 +0100
+++ b/glossary/respec-ref.js Tue May 21 21:55:05 2013 -0400
@@ -8,34 +8,55 @@
berjon.biblio["LD-FOR-DEVELOPERS"] = "<cite><a href=\"http://manning.com/dwood/\">Linked Data: Structured Data on the Web.</a> David Wood, Marsh Zaidman, Luke Ruth, with Michael Hausenblas</cite>; 2013 URL: <a href=\"http://www.manning.com/dwood\">http://www.manning.com/dwood/</a>";
berjon.biblio["LDP-ONE"] = "<cite><a href=\"http://www.w3.org/TR/2013/WD-ldp-20130307/\">Linked Data Platform 1.0.</a></cite> Steve Speicher, John Arwe. 07 March 2013. W3C Working Draft, Linked Data Platform Working Group. URL: <a href=\"http://www.w3.org/TR/ldp/\">http://www.w3.org/TR/ldp/</a>";
-
berjon.biblio["XHTML-RDFA"] = "<cite><a href=\"http://www.w3.org/TR/xhtml-rdfa/\">XHTML+RDFa</a></cite> Manu Sporny; et al. 31 March 2011. W3C Working Draft. URL: http://www.w3.org/TR/xhtml-rdfa/ ";
berjon.biblio["HTML-RDFA"] = "<cite><a href=\"http://dev.w3.org/html5/rdfa/\">HTML+RDFa</a></cite> Manu Sporny; et al. 24 May 2011. W3C Working Draft. URL: http://dev.w3.org/html5/rdfa/ ";
berjon.biblio["COOL-SWURIS"] = "<cite><a href=\"http://www.w3.org/TR/cooluris/\">Cool URIs for the Semantic Web</a></cite>, L. Sauermann and R. Cyganiak, W3C Interest Group Note 03 December 2008. URL: <a href=\"http://www.w3.org/TR/cooluris/\">http://www.w3.org/TR/cooluris/</a>";
+
berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
+
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: <a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">http://www.w3.org/Protocols/rfc2616/rfc2616.html</a>.";
+
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: <a href=\"http://tools.ietf.org/html/rfc2396\">http://tools.ietf.org/html/rfc2396</a>";
- 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["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: <a href=\"http://tools.ietf.org/html/rfc2396\">http://tools.ietf.org/html/rfc2396</a>";
+
+ berjon.biblio["TURTLE-TR"] = "<cite><a href=\"http://www.w3.org/TR/turtle/\">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/turtle/\">http://www.w3.org/TR/turtle/</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>";
- berjon.biblio["SPARQL-11"] = "<cite><a href=\"http://www.w3.org/TR/2012/PR-sparql11-overview-20121108/\">SPARQL 1.1 Overview</a></cite>,The W3C SPARQL Working Group, 8 November 2012. W3C Proposed Recommendation. URL: <a href=\"http://www.w3.org/TR/2012/PR-sparql11-overview-20121108/\">http://www.w3.org/TR/2012/PR-sparql11-overview-20121108/</a>";
+
+ berjon.biblio["SPARQL-11"] = "<cite><a href=\"http://www.w3.org/TR/sparql11-overview/\">SPARQL 1.1 Overview</a></cite>,The W3C SPARQL Working Group, 21 March 20113. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/sparql11-overview/\">http://www.w3.org/TR/sparql11-overview/</a>";
+
berjon.biblio["RDFS"] = "<cite><a href=\"http://www.w3.org/TR/rdf-schema/\">RDF Vocabulary Description Language 1.0: RDF Schema</a></cite>,ed. Dan Brickley, R.V. Guha, 10 February 2004. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf-schema/\">http://www.w3.org/TR/rdf-schema/</a>";
berjon.biblio["OWL2"] = "<cite><a href=\"http://www.w3.org/TR/owl2-overview/\">OWL 2 Web Ontology Language Document Overview</a></cite>, W3C OWL Working Group, 27 October 2009. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/owl2-overview/\">http://www.w3.org/TR/owl2-overview/</a>";
+
berjon.biblio["XHTML1"] = "<cite><a href=\"http://www.w3.org/TR/xhtml1/\">XHTML 1.0 The Extensible HyperText Markup Language (Second Edition)</a></cite>, Steven Pemberton, Daniel Auster, et al., 26 January 2000. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/xhtml1/\">http://www.w3.org/TR/xhtml1/</a>";
+
berjon.biblio["XML"] = "<cite><a href=\"http://www.w3.org/TR/REC-xml/\">Extensible Markup Language (XML) 1.0 (Fifth Edition)</a></cite>, Tim Bray, Jean Paoli, C.M. Sperberg-McQueen, Eve Maler, François Yergeau, 26 November 2008. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-xml/\">http://www.w3.org/TR/REC-xml/</a>";
+
berjon.biblio["RDFa-PRIMER"] = "<cite><a href=\"http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607/\">RDFa Primer</a></cite>, Ben Adida, Ivan Herman, Manu Sporny, 07 June 2012. W3C Note. URL: <a href=\"http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607/\">http://www.w3.org/TR/2012/NOTE-rdfa-primer-20120607/</a>";
+
berjon.biblio["N3"] = "<cite><a href=\"http://www.w3.org/TeamSubmission/n3/\">Notation3 (N3): A readable RDF syntax</a></cite>, Tim Berners-Lee, Dan Connolly, 28 March 2011. W3C Team Submission. URL: <a href=\"http://www.w3.org/TeamSubmission/n3/\">http://www.w3.org/TeamSubmission/n3/</a>";
- 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["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["RDF11-CONCEPTS"] = "<cite><a href=\"http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/\">RDF 1.1: Concepts and Abstract Syntax</a></cite>, Richard Cyganiak, David Wood, 15 January 2013. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/\">http://www.w3.org/TR/rdf11-concepts/#resources-and-statements/</a>";
+
berjon.biblio["RFC4627"] = "<cite><a http://www.ietf.org/rfc/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/rfc/rfc4627.txt\">http://www.ietf.org/rfc/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>";
+
berjon.biblio["PROV-O"] = "<cite><a href=\"http://www.w3.org/TR/prov-o/\">PROV-O: The PROV Ontology</a></cite>, Timothy Lebo, Sathya Sahoo, Deborah McGuinness (eds), 11 December 2012, W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>";
+
berjon.biblio["LD-CLOUD"] = "<cite><a href=\"http://lod-cloud.net\">Linking Open Data cloud diagram</a></cite>, Richard Cyganiak, Anja Jentzsch. URL: <a href=\"http://lod-cloud.net\">http://lod-cloud.net</a>";