--- a/bp/index.html Fri Dec 06 09:20:25 2013 +0100
+++ b/bp/index.html Fri Dec 06 09:42:31 2013 +0100
@@ -181,15 +181,15 @@
<h2>Audience</h2>
<p>
-Readers of this document are expected to be familiar with fundamental Web technologies such as HTML, URIs, and HTTP. The document is targeted at developers, government information management staff, website administrators.
+Readers of this document are expected to be familiar with fundamental Web technologies such as <a href="http://www.w3.org/TR/ld-glossary/#hypertext-markup-language" target="blank">HTML</a>, <a href="http://www.w3.org/TR/ld-glossary/#uri" target="blank">URIs</a>, and <a href="http://www.w3.org/TR/ld-glossary/#hypertext-transfer-protocol" target="blank">HTTP</a>. The document is targeted at developers, government information management staff, website administrators.
</p>
<h2>Scope</h2>
<p>
-This document aims to facilitate the adoption of Linked Open Data Principles for publishing open government data on the Web. Linked Data utilizes the Resource Description Framework [[!RDF-CONCEPTS]].
+This document aims to facilitate the adoption of <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles" target="blank">Linked Open Data Principles</a> for publishing open government data on the Web. <a href="http://www.w3.org/TR/ld-glossary/#linked-data" target="blank">Linked Data</a> utilizes the Resource Description Framework [[!RDF-CONCEPTS]].
<p>
-Linked Data refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of the RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. RDF and Linked Data are not the same thing.
+Linked Data refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of the RDF family of syntaxes (e.g., <a href="http://www.w3.org/TR/ld-glossary/#rdf-xml" target="blank">RDF/XML</a>, <a href="http://www.w3.org/TR/ld-glossary/#n3" target="blank">N3</a>, <a href="http://www.w3.org/TR/ld-glossary/#turtle" target="blank">Turtle</a> and N-Triples) and <a href="http://www.w3.org/TR/ld-glossary/#http-uris" target="blank">HTTP URIs</a>. <a href="http://www.w3.org/TR/ld-glossary/#rdf" target="blank">RDF</a> and <a href="http://www.w3.org/TR/ld-glossary/#linked-data" target="blank">Linked Data</a> are not the same thing.
Linked Data can be published by a person or organization behind the firewall or on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data.
</p>
@@ -475,7 +475,7 @@
</p>
<p class="highlight"><b>URIs for properties with non-literal ranges</b><br/>
- <i>What it means:</i> Name all properties as verb senses, so that triples may be actually read; e.g., <i>hasProperty</i> .
+ <i>What it means:</i> Name all properties as verb senses, so that <a href="http://www.w3.org/TR/ld-glossary/#triple" target="blank">triples</a> may be actually read; e.g., <i>hasProperty</i> .
</p>
<p class="highlight"><b>Vocabularies should be self-descriptive</b><br/>
@@ -700,7 +700,7 @@
</p>
<h3>URI Design Principles</h3>
-<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>The Web makes use of the <a href="http://www.w3.org/TR/ld-glossary/#uri" target="blank">URI</a> (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 <a href="http://www.w3.org/TR/ld-glossary/#resource" target="blank">resources</a> 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>
<i>What it means:</i> 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.
@@ -987,7 +987,7 @@
<h3>Stability Properties</h3>
-<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
+<p>There are characteristics that influence the stability or longevity of useful <a href="http://www.w3.org/TR/ld-glossary/#open-government-data" target="blank">open government data</a>. Many of these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
<ul>
<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given data set.</li>