Include To Do's and fix the gld-comments email address
authorBoris Villazon-Terrazas <bvillazon@fi.upm.es>
Wed, 14 Nov 2012 00:53:47 +0100
changeset 251 2f8a7280c0f4
parent 250 c27600021dff
child 252 a94533d54606
Include To Do's and fix the gld-comments email address
bp/index.html
bp/respec-config.js
--- a/bp/index.html	Sat Nov 10 17:33:41 2012 +0100
+++ b/bp/index.html	Wed Nov 14 00:53:47 2012 +0100
@@ -20,7 +20,7 @@
 </section>
 
 <section id="sotd">
-  <p>This document is work in progress.</a></p>
+  <p>This document is work in progress.</p>
 </section>
 
 <!-- Structure of Best Practices -->
@@ -69,6 +69,12 @@
 
 </section>
 
+<p class="todo"> To include: a proper introduction of what a link is the given context.
+</p>
+
+<p class="todo"> To include: a section on how to create data links (within an organization's dataset and, more importantly, to data from other sources).
+</p>
+
 
 <!-- List of Best Practices -->
 
@@ -113,20 +119,32 @@
 <h3> Linked Open Data Lifecycle </h3>
 <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p>
 
-<p class="todo"> To Review: Bernadette, Michael, Boris - Please add a brief description for your lifecycle diagrams.
+<p class="todo"> To Review: Bernadette, Michael, Boris - Please review the brief descriptions for your lifecycle diagrams.
 </p>
 
-<p>Hyland et al.</p>
+<ul>
+	<li>
+	<p>Hyland et al. propose a Linked Data creation process that consists in the following steps: (1) Identify, (2) Model, (3) Name, (4) Describe, (5) Convert, (6) Publish, and (7) Mantain.</p>
+	</li>
+</ul>
 <div id="centerImg">
 </div>
 <img src="img/GLF_Hyland.PNG"  width="550"/>
-<p>Hausenblas et al.</p>
+
+<ul>
+	<li>
+	<p>Hausenblas et al. propose Linked Data life cycles that consist in the following steps: (1) data awareness, (2) modelling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.</p>
+	</li>
+</ul>
 <img src="img/GLF_Hausenblas.PNG" width="600"/>
-<p>Villaz&oacute;n-terrazas et al.</p>
+
+<ul>
+	<li>
+	<p>Villaz&oacute;n-terrazas et al. claim that the process of publishing Government Linked Data must have a life cycle, in the same way of Software Engineering, in which every development project has a life cycle. According to our experience this process has an iterative incremental life cycle model, which is based on the continuous improvement and extension of the Government Linked Data resulted from performing several iterations.
+</p>
+	</li>
+</ul>
 <img src="img/GLF_Villazon-terrazas.PNG" width="600" />
-<p>
-The process of publishing Government Linked Data must have a life cycle, in the same way of Software Engineering, in which every development project has a life cycle. According to our experience this process has an iterative incremental life cycle model, which is based on the continuous improvement and extension of the Government Linked Data resulted from performing several iterations.
-</p>
 </section>
 
 
@@ -199,7 +217,13 @@
 <section>
 <h2>Vocabulary Selection</h2>
 
-<p class="todo">Please Review: Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM),  Daniel Vila-Suero (UPM)</p>
+<p class="todo"> To include: George suggests to include how to mint new terms and reusing available terms, and mention the "accidental subsumption".
+</p>
+
+<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
+</p>
+
+<p class="todo">Please Review: Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO),  Daniel Vila-Suero (UPM)</p>
 <p>
 Reuse standard, vetted vocabularies to encourage others to use your data. Guidance on finding standard, vetted vocabularies is described in the Vocabulary Discovery Checklist below.
 </section>
@@ -370,7 +394,7 @@
 <!-- << URI CONSTRUCTION   -->
 <section>
 <h2>URI Construction</h2>
-<p class="todo">To Review: Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM), Daniel Vila (UPM), John Erickson (RPI), Bernadette Hyland (3 Round Stones)</p>
+<p class="todo">To Review: Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila (UPM), John Erickson (RPI), Bernadette Hyland (3 Round Stones)</p>
 <p>
 Guidance in this document is minting URIs for vocabularies, concepts, and datasets.  This section specifies how to create good URIs for use in government linked data. Inputs include 
 <ul>
@@ -806,6 +830,26 @@
 This section contains advices concerning how to expose source data, data which is being maintained in pre-existing (non-linked-data) systems such as RDBs or spreadsheets.
 </p>
 
+<p>In this section the group will produce specific advice concerning how to expose legacy data, data which is being maintained in pre-existing (non-linked-data) systems. Subject: Roadmap for cities to adopt open data</p>
+
+<p>Use case</p>
+<p>Suppose a city is considering opening up its data. It has certain concerns:</p>
+<ul>
+	<ol type="1">
+		Business and legal level
+		<li>What are the privacy considerations in publishing data? On one hand, city will like to respect the privacy of citizens and businesses, and on the other, it will like the data to be valuable enough to lead to positive change.</li>
+		<li>How to pay for the cost of opening up data? Cities may or may not have legal obligations to open up data. Accordingly, they will look for guidance on how to account for the costs. Further, can they levy a license fee if they are not obligated to open data.</li>		
+		<li>Which data should be opened and when? Should it be by phases? What data should not be shared?</li>
+		<li>What policies / laws are needed from the city so that businesses can collaborate on open data, while preserving their IP?</li>
+	</ol>
+	<ol type="1">
+		Technical level
+		<li>What should be architecture to share large-scale public data? How do we ensure performance and security?</li>
+		<li>What visualization should be supported for different types of data?</li>
+		<li>Can we provide a template implementation for the reference architecture?</li>
+	</ol>
+</ul>
+
 <p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Source_Data">content</a> as well as Spyros' <a href="http://www.w3.org/2011/gld/wiki/images/0/08/LegacyData.pdf">slides</a> from the F2F2</p>
 
 </section>
--- a/bp/respec-config.js	Sat Nov 10 17:33:41 2012 +0100
+++ b/bp/respec-config.js	Wed Nov 14 00:53:47 2012 +0100
@@ -50,7 +50,7 @@
     wgURI:        "http://www.w3.org/2011/gld/",
 
     // name of the public mailing to which comments are due
-    wgPublicList: "public-gld-wg",
+    wgPublicList: "public-gld-comments",
 
     // URI of the patent status for this WG, for Rec-track documents
     // !!!! IMPORTANT !!!!