General updates to sections marked for Bern
authorbhyland
Mon, 30 Jan 2012 21:32:11 -0500
changeset 48 50e1c31a9c64
parent 47 3912db018cc5
child 49 caf0b94e68fa
General updates to sections marked for Bern
bp/index.html
--- a/bp/index.html	Sun Jan 29 20:38:34 2012 +0000
+++ b/bp/index.html	Mon Jan 30 21:32:11 2012 -0500
@@ -109,14 +109,6 @@
 While LOD is a relatively new approach to data provisioning, growth has been exponential. LOD has been adopted by other national governments including the UK, Sweden, Germany, France, Spain, New Zealand and Australia.
 </p>
 
-<p>
-While LOD is a relatively new approach to data provisioning, growth has been exponential. LOD has been adopted by other national governments including the UK, Sweden, Germany, France, Spain, New Zealand and Australia.
-</p>
-
-<p>
-Development and maintenance of linked data is supported by the Semantic Web/Semantic Technologies industry. Useful information about industry vendors/contractors, and their associated products and services, is available from the World Wide Web Consortium’s Government Linked Data (W3C/GLD) workgroup Community Directory.
-<p>
-
 <h5>LOD Production through Consumption Lifecycle</h5>
 
 <p>
@@ -391,41 +383,52 @@
 </section>
 
 <!--    Pragmatic Provenance  -->
-<!-- Note to Editors: This section is not officially part of our charter and probably needs to be folded into another section yet to be determined. -->
+<!-- Note to Editors: This section is not part of our charter and probably will be folded into another section.  Yet to be determined. -->
 
 <section>
-<h3>Pragmatic Provenance - Boris</h3>
+<h3>TBD - Pragmatic Provenance - Boris</h3>
 <p class='responsible'>John Erickson (RPI)</p>
 <p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/228_Best_Practices_Pragmatic_Provenance">content</a>. 
 </section>
 
 
 <!--    Epilogue: The Social Contract of a Linked Open Data Publisher   -->
-<!-- Note to Editors: This section is not officially part of our charter and probably needs to be folded into another section yet to be determined. -->
+<!-- Note to Editors: This section is not part of our charter and probably will be folded into another section.  Yet to be determined. -->
 
 <section>
-<h3>The Social Contract of a Linked Open Data Publisher - Bernadette</h3>
+<h3>TBD - The Social Contract - Bernadette</h3>
 <p class='responsible'>Bernadette Hyland (3 Round Stones)</p>
 <p class="todo">Integrate from Linked Data Cookbook <a href="http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook#Your_Social_Responsibility_as_a_Data_Publisher">content</a>. 
 </section>
 
 <p>
-Publishers of Linked Data implicitly enter into an implicit social contract with users of their data. A problem on the Web is that it can be difficult to determine how much your information may matter to users. Publishers should feel a responsibility to maintain their data, to keep it fresh and up to date, to ensure its accuracy to the greatest degree possible and to repair reported problems. Publishers should assign a contact person or people to respond to enquires via some common mechanisms such as electronic mail or even telephone. If reuse is a priority, then following best practices such as modeling your data as high quality Linked Data, carefully consid- ering your URI strategy and publishing VoID descriptions will form the foundation of your Open Government initiatives. Ensuring that your Linked Open Data set re- mains available where you say it will be is critical.
-</p>
-<p>
-If you move or remove data that is published to the Web, you may break third party applications or mashups without knowing. This is considered rude for obvious reasons and is the basis for the social contract. A good way to prevent causing http 404's is for your organization to implement a persistence strategy.
-</p>
-
[email protected]@ TODO: More on persistence strategy (BOH)
-<p>
-It is beyond the charter of this working group to describe and recommend appropriate licenses for Open Government content published as Linked Data. However, 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.
-</p>
-<p>
-For example, 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.
+The following is informative in relation to publishing open government data as LOD.
 </p>
 
 <p>
-Similarly, 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. Additional work around the recording of legal implications and licensing may be undertaken by the W3C Government Linked Data Working Group in coming years. It is recommended that governmental agencies publishing Linked Data review the Recommendations produced by the W3C.
+Publishers of Linked Data enter into an implicit social contract with users of their data.  Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be.  Here is a summary of best practices that relate to the implicite "social contract".  Additional informational details are included for reference.
+</p>
+
+<ul>
+<li>Publish a VoID description for each published data set;</li>
+<li>Associate metadata on the frequency of data updates;</li>
+<li>Associate a government appropriate license with all content your agency publishes if you wish to encourage re-use;</li>
+<li>Plan and implement a persistence strategy;</li>
+<li>Ensure data is accurate to the greatest degree possible;</li>
+<li>Publish an email address to report problematic data;</li>
+<li>Ensure the contact person or team responds to enquires via email or telephone, if necessary.</li> 
+</ul>
+
+<p>
+Giving due consideration your organization's URI strategy should be one of the first activities your team undertakes as they prepare a Linked Open Data strategy. Authoritative data requires the permanence and resolution of HTTP URIs.  If publishers move or remove data that was published to the Web, third party applications or mashups may break. This is considered rude for obvious reasons and is the basis for the Linked Data "social contract." A good way to prevent causing HTTP 404's is for your organization to implement a persistence strategy.
+</p>
+
+<p>
+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>
+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>
 
 @@ TODO: Expand for other countries by example, e.g., Brazil, others