--- a/bp/index.html	Wed Mar 13 01:20:11 2013 -0400
+++ b/bp/index.html	Thu Mar 14 10:02:26 2013 -0400
@@ -20,7 +20,7 @@
 
 <section id="abstract">
 <p>
-This document provides best practices for creating, publishing and announcing government content as Linked Data. Guidance on the life cycle of a Linked Data project, beginning with identification of suitable data sets, vocabulary selection, URI naming conventions through publication of data sets is included.  The goal of this document is to aid the publication of high quality Linked Open Data (LOD) from government authorities. This document collects the most relevant data management practices, promoting best practices for publishing Linked Open Data and warning against practices that are considered harmful.
+This document provides best practices for creating, publishing and announcing open government content as Linked Data. Guidance on the life cycle of a Linked Data project, beginning with identification of suitable data sets, vocabulary selection, URI naming conventions through publication of data sets is included.  The goal of this document is to aid the publication of high quality Linked Open Data (LOD) from government authorities. This document aims to compile the most relevant data management practices, promoting best practices for publishing Linked Open Data and warns against practices that are considered harmful.
 </p>
 </section>
 
@@ -33,21 +33,22 @@
 <section class="introductory">
 <h2>Purpose of the Document</h2>
 <p>
-This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data. 
-The following recommendations are offered to creators, maintainers and operators of Web sites publishing open government data.
+This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data. The following recommendations are offered to creators, maintainers and operators of Web sites publishing open government data.
 </p>
 
 <h2>Audience</h2>
 <p>
-Readers of this document are expected to be familiar with the creation of Web applications, and to have a general familiarity with the technologies involved.  The document is targeted at developers, government procurement officers, website administrators, and tool developers.
+Readers of this document are expected to be familiar with fundemental Web technologies such as HTML, URIs, and HTTP.  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 a Linked Open Data approach to publishing open government data on the Web.  
+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) 
 
 <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. Linked Data can be published by an 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.
+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 can be published by an 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>
 
 <h2>Background</h2>

--- a/glossary/index.html	Wed Mar 13 01:20:11 2013 -0400
+++ b/glossary/index.html	Thu Mar 14 10:02:26 2013 -0400
@@ -32,6 +32,11 @@
 </section>
 
 <section>
+<h4>5 Star Linked Data</h4>
+@@TODO
+</section>
+
+<section>
 <h4>ABox</h4>
 Assertion Box (ABox) is one of two types of statements in an ontology (the other being <a href="#tbox">TBox</a>). ABox statements cover instantiation and description of individuals (i.e. instances), e.g. John is a Person.
 </section>
@@ -79,7 +84,7 @@
 
 <section>
 <h4>Converter</h4>
-Converter refers to a tool or script that converts data from one form to another, e.g., spreadsheet into <a href="#rdf">Resource Description Framework (RDF)</a>. Publishing good quality, useful RDF requires expression of the relationships using Linked Data modeling subject matter expertise. Thus, modeling about the relationships implicit in the data must be performed before the data is converted from one format into RDF. 
+Converter refers to a tool or script that converts data from one form to another, e.g., spreadsheet into <a href="#rdf">Resource Description Framework (RDF)</a>. Publishing good quality, useful RDF requires expression of the relationships using Linked Data modeling subject matter expertise. Thus, modeling about the relationships implicit in the source data must be performed before the data is converted using the RDF model for Linked Data. 
 </section>
 
 <section>
@@ -244,7 +249,7 @@
 
 <section>
 <h4>Linked Data</h4>
-Linked data refers to a set of <a href="http://linkeddata.org/">best practices</a> 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. Linked Data can be published by an person or organization behind the firewall or on the public Web.  If Linked Data is published on the public Web, it is generally called <em><a href="#linked-open-data">Linked Open Data</a></em>.
+Linked data refers to a set of <a href="http://linkeddata.org/">best practices</a> 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. Linked Data and RDF are <b>not</b> the same thing.  RDF provides a common model for for Linked Data and is well suited for the representation of data on the Web.  Linked Data can be published by an person or organization behind the firewall or on the public Web.  If Linked Data is published on the public Web, it is generally called <em><a href="#linked-open-data">Linked Open Data</a></em>.
 </section>
 
 <section>
@@ -253,6 +258,17 @@
 </section>
 
 <section>
+<h4>Linked Data Principles</h4>
+Linked Data uses the Resource Description Framework (RDF) family of standards to represent and query data.  Linked Data is built on RDF but is not the same as RDF. Tim Berners-Lee, the inventor of the Web and the <a href="http://www.w3.org/DesignIssues/LinkedData.html"> Linked Data</a> project, proposed these rules. Linked Data is based on the following principles:
+<ol>
+<li>Use HTTP URIs as names for things;</li> 
+<li>Use HTTP URIs so people can look up those names;</li>
+<li>When someone looks up a URI, provide useful information, using the open Web standards, i.e., RDF, SPARQL;</li>
+<li>Include links to other URIs, so that people can discover more things.</li>
+</ol>
+</section>
+
+<section>
 <h4>Linked Open Data (LOD)</h4>
 Linked Open Data refers to Linked Data published on the public Web .  Publishing Linked Open Data [[HOWTO-LODP]] enables distributed <a href="#sparql">SPARQL</a> queries of the data sets and a "browsing" or "discovery" approach to finding information, as compared to a search strategy.
 </section>
@@ -277,18 +293,11 @@
 Machine-Readable Cataloging system is a family of formats for the representation of bibliographic information in libraries (ISO 2709, ANSI/NISO Z39.2).
 </section>
 
-<!--commented for now
-<section>
-<h4>Management, Resources and Results Structure</h4> 
-Government of Canada policy linking the management of government resources and program results to their organizational structures. It provides a representation of how a department is managed through a)  strategic outcomes; b) program activity architecture (PAA); and c)  governance structure. 
-</section>
-
 <section>
 <h4>Message</h4> 
 The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined as an <a href="http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-03.html#httpmessage" target="blank">HTTP Message</a> and transmitted via the connection.
 </section>
 
--->
 <section>
 <h4>Metadata</h4> 
 Metadata literally means data about data. It refers to the information used to administer, describe, preserve, present, use or link other information held in resources, especially knowledge resources, be they physical or virtual. 
@@ -382,7 +391,7 @@
 
 <section>
 <h4>RDF</h4>
-Resource Description Framework (RDF), is a general-purpose language for representing information in the Web.  RDF is based on the idea of identifying things using Web identifiers or HTTP URIs (Uniform Resource Identifiers), and describing resources in terms of simple properties and property values. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values [[!RDF-Primer]].
+Resource Description Framework (RDF), is a general-purpose language for representing information in the Web. RDF is not a data format, rather a model for expressing relationships between arbitrary data elements that may be represented in a variety of standard formats.  RDF is based on the idea of identifying things using Web identifiers or HTTP URIs (Uniform Resource Identifiers), and describing resources in terms of simple properties and property values. This enables RDF to represent simple statements about resources as a graph of nodes and arcs representing the resources, and their properties and values [[!RDF-Primer]].
 </section>
 
 <section>