--- a/bp/index.html Wed Nov 20 19:25:29 2013 +0100
+++ b/bp/index.html Wed Nov 20 19:56:53 2013 +0100
@@ -83,7 +83,7 @@
"Richard Cyganiak"
, "Dave Reynolds"
]
- , status: "LC"
+ , status: "CR"
, publisher: "W3C"
},
@@ -111,7 +111,30 @@
authors: ["Diego Berrueta", "Jon Phipps"] ,
publisher: "W3C",
status: "WG-NOTE"
- }
+ } ,
+
+ "yakel-07": {
+ title: "Digital curation" ,
+ href: "DOI: 10.1108/10650750710831466",
+ authors: ["Elizabeth Yakel"] ,
+ publisher: "CLC Systems & Services, Vol. 23 Iss: 4, pp.335 - 340 (2007)"
+ },
+
+ "i18n-web": {
+ title:"I18n of Semantic Web Applications",
+ authors: ["S. Auer", "M. Weidl", "J. Lehmann", "Amrapali J. Zaveri", "Key-Sun Choi"] ,
+ publisher: "In Lecture Notes in Computer Science Volume 6497, 2010, pp 1-16"
+ }
+
+ "uk-govuri":{
+ title: "Designing URI sets for the UK public sector",
+ href: "https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector/" ,
+ authors: ["Cabinet Office GOV.UK"] ,
+ publisher: "Cabinet Office UK"
+ }
+
+
+ }
@@ -579,7 +602,7 @@
<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 <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 [[TIAW-LEMON]]</a>, <a href="http://lexinfo.net/" target="_blank">[[LEXINFO]]</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>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>
</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>
@@ -611,7 +634,7 @@
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 [[COOLURIS]]</li>
- <li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Designing URI</a> Sets for the UK Public Sector </li>
+ <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>
@@ -752,7 +775,7 @@
<p>
PURLs implement one form of persistent identifier for virtual resources. Other persistent identifier schemes include Digital Object Identifiers (DOIs), Life Sciences Identifiers (LSIDs) and INFO URIs. All persistent identification
-schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, <b>“the active involvement of information professionals in the management, including the preservation, of digital data for future use.”</b> [[YAKEL-07]] For a persistent identification scheme to provide a curation opportunity for a virtual resource, it must allow real-time resolution of that resource and also allow real-time administration of the identifier.
+schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, <b>“the active involvement of information professionals in the management, including the preservation, of digital data for future use.”</b> [[yakel-07]] For a persistent identification scheme to provide a curation opportunity for a virtual resource, it must allow real-time resolution of that resource and also allow real-time administration of the identifier.
</p>
<p>URI persistence is a matter of policy and commitment on the part of the URI owner. The choice of a particular URI scheme provides no guarantee that those URIs will be persistent or that they will not be persistent. HTTP [[!RFC2616]] has been designed to help manage URI persistence. For example, HTTP redirection (using the 3xx response codes) permits servers to tell an agent that further action needs to be taken by the agent in order to fulfill the request (for example, a new URI is associated with the resource).
@@ -789,7 +812,7 @@
</li>
<li><b>Domain names and phishing:</b> One of the problems associated with IDN support in browsers is that it can facilitate phishing through what are called 'homograph attacks'. Consequently, most browsers that support IDN also put in place some safeguards to protect users from such fraud.
</li>
- <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not homogenic and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in [[I18n-WEB]] .
+ <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not homogenic and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in [[i18n-web]] .
</li>
</ul>