--- a/bp/index.html Fri Jun 07 10:42:11 2013 +0200
+++ b/bp/index.html Fri Jun 07 11:23:31 2013 +0200
@@ -404,7 +404,7 @@
<section id="multilingual" class="informative">
<h2>Multilingual Vocabularies</h2>
<p>
-This section provides some considerations when we are dealing with multilingualism in vocabularies.</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:
</p>
<ul>
@@ -580,7 +580,7 @@
<section>
<h3>Internationalized Resource Identifiers</h3>
-<p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, Chinese, etc.)</i></p>
+<p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, French, Chinese, etc.)</i></p>
<p>The URI syntax defined in [[!RFC3986]]</a> STD 66 (Uniform Resource Identifier (URI): Generic Syntax) restricts URIs to a small number of characters: basically, just upper and lower case letters of the English alphabet, European numerals and a small number of symbols. There is now a growing need to enable use of characters from any language in URIs.
</p>
@@ -599,11 +599,11 @@
</p>
<ul>
- <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as .cn, .jp, .kr, etc., and global top level domains such as .info, .org and .museum.
+ <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as <code>.cn, .jp, .kr </code>, etc., and global top level domains such as <code>.info, .org </code> and <code> .museum. </code>
</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 of Semantic Web Applications" by Auer et al.
+ <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>
@@ -619,7 +619,7 @@
It is best practice to explicitly attach a license statement to each data set. Governments typically define ownership of works produced by government employees or contractors in legislation. It is beyond the charter of this working group to describe and recommend appropriate licenses for Open Government content published as Linked Data, however there are useful Web sites that offer detailed guidance and licenses. One valuable resource is the <a href="http://creativecommons.org/">Creative Commons</a> website. Creative Commons develops, supports, and stewards legal and technical infrastructure for digital content publishing.
</p>
-<p>
+<p class="note">
As an informative note, the UK and many former Commonwealth countries maintain the concept of the Crown Copyright. It is important to know who owns your data and to say so. The US Government designates information produced by civil servants as a U.S. Government Work, whereas contractors may produce works under a variety of licenses and copyright assignments. U.S. Government Works are not subject to copyright restrictions in the United States. It is critical for US government officials to know their rights and responsibilities under the Federal Acquisition Regulations (especially FAR Subpart 27.4, the Contract Clauses in 52.227-14, -17 and -20 and any agency-specific FAR Supplements) and copyright assignments if data is produced by a government contractor. It is recommended that governmental authorities publishing Linked Data review the relevant guidance for data published on the Web.
</p>
</section>
@@ -632,15 +632,15 @@
<p>Within government agencies, hosting linked data may require submission and review of a security plan to the authority's security team. While security plan specifics will vary widely based on a range of factors like hosting environment and software configuration, the process for developing and getting a security plan approved can be streamlined if the following guidelines and best practices are considered:</p>
-<p>Notify your security official of your intent to publish open government data.</p>
-<ul>
+<p class="highlight"><b>1- Notify your security official of your intent to publish open government data.</b></p>
+<ul class="note">
<li>Provide an overview of the Linked Data project</li>
<li>Describe how you plan to host the data (e.g., cloud, agency data center), and provide implementation timelines</li>
<li>Consider including your hosting service/software vendor in discussion(s)</li>
</ul>
-<p>Solicit assistance from the security official:</p>
-<ul>
+<p class="highlight"><b>2- Solicit assistance from the security official</b></p>
+<ul class="note">
<li>Identify guidance that should be used (e.g. for US Federal Agencies this typically would entail compliance with security control recommendations from NIST Special Publication 800-53)</li>
<li>Request clarification on regarding specific content/areas that the plan should address</li>
<li>Request a system security plan template to ensure the plan is organized to facilitate the review process (if a vendor is contributing information on controls related to their service/software, the vendor needs to adhere to the template in their response)</li>
@@ -685,7 +685,7 @@
<h2>Procurement</h2>
<p>
-This procurement checklist and <a href='http://www.w3.org/TR/lg-glossary'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
+This procurement checklist and <a href='http://www.w3.org/TR/ld-glossary/'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
</p>
<h3>Overview</h3>
@@ -731,8 +731,7 @@
<!-- <p class='todo'>John Erickson (RPI)</p> -->
<p>
-Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The <a href="http://www.w3.org/TR/prov-overview/
-" target="_blank">PROV Family of Documents</a> defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
+Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The PROV Family of Documents [[!PROV-O]] defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
</p>
<!-- todo: Talk to John Erickson to develop this more for possible inclusion
@@ -794,7 +793,7 @@
<h3>Stability Properties</h3>
-<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/gld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
+<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
<ul>
<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given data set.</li>
--- a/bp/respec-ref.js Fri Jun 07 10:42:11 2013 +0200
+++ b/bp/respec-ref.js Fri Jun 07 11:23:31 2013 +0200
@@ -24,6 +24,9 @@
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>";
+ berjon.biblio["I18n-WEB"] = "<cite>I18n of Semantic Web Applications</cite>, S. Auer, M. Weidl, J. Lehmann, Amrapali J. Zaveri, Key-Sun Choi, In Lecture Notes in Computer Science Volume 6497, 2010, pp 1-16 ";
+ berjon.biblio["ISA-URI"] = "<cite><a href=\"https://joinup.ec.europa.eu/sites/default/files/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf/\"> Study on persistent URIs</a></cite>, P. Archer, S. Goedertier, N. Loutas, 17 Dicember 2012. URL: <a href=\"https://joinup.ec.europa.eu/sites/default/files/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf\">D7.1.3 - Study on persistent URIs, with identification of best practices and recommendations on the topic for the MSs and the EC/a>";
+
// process the document before anything else is done
var refs = document.querySelectorAll('adef') ;