include some references
authorBoris Villazon-Terrazas <bvillazon@fi.upm.es>
Thu, 06 Jun 2013 02:08:30 +0200
changeset 547 4e713562680d
parent 546 446a456314d7
child 548 57bdafcfd7f8
include some references
bp/index.html
bp/respec-config.js
--- a/bp/index.html	Fri May 31 08:13:56 2013 +0200
+++ b/bp/index.html	Thu Jun 06 02:08:30 2013 +0200
@@ -412,12 +412,12 @@
 <h2>URI Construction</h2>
 The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include 
 <ul>
-	<li><a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a></li>
+	<li>Cool URIs for the Semantic Web [[!COOL-SWURIS]]</li>
 	<li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
 	<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li>
 </ul>
 	
-<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</a> (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
+<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to Cool URIs for the Semantic Web [[!COOL-SWURIS]] (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
 </p>
 
 <p>
@@ -428,7 +428,7 @@
 <p>The Web makes use of the URI (Uniform Resource Identifiers) as a single global identification system. The global scope of URIs promotes large-scale "network effects". Therefore, in order to benefit from the value of LD, government and governmental agencies need to identify their resources using URIs. This section provides a set of general principles aimed at helping government stakeholders to define and manage URIs for their resources.</p>
 
 <p class="highlight"><b>Use HTTP URIs</b><br>
-What it means: To benefit from and increase the value of the World Wide Web, governments and agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. As stated in [LDPrinciples], HTTP URIs enable people to "look-up" or "dereference" a URI in order to access a representation of the resource identified by that URI.
+What it means: To benefit from and increase the value of the World Wide Web, governments and agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. As stated in [[!HOWTO-LODP]], HTTP URIs enable people to "look-up" or "dereference" a URI in order to access a representation of the resource identified by that URI.
 To benefit from and increase the value of the World Wide Web, data publishers SHOULD provide URIs as identifiers for their resources.
 </p>
 
@@ -809,16 +809,14 @@
 
 
 <!--   REFERENCE: LINKED DATA COOKBOOK   -->
-<section>
-<h2>References</h2>
-
-<h3>Linked Open Data Cookbook</h3>
-<p>
+<!-- <section>
+ <h2>References</h2>
+ <h3>Linked Open Data Cookbook</h3>
+ <p>
 See <a href="http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook">Cookbook for Open Government Linked Data</a>.
 </p>
-</section>
-
-
+ </section>
+-->
 <!--    ACK   -->
 <section class="appendix">
 <h2>Acknowledgments</h2>
@@ -828,5 +826,9 @@
 
 </p>
 </section>
+
+
+
+
 </body>
 </html>
--- a/bp/respec-config.js	Fri May 31 08:13:56 2013 +0200
+++ b/bp/respec-config.js	Thu Jun 06 02:08:30 2013 +0200
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "NOTE",
-    publishDate:          "2013-04-18",
+    publishDate:          "2013-06-06",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/