--- a/bp/index.html Thu Nov 21 05:42:06 2013 +0100
+++ b/bp/index.html Thu Nov 21 09:30:10 2013 +0100
@@ -601,10 +601,13 @@
<p> We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
</p>
<ul>
- <li>As a set of <code>rdfs:label</code> in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. It is also a best practice to always include an <code>rdfs:label</code> for which the language tag in not indicated. This term corresponds to the <b>"default"</b>language of the vocabulary</li>
+ <li>As a set of <code>rdfs:label</code> in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. </li>
+ <!--remove this, suggested by Phil? It is also a best practice to always include an <code>rdfs:label</code> for which the language tag in not indicated. This term corresponds to the <b>"default"</b>language of the vocabulary</li> -->
+
<li>As <code>skos:prefLabel</code> (or <code>skosxl:Label</code>), in which the language has also been restricted.</li>
<li>As a set of monolingual ontologies (ontologies in which labels are expressed in one natural language) in the same domain mapped or aligned to each other (see the example of EuroWordNet, in which wordnets in different natural languages are mapped to each other through the so-called ILI - inter-lingual-index-, which consists of a set of concepts common to all categorizations).</li>
<li>As a set of ontology + lexicon. This represents the latest trend in the representation of linguistic (multilingual) information associated to ontologies. The idea is that the ontology is associated to an external ontology of linguistic descriptions. One of the best exponents in this case is the lemon model </a>, <a href="http://lexinfo.net/" target="_blank"></a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosintactic, etc., information. One of the main advantages of this approach is that semantics and linguistic information are kept separated. One can link several lemon models in different natural languages to the same ontology.</li>
+ <li> It could be also useful to use the <code>lexInfo</code> ontology available at <code>http://www.lexinfo.net/lmf#</code> where they provide stable resources for languages, such as <code>http://lexvo.org/id/iso639-3/eng </code> for English, or <code>http://lexvo.org/id/iso639-3/cmn</code> for Chinese Mandarin.
</ul>
<p class="note">The current trend is to follow the first approach, i.e., to use at least a <code>rdfs:label</code> and <code>rdfs:comment</code> for each term in the vocabulary.</p>
@@ -639,7 +642,7 @@
<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Designing URI</a> Sets for the UK Public Sector [[uk-govuri]]</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> </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" target="_blank">Draft URI Strategy for the NL Public Sector</a> </li>
<li> <a href="http://bit.ly/xJwA9g" target="_blank">Style Guidelines for Naming and Labelling Ontologies in the Multilingual Web</a> </li>
</ul>