--- a/bp/index.html Wed Dec 18 07:37:13 2013 -0500
+++ b/bp/index.html Wed Dec 18 13:05:37 2013 +0000
@@ -420,7 +420,7 @@
<p class="highlight"><b>A URI structure will not contain anything that could change</b><br />
It is good practice that URIs do not contain anything that could easily change or that is expected to change like session tokens or other state information. URIs should be stable and reliable in order to maximize the possibilities of reuse that Linked Data brings to users. There must be a balance between making URIs
readable and keeping them more stable by removing descriptive information that will likely
-change. For more information on this see [MDinURI] and <a href="http://www.w3.org/TR/webarch/#uri-opacity">Architecture of the World Wide Web: URI Opacity</a>.
+change. For more information on this see <a href="http://www.w3.org/TR/webarch/#uri-opacity">Architecture of the World Wide Web: URI Opacity</a>.
</p>
<p class="highlight"><b>URI Opacity</b><br />
@@ -463,7 +463,7 @@
</p>
<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 identificationschemes 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.
+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.
</p>
@@ -484,7 +484,7 @@
<!--<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/">Study on Persistent URIs</a> with identification of best practices and recommendations on the topic for the Member States and the European Commission</li>[[PARCHER]]
- <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> (PDF) </li>
+ <li> <a href="http://www.pilod.nl/wiki/Bestand:D1-2013-09-19_Towards_a_NL_URI_Strategy.pdf">Towards a <abbr title="Netherlands">NL</abbr> URI Strategy</a> </li>
</ul>
</p>
@@ -501,7 +501,7 @@
<h3>Internationalized Resource Identifiers</h3>
-<p>Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[RFC3986]]</a> are encouraged to reference <a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987">RFC 3987</a>) is a 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>Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[RFC3986]]</a> are encouraged to reference <a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a>s. Defined in (<a href="http://tools.ietf.org/html/rfc3987">RFC 3987</a>), IRI is a 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
@@ -521,7 +521,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 uniformly 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 uniform 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>
@@ -537,7 +537,7 @@
<h2>Standard Vocabularies</h2>
<p>
-Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the <a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of data</a>. The W3C has published several useful vocabularies for Linked Data. For example, the following standard vocabularies help developers to describe basic or more complex relationships for describing <a href="http://www.w3.org/TR/vocab-dcat/">data catalogs</a>, <a href="http://www.w3.org/TR/vocab-org/">organizations</a>, and <a href="http://www.w3.org/TR/vocab-data-cube/">multidimentional data</a>, such as statistics on the Web. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
+Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the <a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of data</a>. The W3C has published several useful vocabularies for Linked Data. For example, the following standard vocabularies help developers to describe basic or more complex relationships for describing <a href="http://www.w3.org/TR/vocab-dcat/">data catalogs</a>, <a href="http://www.w3.org/TR/vocab-org/">organizations</a>, and <a href="http://www.w3.org/TR/vocab-data-cube/">multidimensional data</a>, such as statistics on the Web. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
<p>