--- a/bp/index.html Thu Nov 14 02:20:59 2013 +0100
+++ b/bp/index.html Wed Nov 20 12:16:40 2013 +0100
@@ -225,12 +225,12 @@
<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.
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/>
@@ -265,15 +265,16 @@
<ul>
<li>There is a need to publish a list of terms or taxonomies having a special meaning for the domain</li>
<li> There is a clear distinction between the collections of concepts (ConceptScheme) and the different concepts. </li>
- <li> Define a different namespace for each <i>skos:ConceptScheme</i> </li>
- <li> When the mappings with the concepts are not only of the form owl:sameAs, hence it could be possible to have other semantic relationships among them, e.g.: broader, related, narrower.
+ <li> Define when possible a different namespace for each <code>skos:ConceptScheme</code> </li>
+ <li> Structure the categories using properties <code>skos:hasTopConcept</code>, <code>skos:broader</code>. </li>
+ <li> When the mappings with the concepts are not only of the form <b>owl:sameAs</b>, hence it could be possible to have other semantic relationships among them, e.g.: broader, related, narrower.
</ul>
</div>
+<p>Let's consider a list of equipments where the codes used are: A101="Police", A206="Post Office" and A504="Restaurant". With SKOS, we could define the following structure:</p>
+<div class="example">
-<p>Let's consider a list of equipments where the codes used are: A101=Police, A206=Post Office and A504=Restaurant. With SKOS, we could define the following fragment:</p>
-<div class="example">
<pre>
<http://example.org/codes/typeEquipment/A101>
rdf:type skos:Concept, ex:TypeEquipmentA ;
@@ -362,7 +363,7 @@
<!-- << Vocabulary management/creation -->
-<section>
+<section id="vocab-creation">
<h2>Vocabulary Creation</h2>
<!-- Editorial notes for creators/maintainers:
@@ -457,7 +458,7 @@
<section id="multilingual" class="informative">
<h2>Multilingual Vocabularies</h2>
-<p class="highlight"><b>While designing a vocabulary,provide labels and descriptions, if possible in several languages, to make your vocabulary usable in multiple linguistic scopes.</b> </p>
+<p class="highlight"><b>While designing a vocabulary, provide labels and descriptions if possible, in several languages, to make your vocabulary usable in multiple linguistic scopes.</b> </p>
<p>
This section provides some considerations when we are dealing with multilingualism in vocabularies. For more details on the multilingualism on the Web, see the <a href="http://www.w3.org/International/multilingualweb/lt/" target="_blank"> MultilingualWeb-LT Working Group</a> </p>
<p> We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
@@ -475,6 +476,21 @@
<!-- Multilingualism in vocabs >> -->
+<section id="howto">
+<h2>How should publishers figure out good URIs for properties with non-literal ranges?</h2>
+<p class="note"> This check-list is to help the publishers decide which URIs in different namespace to choose with non-literal ranges. It extends more specifically Section 3.</p>
+
+ <ul>
+ <li>Find out the frequence of usage of the term in Linked Open Data using tools like <a href="http://stats.lod2.eu/properties" target="_blank">lodstats</a> or <a href="http://lov.okfn.org/dataset/lov/stats/" target="_blank">lov stats</a></li>
+ <li>Always use first a property in the namespace of a "standard", or recommended vocabulary by the W3C. </li>
+ <li>Always use a property in a vocabulary more recently published, because it likely extendes or reuses a similar previous vocabulary in the same scope.</li>
+ <li> Consider with higher priority the criteria of sustainability or long term presence of the namespace.</li>
+ <li>Authoritive criteria of the underlying vocabulary has to be taken into account.</li>
+ <li>Don't be ashame, learn from others vocabularies published in the Wild .</li>
+ </ul>
+
+</section>
+
<!-- << URI CONSTRUCTION -->
<section class="informative">