--- a/bp/index.html Tue Nov 05 17:09:59 2013 +0000
+++ b/bp/index.html Wed Nov 06 23:24:57 2013 +0100
@@ -483,12 +483,14 @@
<li>Designing URI Sets for the UK Public Sector [[BPURI-GOVUK]]</li>
<!--<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li> -->
<li> <a href="http://philarcher.org/diary/2013/uripersistence/" target="_blank">10 rules for persistence URI</a> [[ISA-URI]] </li>
- <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> </li>
-
+ <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a>[[URI-NL]] </li>
+ <li> <a href="http://bit.ly/xJwA9g" target="_blank">Style Guidelines for Naming and Labelling Ontologies in the Multilingual Web</a> [[MULTI-LANG]]</li>
</ul>
-
+
+<!--Removed suggestion of Boris
<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to Cool URIs for the Semantic Web [[!COOL-SWURIS]] (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
-</p>
+</p> -->
+
<p>
Many general-purpose guidelines exist for the URI designer to consider, including <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</a>, which provides guidance on how to use URIs to describe things that are not Web documents; <a href="http://www.cabinetoffice.gov.uk/resource-library/designing-uri-sets-uk-public-sector" target="_blank">Designing URI Sets for the UK Public Sector</a>, a document from the UK Cabinet offices that defines the design considerations on how to URIs can be used to publish public sector reference data; and (3) <a href="http://bit.ly/xJwA9g" target="_blank">Style Guidelines for Naming and Labelling Ontologies in the Multilingual Web</a> (PDF), which proposes guidelines for designing URIs in a multilingual scenario.
@@ -503,7 +505,7 @@
</p>
<p class="highlight"><b>Provide at least one machine-readable representation of the resource identified by the URI</b><br>
-What it means: In order to enable HTTP URIs to be "dereferenced", data publishers have to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to serve representations of the resources they want to make available (e.g. a human-readable HTML representation or a machine-readable RDF/XML). A publisher may supply zero or more representations of the resource identified by that URI. However, there is a clear benefit to data users in providing at least one machine-readable representation. More information about serving different representations of a resource can be found in [[!COOL-SWURIS]]</a>.
+What it means: In order to enable HTTP URIs to be "dereferenced", data publishers have to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to serve representations of the resources they want to make available (e.g. a human-readable HTML representation or a machine-readable Turtle). A publisher may supply zero or more representations of the resource identified by that URI. However, there is a clear benefit to data users in providing at least one machine-readable representation. More information about serving different representations of a resource can be found in [[!COOL-SWURIS]]</a>.
</p>
<p class="highlight"><b>A URI structure will not contain anything that could change</b><br>
@@ -511,16 +513,17 @@
</p>
<p class="highlight"><b>URI Opacity</b><br>
-The Architecture of the World Wide Web [Jacobs], provides best practice for the treatment of URIs at the time they are resolved by a Web client:
+The Architecture of the World Wide Web [Jacobs], provides best practices for the treatment of URIs at the time they are resolved by a Web client:
<i>Agents making use of URIs SHOULD NOT attempt to infer properties of the referenced resource.</i>
URIs SHOULD be constructed in accordance with the guidance provided in this document to ensure ease of use during development and proper consideration to the guidelines given herein. However, Web clients accessing such URIs SHOULD NOT parse or otherwise read into the meaning of URIs.
</p>
+<!-->
<p class="highlight"><b>Compliance with http-range-14</b><br>
The World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) attempted to settle a long standing debate about the use of URL resolution on 15 June 2005. Specifically, they decided: <p class="todo"> Statement not finished </p>
-</p>
+</p> -->
<p class="note"><b>TAG advices on http issues</b><br>
The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
@@ -898,7 +901,7 @@
<h2>Acknowledgments</h2>
This document has been produced by the Government Linked Data Working Group, and its contents reflect extensive discussion within the Working Group as a whole.
<p>
-The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Mondeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov).
+The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Mondeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov) and Phil Archer <a href="http://www.w3.org" target="_blank">(W3C / ERCIM)</a>.
</p>
</section>
--- a/bp/respec-config.js Tue Nov 05 17:09:59 2013 +0000
+++ b/bp/respec-config.js Wed Nov 06 23:24:57 2013 +0100
@@ -33,8 +33,8 @@
// only "name" is required
editors: [
{ name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/", company: "3 Round Stones, Inc.", companyURL: "http://3roundstones.com/"},
- { name: "Boris Villazón-Terrazas", url: "http://boris.villazon.terrazas.name", company: "iSOCO, Intelligent Software Components S.A.", companyURL: "http://www.isoco.com"},
- { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin/", company: "EURECOM", companyURL: "http://www.eurecom.fr/en"}
+ { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin/", company: "EURECOM", companyURL: "http://www.eurecom.fr/en"},
+ { name: "Boris Villazón-Terrazas", url: "http://boris.villazon.terrazas.name", company: "iSOCO, Intelligent Software Components S.A.", companyURL: "http://www.isoco.com"}
],
// authors, add as many as you like.
--- a/bp/respec-ref.js Tue Nov 05 17:09:59 2013 +0000
+++ b/bp/respec-ref.js Wed Nov 06 23:24:57 2013 +0100
@@ -17,7 +17,7 @@
berjon.biblio["QB"] = "<cite><a href=\"http://www.w3.org/TR/vocab-data-cube/\">The RDF Data Cube Vocabulary </a></cite>, R. Cyganiak, D. Reynolds, 06 June 2013. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/vocab-data-cube/\">http://www.w3.org/TR/vocab-data-cube/</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["BV5STAR"] = "<cite><a href=\"http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html/\">, Is Your Linked Data vocabulary 5 Stars</a></cite>, Bernard Vatant, 05 March 2012. URL: <a href=\"http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html\">http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html</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["SKOS-REFERENCE"] = "<cite><a href=\"http://www.w3.org/TR/2009/sko-reference/\">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["VoID"] = "<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: <a href=\"http://www.w3.org/TR/void/\">http://www.w3.org/TR/void/</a>";
berjon.biblio["PROV-O"] = "<cite><a href=\"http://www.w3.org/TR/prov-o/\">PROV-O: The PROV Ontology</a></cite>, T. Lebo, S. Sahoo, and D. McGuinness, URL: http://www.w3.org/TR/2013/REC-prov-o-20130430/";
berjon.biblio["GEOW3C"] = "<cite><a href=\"http://www.w3.org/2003/01/geo/\">Basic Geo (WGS84 lat/long) Vocabulary</a></cite>, Dan Brickley, Tim Berners-Lee, URL: <a href=\"http://www.w3.org/2003/01/geo/\">http://www.w3.org/2003/01/geo/</a>";