--- a/bp/index.html	Mon Nov 04 17:46:15 2013 +0100
+++ b/bp/index.html	Mon Nov 04 17:52:34 2013 +0100
@@ -122,12 +122,12 @@
 The process of publishing  Government Linked Open Data should be comprised of tractable and manageable steps, forming a life cycle in the same way Software Engineering uses life cycles in development projects. A GLD life cycle should cover all steps from identifying appropriate datasets to actually publishing and maintaining them. In the following paragraph three different life cycle models are presented, however it is evident that they all share common (and sometimes overlapping) characteristics in their constituents. For example, they all identify the need to specify, model and publish data in acceptable LOD formats. In essence, they capture the same tasks that are needed in the process, but provide different boundaries between these tasks.
 </p>
 
-<p class="issue"> (Editors) - Please provide a brief description of lifecycle diagrams.
-</p>
+<!--<p class="issue"> (Editors) - Please provide a brief description of lifecycle diagrams.
+</p> -->
 
 <ul>
 	<li>
-	<p>Hyland et al. [BHYLAND] provide a six-step “cookbook” to model, create, publish, and announce government linked data. They highlight the role of the World Wide Web Consortium who is currently driving specifications and best practices for the publication of governmental data. Hyland et al.lifecycle consists of the following activities: (1) Identify, (2) Model, (3) Name, (4) Describe, (5) Convert, (6) Publish, and (7) Mantain.
+	<p>Hyland et al. [BHYLAND] provide a six-step “cookbook” to model, create, publish, and announce government linked data. They highlight the role of the World Wide Web Consortium who is currently driving specifications and best practices for the publication of governmental data. Hyland et al. lifecycle consists of the following activities: (1) Identify, (2) Model, (3) Name, (4) Describe, (5) Convert, (6) Publish, and (7) Mantain.
 </p>
 	
 	</li>
@@ -146,7 +146,7 @@
 
 <ul>
 	<li>
-	<p>Villaz&oacute;n-Terrazas et al. propose in \cite{} a first step to formalize their experience gained in the development of government Linked Data, into a preliminary set of methodological guidelines for generating, publishing and exploiting Linked Government Data. Their life cycle consists of the following activities: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
+	<p>Villaz&oacute;n-Terrazas et al. propose in [BVILLAZON] a first step to formalize their experience gained in the development of government Linked Data, into a preliminary set of methodological guidelines for generating, publishing and exploiting Linked Government Data. Their life cycle consists of the following activities: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
 
 </p>
 	</li>
@@ -243,21 +243,22 @@
 </p>
 </section>
 
-<!-- Discovery Checklist -->
-
-<h2>Using SKOS to Create a Controlled Vocabulary</h2>
-<p class="issue"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS.  Confirm this fits with the scope of BP document. <br/>
+<!-- Discovery Checklist 
+    <p class="issue"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS.  Confirm this fits with the scope of BP document. <br/>
   Some pointers: <br/>
 	+ SKOS datasets: http://www.w3.org/2001/sw/wiki/SKOS/Datasets <br/>
 	+ SKOS implementation records: http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/implementation.html <br/>
 	+ An introduction to SKOS: http://www.xml.com/pub/a/2005/06/22/skos.html
 
-</p>
+</p>-->
+
+<h2>Using SKOS to Create a Controlled Vocabulary</h2>
+
 <div class="note">
 	<p> [[SKOS-REFERENCE]] , which stands for Simple Knowledge Organization System, is a W3C standard, based on other Semantic Web standards (RDF and OWL), that provides a way to represent controlled vocabularies, taxonomies and thesauri. Specifically, SKOS itself is an OWL ontology and it can be written out in any RDF flavour.
 
 The W3C SKOS standard defines a portable, flexible controlled vocabulary format that is increasingly popular, with the added benefit of a good entry-level step toward the use of Semantic Web technology. </p>
-<p class="highlight"> It is a good practice to use SKOS in the following situations:
+<p > It is a good practice to use SKOS in the following situations:
 	<ul>
 		<li>There is a need to publish a list of terms or taxonomies having a special meaning for the domain</li>
 		<li> There is a clear distinction between the collections of concepts (ConceptScheme) and the different concepts. </li>
@@ -267,8 +268,9 @@
 </p> 
 </div>
 
+
+<p>Let's consider a list of equipments where the codes used are: A101=Police, A206=Post Office and A504=Restaurant. With SKOS, we could define the following fragment:</p>
 <div class="example">
-Let's consider a list of equipments where the codes used are: A101=Police, A206=Post Office and A504=Restaurant. With SKOS, we could define the following fragment:
 <pre>
 	&lt;http://example.org/codes/typeEquipment/A101> 
     rdf:type skos:Concept, ex:TypeEquipmentA ;
@@ -293,7 +295,7 @@
     rdfs:label "Type of Equipments"@en;
     rdfs:label "Type d'equipements"@fr .
   </pre>
-  
+
 </div>
 <!-- << is your Linked Data Vocabulary 5 star?