--- a/bp/index.html	Mon Nov 04 15:11:50 2013 +0000
+++ b/bp/index.html	Mon Nov 04 17:46:15 2013 +0100
@@ -127,7 +127,9 @@
 
 <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>
+	<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>
 </ul>
 <div id="centerImg">
@@ -136,14 +138,16 @@
 
 <ul>
 	<li>
-	<p>Hausenblas et al. propose Linked Data life cycles that consist in the following steps: (1) data awareness, (2) modeling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.</p>
+	<p>According to Hausenblas et al. [HAUSENBLAS] existing data management approaches assume control over schema, data and data generation, which is not the case in the Web because it is open, de-centralised environment. Based on their experience in Linked Data publishing and consumption over the past years, they have identify involved parties and fundamental phases, which provide for a multitude of so called Linked Data life cycles that consists in the following steps: (1) data awareness, (2) modeling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.
+</p>
 	</li>
 </ul>
 <img src="img/GLF_Hausenblas.PNG" width="600"/>
 
 <ul>
 	<li>
-	<p>Villaz&oacute;n-terrazas et al. propose a Linked Data life cycle that consists of the following steps: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
+	<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>
 	</li>
 </ul>
@@ -249,7 +253,48 @@
 	+ An introduction to SKOS: http://www.xml.com/pub/a/2005/06/22/skos.html
 
 </p>
+<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:
+	<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>
+		<li> Define a different namespace for each <i>skos:ConceptScheme</i> </li>
+        <li> When the mappings with the concepts are not only of the form owl:sameAs, hence it could be possible to have other semantic relationships among them, e.g.: broader, related, narrower.
+	</ul>
+</p> 
+</div>
+
+<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 ;
+    skos:notation "A101"
+    skos:prefLabel "Police"@en ;
+    skos:inScheme &lt;http://example.org/codes/typeEquipment> .
+
+    &lt;http://example.org/codes/typeEquipment/A206> 
+    rdf:type skos:Concept, ex:TypeEquipmentA ;
+    skos:notation "A206"
+    skos:prefLabel "Post office"@en ;
+    skos:inScheme &lt;http://example.org/codes/typeEquipment> .
+
+    &lt;http://example.org/codes/typeEquipment/A504> 
+    rdf:type skos:Concept, ex:TypeEquipmentA ;
+    skos:notation "A504"
+    skos:prefLabel "Restaurant"@en ;
+    skos:inScheme &lt;http://example.org/codes/typeEquipment> .
+
+    &lt;http://example.org/codes/typeEquipment> 
+    rdf:type skos:ConceptScheme ;
+    rdfs:label "Type of Equipments"@en;
+    rdfs:label "Type d'equipements"@fr .
+  </pre>
+  
+</div>
 <!-- << is your Linked Data Vocabulary 5 star?  
 
 <p class="todo"> (Editors) - Update with attribution to Bernard Vatant's 5 Star Linked Data Vocabulary scheme (proposed).