--- a/bp/index.html Thu Jun 06 22:17:42 2013 +0200
+++ b/bp/index.html Fri Jun 07 10:41:03 2013 +0200
@@ -211,23 +211,25 @@
</p>
<p class="highlight"><b>Specify the domain</b><br/>
-<i>What it means:</i>
-Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation. </p>
+<i>What it means:</i> Identify the domain scope of the vocabulary <br/>
+<i>Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</i> </p>
<p class="highlight"><b>Identify relevant keywords in the dataset</b><br/>
- <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine.
- <!-- If you have raw data in <a href='http://www.w3.org/TR/gld-glossary/#csv'>CSV</a>, the columns of the tables can be used for the searching process.--> <br/><br/>
- Examples: commune, county, feature
+ <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. <br/><br/>
+ <!-- If you have raw data in <a href='http://www.w3.org/TR/gld-glossary/#csv'>CSV</a>, the columns of the tables can be used for the searching process.-->
+ <i>Examples: commune, county, feature. </i>
</p>
+<div class="note">
<p class="highlight"><b>Searching for a vocabulary in one specific language</b><br/>
- <i>What it means:</i>Many of the available vocabularies are in English. You may be aware of having a vocabulary in your own language.
+ <i>What it means:</i> Many of the available vocabularies are in English. You may be aware of having a vocabulary in your own language.
Consider this issue as it may restrict your search. Sometimes it might be useful to translate some of the keywords to English.
</p>
+</div>
<p class="highlight"><b>How to find vocabularies</b><br/>
<i>What it means:</i>There are some specific search tools (<a href="http://ws.nju.edu.cn/falcons/" target="_blank">Falcons</a>, <a href="http://watson.kmi.open.ac.uk/WatsonWUI/" target="_blank">Watson</a>, <a href="http://sindice.com/" target="_blank">Sindice</a>, <a href="http://swse.deri.org/" target="_blank">Semantic Web Search Engine</a>, <a href="http://swoogle.umbc.edu/" target="_blank">Swoogle</a>, <a href="http://schemapedia.com/" target="_blank">Schemapedia</a>) that collect, analyse and index vocabularies and semantic data available online for efficient access.<br/><br/>
- Examples: It is possible to perform a search on a relevant term or category present in your data.
+ <i>Examples: It is possible to perform a search on a relevant term or category present in your data.</i>
</p>
<p class="highlight"><b>Where to find existing vocabularies in datasets catalogues</b><br/>
@@ -295,9 +297,9 @@
<i>What it means:</i> Each property or term in a vocabulary should have a Label, Definition and Comment defined.
Self-describing data suggests that information about the encodings used for each representation is provided explicitly within the representation. The ability for Linked Data to describe itself, to place itself in context, contributes to the usefulness of the underlying data.<br/><br/>
For example, popular vocabulary called <code>DCMI Metadata Terms</code> has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
- <code>Label: Contributorbr/>
- Definition: An entity responsible for making contributions to the resource<br/>
- Comment: Examples of a Contributor include a person, an organization, or a service.<br/></code>
+ <code>Label: Contributor </code><br/>
+ <code>Definition: An entity responsible for making contributions to the resource </code><br/>
+ <code>Comment: Examples of a Contributor include a person, an organization, or a service.</code><br/>
</p>
<p class="highlight"><b>Vocabularies SHOULD be described in more than one language</b><br/>
@@ -309,7 +311,8 @@
</p>
<p class="highlight"><b>Vocabularies SHOULD be used by other data sets</b><br/>
- <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open Data sets that is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data. Selected vocabularies from third parties should be already in use by other data sets, as shows that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies" target="_blank">use of vocabularies</a> on the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1" target="_blank">FOAF</a> is reused by more than 55 other vocabularies.
+ <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open Data sets that is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data. Selected vocabularies from third parties should be already in use by other data sets, as shows that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. <br/><br/>
+ For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies" target="_blank">use of vocabularies</a> on the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1" target="_blank">FOAF</a> is reused by more than 55 other vocabularies.
</p>
<p class="highlight"><b>Vocabularies SHOULD be accessible for a long period</b><br/>
@@ -322,7 +325,7 @@
<p class="highlight"><b>Vocabularies SHOULD have persistent URLs</b><br/>
<i>What it means:</i> Persistent access to the server hosting the vocabulary, facilitating reusability is necessary.<br/><br/>
- Example: The <a href="http://lov.okfn.org/dataset/lov/details/vocabulary_geo.html" target="_blank">Geo W3C vocabulary</a>[[GEOW3C]] is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
+ Example: The <a href="http://lov.okfn.org/dataset/lov/details/vocabulary_geo.html" target="_blank">Geo W3C vocabulary</a> [[GEOW3C]] is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
</p>
<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br/>
@@ -425,8 +428,11 @@
The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include:
<ul>
<li>Cool URIs for the Semantic Web [[!COOL-SWURIS]]</li>
- <li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
- <li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li>
+ <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>
+
</ul>
<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.
@@ -445,7 +451,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 <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</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 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>.
</p>
<p class="highlight"><b>A URI structure will not contain anything that could change</b><br>
@@ -586,7 +592,7 @@
<a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new protocol element, that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
</p>
-<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the IETF in March 2003.
+<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the <a href="http://www.w3.org/TR/ld-glossary/#internet-engineering-task-force-ietf">IETF</a> in March 2003.
</p>
<p>Although there exist some standards focused on enabling the use of international characters in Web identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers. This section is not meant to be exhaustive and we point the interested audience to <a ref="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">An Introduction to Multilingual Web Addresses</a>, however some of the most relevant issues are following:
--- a/bp/respec-ref.js Thu Jun 06 22:17:42 2013 +0200
+++ b/bp/respec-ref.js Fri Jun 07 10:41:03 2013 +0200
@@ -16,13 +16,14 @@
berjon.biblio["ORG"] = "<cite><a href=\"http://www.w3.org/TR/vocab-org/\">An Organization ontology (ORG)</a></cite>, Dave Reynolds, 23 October 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/gld/vocab-org/\">http://www.w3.org/TR/gld/vocab-org/</a>.";
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["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["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>";
- berjon.biblio["LEXINFO"] = "<cite> Towards Linguistically Grounded Ontologies</cite>Paul Buitelaar, Philipp Cimiano, Peter Haase, Michael Sintek, URL: <a href=\"http://lexinfo.net\">http://lexinfo.net</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>";
+ berjon.biblio["LEXINFO"] = "<cite> Towards Linguistically Grounded Ontologies</cite>, Paul Buitelaar, Philipp Cimiano, Peter Haase, Michael Sintek, URL: <a href=\"http://lexinfo.net\">http://lexinfo.net</a>";
berjon.biblio["BP-PUB"] = "<cite><a href=\"http://www.w3.org/TR/swbp-vocab-pub/\"></a></cite>Diego Berrueta, Jon Phipps (eds), 28 August 2008. W3C Working Group Note URL: <a href=\"http://www.w3.org/TR/swbp-vocab-pub/\">http://www.w3.org/TR/swbp-vocab-pub/</a>";
+ berjon.biblio["BPURI-GOVUK"] = "<cite><a href=\"https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector/\">Designing URI sets for the UK public sector</a></cite>, Cabinet Office GOV.UK, 5 October 2010. URL: <a href=\"https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector\">https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector</a>";
// process the document before anything else is done
var refs = document.querySelectorAll('adef') ;