--- a/bp/index.html	Wed Nov 20 18:48:42 2013 +0100
+++ b/bp/index.html	Wed Nov 20 18:50:38 2013 +0100
@@ -145,49 +145,56 @@
 <section class="summary">
 <h2>Summary of Best Practices</h2>
 
-The following best practices are discussed in this document and listed here for convenience.
-
-<p class='stmt'><a href="#IDENTIFY">IDENTIFY</a> Indentify data sets that other people may wish to re-use.
-</p>
-
-<p class='stmt'><a href="#MODEL">MODEL</a> Model the data in an application-independent, objective way in terms of representation.  Denormalize the data as necessary.
+<p class="todo"> (Editors) - Please link underlined words to relevant sections of the BP doc where discussed.
 </p>
 
-<p class='stmt'><a href="#METADATA">METADATA</a> Provide basic metadata, including MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s). 
+The following best practices are discussed in this document and listed here for convenience.
+
+<p class='stmt'><a href="#NOMINATE">NOMINATE A PILOT</a> Nominate a pilot project on Linked Open Data.
 </p>
 
-<p class='stmt'><a href="#IDENTIFY">PII</a> Do not Publish Personally Identifiable Information as Open Data on the Web
-Data on the public Web can be potentially misused. Examples of personally identifiable data include: individual names, national identification number, phone number, credit card number and driver license number. 
+<p class='stmt'><a href="#SELECT">SELECT A DATA SET</a> Select a data set that provides benefit to others for re-use.  Consider a data set that your organization collects unique information that when combined with other open data provides greater value.  For example, publishing facilities that can then be linked with geographic information including postal codes is a popular example.
 </p>
 
-<p class='stmt'><a href="#NAME">NAME</a> Use HTTP URIs as names for your objects. Give careful consideration to the URI naming strategy. Consider how the data will change over time and name as necessary.
+<p class='stmt'><a href="#PII">PERSONALLY IDENTIFIABLE DATA</a> Do not Publish Personally Identifiable Information as Linked Open Data as it can potentially be misused.  Examples of personally identifiable data include: individual names, national identification number, phone number and office extention, and drivers license number. 
+</p>
+
+<p class='stmt'><a href="#LICENSE">ASSOCIATE A LICENSE</a> Associate an appropriate open license with which to publish the data.  People will only reuse data when there is a clear, acceptable license assocated with the data.
+</p>
+
+<p class='stmt'><a href="#MODEL">MODEL</a> Model the data in an application-independent way.  This means that if the data was originally organized for a specific application, you're likely to remove irrelevant content.  In many cases, denormalizing the data may be necessary and is appropriate. 
 </p>
 
 <p class='stmt'><a href="#STANDARD-VOCABULARIES">STANDARD_VOCABULARIES</a> Describe objects with standard vocabularies whenever possible.
 </p>
 
-<p class='stmt'><a href="#VOCABULARY-USE">VOCABULARY_USE</a> Use vocabularies as loosely coupled modular components.  
-</p>
-
-<p class='stmt'><a href="#REPRESENTATION">REPRESENTATION</a> Convert the source data into a Linked Data representation, also called an RDF serialization including Turtle, Notation-3 (N3), N-Triples, XHTML with embedded RDFa, and RDF/XML.
+<p class='stmt'><a href="#METADATA">BASIC METADATA</a> Always provide basic metadata, including MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s). 
 </p>
 
 <p class='stmt'><a href="#HUMAN">HUMAN READABLE</a> Provide human readable descriptions with your Linked Data.
 </p>
 
-<p class='stmt'><a href="#MACHINE">MACHINE ACCESSIBLE</a>Provide access to the data representation via RESTful API, SPARQL endpoint(s) and RDF download.
-</p>
-
-<p class='stmt'><a href="#SPECIFY-LICENSE">SPECIFY_LICENSE</a> Specify an appropriate license.
+<p class='stmt'><a href="#HTTPURIS">HTTP URIs</a> Create HTTP URIs as names for your objects. Give careful consideration to the URI naming strategy. Consider how the data will change over time and name as necessary.
 </p>
 
-<p class='stmt'><a href="#HOST">HOST</a> Deliver open government data on authoritative domain to increase perceived trust.  
+<p class='stmt'><a href="#MACHINE">MACHINE ACCESSIBLE</a>A major benefit of Linked Data is providing access to data for machines.  Machines can use a variety of methods to read data including, but not limited to: a RESTful API, SPARQL endpoints or download.
 </p>
 
-<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE</a> Announce open government data, have a feedback mechanism and be prepared to be responsive to feedback. 
+<p class='stmt'><a href="#SERIALIZATION">SERIALIZATION</a> Convert the source data into a Linked Data representation.  This process is also called "Triplifaction" however, more accurately, it is the process serializing data into one or more RDF serializations.  RDF serializations include Turtle, Notation-3 (N3), N-Triples, XHTML with embedded RDFa, and RDF/XML.  
 </p>
 
-<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT</a> Maintenance is critical. Without a permanent identifier scheme, if you move or remove data that is published to the Web, you may break third party applications or mashups which is clearly undesireable.  URI strategy and implementation are critical.
+<p class='stmt'><a href="#LINK">LINKS ARE KEY</a> As the name suggests, Linked Open Data means the data is linked to other stuff.  Data in isolation is rarely valauble, however, interlinked data is suddenly very valuable.  There are many popular data sets, such as DBpedia that provide valuable data, including photos and geographic information. Being able to connect Linked Open Data from a government authority with DBpedia is quick way to show the value of adding content to the Linked Data Cloud.
+</p>
+
+<p class='stmt'><a href="#HOST">DOMAIN</a> Deliver Linked Open Data on authoritative domain.  Using an authoritative domain increases the perception of trusted content.  Authoritative data that is regularly updated on a government domain is critical to uptake and reuse of the data set(s).
+</p>
+
+<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE</a> Announce the Linked Open Data on multiple channels.  Be sure to have a plan in place to handle timely feedback.  Linked Open Data implies the public is looking at and using the data, so ensure you have people in place to handle the customer service and technical support required to support the global Web audience.
+</p>
+
+<p class='stmt'><a href="#NETWORK">NETWORK EFFECT</a> Establish and manage the network effect by helping other data stewards.  Support the use of Linked Open Data through guidance, pilot funding or technical assistance and know how.</p>
+
+<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT</a> Publishing Linked Open Data on the Web implies a social contract.  Associating a good open data license is necessary.  Regular updates and maintenance is a requirement. A permanent identifier scheme is highly recommended.  If authorities move or remove data that is published to the Web, third party applications or mashups can break which is clearly undesireable.  
 </p>