--- a/bp/index.html	Fri Feb 03 19:46:20 2012 +0100
+++ b/bp/index.html	Mon Feb 06 02:42:50 2012 +0100
@@ -218,14 +218,75 @@
 <!--    VOCABULARY SELECTION   -->
 <section>
 <h3>Vocabulary Selection - Boris</h3>
-<p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM), George Thomas (Health & Human Services, US), John Erickson (RPI), Biplav Srivastava (IBM)</p>
+<p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM),  Daniel Vila-Suero (UPM), George Thomas (Health & Human Services, US), John Erickson (RPI), Biplav Srivastava (IBM)</p>
 <p>
 The group will provide advice on how governments should select RDF vocabulary terms (URIs), including advice as to when they should mint their own. This advice will take into account issues of stability, security, and long-term maintenance commitment, as well as other factors that may arise during the group's work.
 </p>
 
 <h4>Discovery</h4>
 <p>First phase is discovery, that is, the process of finding a vocabulary that can represent entities of a domain, for example, organisations or people.</p>
+<p>Next we present the discovery checklist that provides some steps to take into account when trying to find out existing vocabularies that could best fit the needs of a Government or a specialized agency. The reason is to avoid as much as possible building from scratch a new vocabulary and to reuse as much as possible existing *good* vocabularies of the domain.</p>
+<ul>
+	<li>
+		<b>What is your domain of interest?</b> By this answer, you define and restrict the scope of your domain to quickly find out related works in LOD in your domain. 
+Example: Geography, Environment, Administrations, State Services, Statistics, etc.
+	</li>
+	<li>
+		<b>What are the keywords in your dataset?</b>By identifying the relevant keywords or categories of your dataset, it helps for the searching process using Semantic Web Search Engine.
+If you have raw data in csv, the columns of the tables can be used for the searching process.
+Example: commune, county, point, feature, address, etc.
+	</li>
+	<li>
+		<b>Are you looking for a vocabulary in one specific language?</b>Many of the vocabularies are available in english. You may be aware of having a vocabulary in your own language. Consider this issue
+as it may restrict your search. Sometimes it might be useful to translate some of the keywords to english.
+	</li>
+	<li>
+		<b>How could you find vocabularies?</b>There are some specific search tools (Falcons, Watson, Sindice, Semantic Web Search Engine, Swoogle) that collect, analyse and indexe
+ vocabularies and semantic data available online for efficient access.
+	</li>
+	<li>
+		<b>Where could you find related vocabularies in datasets catalogues?</b>Another way around is to perform search using the previously identified key terms in datasets catalogues. The latter provide some samples
+ of how the underlying data was modelled and how it was used for.
+ Some existing catalogues are: Data Hub (previously CKAN), LOV directory, Kasabi, etc.
+	</li>
+</ul>
 
+<h4>Selection</h4>
+<p>This checklist aims at giving some advices to better assess and select the best vocabulary, according to the output of the vocabularies discovered in the *Discovery* section. The final result should be one or two vocabularies that could be reused for your own purpose (mappings, extension, etc..)</p>
+<ul>
+	<li>
+		<b>Are they good use of rdfs:label and rdfs:comment?</b>The vocabulary should be self-descriptive. Each Class and Property should have a label and comments associated.
+	</li>
+	<li>
+		<b>Is the vocabulary available in more than one language?</b>Multilingualism should be supported by the vocabulary at least for different lanquage different to English. That is also very important 
+as the documentation should be clear enough with appropriate tag for the language used for the comments or the labels.
+	</li>
+	<li>
+		<b>Who is using the vocabulary?</b>It is always better to check how the vocabulary is used by others initiatives around and  its popularity. 
+	</li>
+	<li>
+		<b>How is the vocabulary maintained?</b>The vocabulary selected should have a guarantee of maintenance in a long term, or at least the editors should be aware of that issue.
+It also include here checking the permanence of the URIs, and how is the policy of vocabulary versioning.
+	</li>
+	<li>
+		<b>Who is the publisher of the vocabulary?</b>Although anyone can create a vocabulary, it is always better to check if it is one person or a group or organization which is
+responsible for publishing and maintaining the vocabulary.
+It is recommended to better trust a well-known organization than a single person.
+	</li>
+	<li>
+		<b>How permanent are the URIs?</b>It refers here to not have a 404 http error when trying to access at any *thing* of the vocabulary.
+Also it refers to the permanent access to the server hosting the vocabulary.
+	</li>
+	<li>
+		<b>What policies are applied to control the changes?</b>It refers to the mechanism put in place by the publisher to always take care of backward compatibilities of the versions, the ways those changes affected the previous versions.
+	</li>
+	<li>
+		<b>Is the documentation available?</b>A vocabulary should be well-documented for machine readable (use of labels and comments; tags to language used), and 
+also for human-readable, that is an extra documentation should be provided by the publisher to better understands 
+the classes and properties, and if possible with some valuable use cases.
+	</li>
+</ul>
+<!--
 <h5>Key terms</h5>
 <p>Identify key domain terms</p>
 
@@ -250,7 +311,7 @@
 <li>Publisher</li>
 <li>Documentation</li>
 </ul>
-
+-->
 
 <!-- Editorial notes for creators/maintainers:
 
@@ -319,7 +380,7 @@
 
 <!--    URI CONSTRUCTION   -->
 <section>
-<h3>URI Construction - Michael</h3>
+<h3>URI Construction - Boris</h3>
 <p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM), Daniel Vila (UPM), John Erickson (RPI), Martin Alvarez (CTIC)</p>
 <p>
 This section specifies how to create good URIs for use in government linked data. Inputs include <a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a>, <a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF), and <a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk). Guidance will be produced not only for minting URIs for governmental entities, such as schools or agencies, but also for vocabularies, concepts, and datasets.
@@ -342,14 +403,43 @@
 	<li>retracting published data</li>
 </ul>
 </p>
-<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Versioning">content</a>.</p>
+<p>The group will specify how to publish data which has multiple versions, including variations such as:</p>
+<ul>
+	<li>data covering different time periods</li>
+	<li>corrected data about the same time period</li>
+	<li>the same data published using different vocabularies, formats, and presentation styles</li>
+	<li>retracting published data</li>	
+</ul>
 
+<b>By John Erickson(RPI)*</b>
+<p>
+The Digital Library community has faced the problem of versions in digital repositories for more than a decade+. One useful summary of thinking in this space can be found at the Version Identification Framework (VIF) Project site. See especially:
+</p>
+<ul>
+	<li><a href="http://www2.lse.ac.uk/library/vif/Framework/Essential/index.html">Essential Versioning Information</a></li>
+	<li><a href="http://www2.lse.ac.uk/library/vif/Framework/Object/index.html">Embedding Versioning Information in an Object</a></li>
+	<li><a href="http://www2.lse.ac.uk/library/vif/Framework/SoftwareDevelopment/index.html">Recommendations for Repository Developers</a></li>
+</ul>
+
+<p>The Resourcing IDentifier Interoperability for Repositories (RIDIR) project (2007-2008) considered in depth the relationship between identifiers and finding versions of objects. See RIDIR Final Report. In their words, RIDIR set out to investigate how the appropriate use of identifiers for digital objects might aid interoperability between repositories and to build a self-contained software demonstrator that would illustrate the findings. A number of related projects are listed at JISC's RIDIR information page.</p>
+
+<p>In addition, at TWC we have adopted an ad hoc approach to denoting versions of published linked data:</p>
+<ul>
+	<li>
+	The URI for the "abstract" dataset has no version information, e.g. http://logd.tw.rpi.edu/source/data-gov/dataset/1017
+	</li>
+	<li>The URI for a particular version appends this, e.g. http://logd.tw.rpi.edu/source/data-gov/dataset/1017/version/1st-anniversary</li>
+	<li>The version indicator (e.g. "1st-anniversary") is arbitrary; a date code may be used. We sometimes use NON-ISO 8601 (e.g. "12-Jan-2012" to make it clear this is (in our case) not necessarily machine produced.</li>
+</ul>
+
+<!-- <p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Versioning">content</a>.</p>
+-->
 </section>
 
 
 <!--    STABILITY   -->
 <section>
-<h3>Stability - Michael</h3>
+<h3>Stability - Boris</h3>
 <p class='responsible'>Anne Washington (GMU), Ron Reck</p>
 <p>
 This section specifies how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.

--- a/bp/respec-config.js	Fri Feb 03 19:46:20 2012 +0100
+++ b/bp/respec-config.js	Mon Feb 06 02:42:50 2012 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2012-01-26",
+    publishDate:          "2012-02-06",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/