again references bp doc
Wed, 20 Nov 2013 21:21:52 +0100
changeset 664 7a3b2e58c751
parent 663 6b78140872b1
child 665 179bda7b6d29
again references bp doc
--- a/bp/index.html	Wed Nov 20 20:09:15 2013 +0100
+++ b/bp/index.html	Wed Nov 20 21:21:52 2013 +0100
@@ -250,7 +250,7 @@
 <!-- Diagrams -->
+<section id="NOMINATE">
 <h2> Linked Open Data Lifecycle </h2>
 <!-- <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="">ISSUE-15</a></p> -->
@@ -291,7 +291,7 @@
 <h2>Vocabulary Selection</h2>
@@ -314,7 +314,7 @@
 <!--<p class="todo"> To include: Phil suggests to include <a href="" target="_blank">Conformance for Vocabularies</a>.
 </p> -->
 <!-- section conformance -->
+<section id="conformance">
 <h2>Conformance for Vocabularies</h2>
 A data interchange, however that interchange occurs, is <b>conformant</b> with a vocabulary if:
@@ -343,7 +343,7 @@
 <!-- Discovery Checklist -->
+<section id="LINK">
 <h2>Vocabulary Discovery Checklist</h2>
 <p>The following checklist is a guide to helping developers determine whether an existing vocabulary would be a reasonable candidate for use by a government authority.
@@ -387,7 +387,7 @@
+<section id="skos">
 <h2>Using SKOS to Create a Controlled Vocabulary</h2>
 <div class="note">
@@ -441,7 +441,7 @@
 <!-- << Vocabulary Selection Criteria checklist -->
+<section id="vocab-checklist">
 <h2>Vocabulary Selection Criteria</h2>
 <p class="note"> This checklist aims to help in vocabulary selection, in summary: (1)-
@@ -497,7 +497,7 @@
 <!-- << Vocabulary management/creation -->
-<section id="vocab-creation">
+<section id="MODEL">
 <h2>Vocabulary Creation</h2>
 <!-- Editorial notes for creators/maintainers:
@@ -590,7 +590,7 @@
 <p class="todo">Add references to Felix Sasaka's work on multilingual Web and new W3C WG</p> -->
-<section id="multilingual" class="informative">
+<section id="multilingual">
 <h2>Multilingual Vocabularies</h2>
 <p class="highlight"><b>While designing a vocabulary, provide labels and descriptions if possible, in several languages, to make your vocabulary usable in multiple linguistic scopes.</b> </p>	
@@ -627,7 +627,7 @@
 <!-- << URI CONSTRUCTION   -->
-<section class="informative">
+<section id="HTTPURIS">
 <h2>URI Construction</h2>
 <!--<p class="issue"> The editors will rephrase better this content and may extend it </p> -->
 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: 
@@ -680,15 +680,15 @@
 <p class="note"><b>TAG advices on http issues</b><br>
 The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
-<pre class="example">
+<div class="example">
+<pre >
 <li> If an "http" resource responds to a GET request with a 2xx response, then the resource identified by that URI is an information resource;</li>
 <li> If an "http" resource responds to a GET request with a 303 (See Other) response, then the resource identified by that URI could be any resource;</li>
 <li> If an "http" resource responds to a GET request with a 4xx (error) response, then the nature of the resource is unknown.
 The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [[Wood2007]]).  Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
@@ -758,7 +758,7 @@
+<section id="URI-POLICY"> 
 <h3>URI Policy for Persistence</h3>
 <!-- <p class="todo">To Review: Bernadette Hyland, John Erickson</p> -->
@@ -785,7 +785,7 @@
+<section id="HUMAN"> 
 <h3>Internationalized Resource Identifiers</h3>
 <p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, French, Chinese, etc.)</i></p>
@@ -819,7 +819,7 @@
+<section id="LICENSE">
 <h2>Specifying an Appropriate License</h2>
 <!-- <p class='todo'>To Review: Bernadette Hyland</p> -->
@@ -833,7 +833,8 @@
+<section id="HOST">
 <h2>Security and Hosting</h2>
 <!-- <p class='todo'>To Review: Michael Pendleton (US EPA)</p> -->
@@ -862,7 +863,7 @@
+<section id="SOCIAL-CONTRAT">
 <h2>Publishers' "Social Contract"</h2>
 <!-- <p class='todo'>To Review: Bernadette Hyland </p> -->
@@ -889,7 +890,7 @@
 <!--    PROCUREMENT   -->
+<section id="PROCUREMENT">
@@ -938,7 +939,7 @@
 <!--    Pragmatic Provenance  -->
 <!-- Note to Editors: This section is NOT part of our charter and should be folded into other section(s). -->
+<section id="PROV">
 <!-- <p class='todo'>John Erickson (RPI)</p> -->
@@ -999,7 +1000,7 @@
+<section id="">
 <!-- << STABILITY.overview -->