--- a/bp/index.html	Thu Apr 04 18:14:10 2013 +0100
+++ b/bp/index.html	Mon Apr 08 00:52:08 2013 +0200
@@ -512,13 +512,13 @@
 </p>
 
 <p>
-<a href='http://www.w3.org/TR/gld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new protocol element, that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore be used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
+<a href='http://www.w3.org/TR/gld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new protocol element, that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
 </p>
 
 <p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the IETF in March 2003.
 </p>
 
-<p>Althought there exist some standards focused on enabling the use of international characters in Web identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers. This section is not meant to be exhaustive and we point the interested audience to <a ref="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">An Introduction to Multilingual Web Addresses</a>, however some of the most relevant issues are following:
+<p>Although there exist some standards focused on enabling the use of international characters in Web identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers. This section is not meant to be exhaustive and we point the interested audience to <a ref="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">An Introduction to Multilingual Web Addresses</a>, however some of the most relevant issues are following:
 </p>
 
 <ul>
@@ -558,7 +558,7 @@
 <p>Notify your security official of your intent to publish open government data.</p>
 <ul>
 	<li>Provide an overview of the Linked Data project</li>
-	<li>Describe how you plan to host the data (e.g., cloud, agency data center), implementation timelines</li>
+	<li>Describe how you plan to host the data (e.g., cloud, agency data center), and provide implementation timelines</li>
 	<li>Consider including your hosting service/software vendor in discussion(s)</li>
 </ul>
 
@@ -569,7 +569,7 @@
 	<li>Request a system security plan template to ensure the plan is organized to facilitate the review process (if a vendor is contributing information on controls related to their service/software, the vendor needs to adhere to the template in their response)</li>
 </ul>
 
-<p>Security plans are typically comprised of a set of security controls, describing physical, procedural, technical and other processes and controls in a system which are in place to protect information access, availability and integrity, and for avoiding, counteracting and minimizing security risks. These are typically comprised of several layers, such as physical facility security, network and communications, to considerations of operating system, software, integration and many other elements. As such, there will typically be some common security controls which are inherited, and which may not be specific or unique to the linked data implementation, such as controls inherited from the hosting environment, whether cloud hosting provider, agency data center, et cetera. Additionally, some security controls will be inherited from the software vendors.</p>
+<p>Security plans are typically comprised of a set of security controls, describing physical, procedural, technical and other processes and controls in a system which are in place to protect information access, availability and integrity, and for avoiding, counteracting and minimizing security risks. These are typically comprised of several layers, that can range from physical facility security, network and communications, to considerations of operating system, software, integration and many other elements. As such, there will typically be some common security controls which are inherited, and which may not be specific or unique to the linked data implementation, such as controls inherited from the hosting environment, whether cloud hosting provider, agency data center, et cetera. Additionally, some security controls will be inherited from the software vendors.</p>
 
 <p>As such, opportunities may exist to streamline the development of a security plan, or conversely, to identify potential project security vulnerabilities and risks, through early engagement with hosting providers, software vendors and others who may be responsible for those common, inherited controls. If the inherited controls meet the recommendations, they can then be assembled following the requisite templates, and the system security plan can be completed through addition of any applicable controls specific or unique to the linked data application's configuration, implementation, processes or other elements described in the security control and security plan guidance.</p>
 
@@ -583,7 +583,7 @@
 <!-- <p class='todo'>To Review: Bernadette Hyland </p> -->
 
 <p>
-Publishers of Linked Data enter into an implicit social contract with users of their data.  Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be.  Here is a summary of best practices that relate to the implicite "social contract".  Additional informational details are included for reference.
+Publishers of Linked Data enter into an implicit social contract with users of their data.  Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be.  Here is a summary of best practices that relate to the implicit "social contract".  Additional informational details are included for reference.
 </p>
 
 <ul>
@@ -597,7 +597,7 @@
 </ul>
 
 <p>
-Giving due consideration your organization's URI strategy should be one of the first activities your team undertakes as they prepare a Linked Open Data strategy. Authoritative data requires the permanence and resolution of HTTP URIs.  If publishers move or remove data that was published to the Web, third party applications or mashups may break. This is considered rude for obvious reasons and is the basis for the Linked Data "social contract." A good way to prevent causing HTTP 404's is for your organization to implement a persistence strategy.
+Giving due consideration to your organization's URI strategy should be one of the first activities your team undertakes as they prepare a Linked Open Data strategy. Authoritative data requires the permanence and resolution of HTTP URIs.  If publishers move or remove data that was published to the Web, third party applications or mashups may break. This is considered rude for obvious reasons and is the basis for the Linked Data "social contract." A good way to prevent causing HTTP 404's is for your organization to implement a persistence strategy.
 </p>
 
 </section>

--- a/bp/respec-config.js	Thu Apr 04 18:14:10 2013 +0100
+++ b/bp/respec-config.js	Mon Apr 08 00:52:08 2013 +0200
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-    specStatus:           "ED",
-    publishDate:          "2013-03-26",
+    specStatus:           "WD",
+    publishDate:          "2013-04-08",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/