--- a/bp/index.html	Thu Mar 07 18:45:44 2013 +0000
+++ b/bp/index.html	Thu Mar 07 15:10:48 2013 -0500
@@ -658,6 +658,9 @@
 
 <p>Provide best practice recommendations for stakeholders on documenting the provenance of their linked government data and how to interpret that data so that consumers know what they are looking at.</p>
 
+Provenance = the sources that establish a context for the production and/or use of an artifact. See <a href="http://www.w3.org/2011/prov/wiki/Main_Page" target="_blank">W3C Provenance working group</a></li>
+
+
 <h3>Background</h3>
 <p>In 1997 Tim Berners-Lee called for pervasive provenance on the Web:</p>
 <p class="highlight">
@@ -744,48 +747,11 @@
 </section>
 
 
-<!--  << STABILITY   -->
+<!--  << PROPOSE REMOVING STABILITY due to lack of input   -->
 <section>
-<h2>Stability</h2>
-<!-- <p class="todo">To Review: Anne Washington (GMU), Ron Reck</p> -->
 
 <!-- << STABILITY.overview -->
-<h3>Overview</h3>
-<p>This section will focus how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.</p>
 
-<h3>Definition</h3>
-<p>The following definition is applicable to Linked Open Data.</p>
-<b>Stability.</b> <u>Stable</u> LOD is persistent, predictable and machine accessible from externally visible locations. 
-</p>
-<ul>
-	<li>Persistent = Information accessible for an unbounded period of time.</li>
-	<li>Predictable = Names and information follow a logical format.</li>
-	<li>Stable location = Externally visible locations are consistent in name, and availability.</li>
-	<li>Other things that impact stability
-		<ul>
-			<li>legacy = earlier naming schemes, formats, data storage devices</li>
-			<li>steward = people who are committed to consistently maintain specific datasets, either individuals or roles in organizations</li>
-			<li>provenance = the sources that establish a context for the production and/or use of an artifact. See <a href="http://www.w3.org/2011/prov/wiki/Main_Page" target="_blank">W3C Provenance working group</a></li>
-		</ul>
-	</li>
-</ul>
-
-<h3>Best practice for Stability</h3>
-
-<p>The length of time information is available is inherently connected to the value placed upon it. If information is deemed valuable, it is likely to persist for a longer period of time.  Value, which can change over time, is always determined based on a cost-benefit relationship; Any benefit derived from information is reduced by the cost(s) associated with using it.  Increasing stability requires the adoption of a strategy to allocate limited resources for achieving a goal. 
-</p>
-
-<h3>Organizational Success Factors</h3>
-<p>Organizational considerations without internal stability from the data stewards, any external technology stability is a challenge. The following are some organization characteristics for stable data.</p>
-<ul>
-	<li>Consistent human skills</li>
-	<li>Consistent infrastructure</li>
-	<li>Data related to organizational values or business needs</li>
-	<li>Internal champion or consistent business process</li>
-	<li>Internal politics on variation names do not impact external locations</li>
-</ul> 
-
-<!-- << STABILITY.Properties -->
 
 <h3>Stability Properties</h3>
 <p><i>These are characteristics that influence the stability or longevity. Many of these properties are not unique to LOD, yet they influence data cost and therefore data value.</i></p>

--- a/glossary/respec-config.js	Thu Mar 07 18:45:44 2013 +0000
+++ b/glossary/respec-config.js	Thu Mar 07 15:10:48 2013 -0500
@@ -1,6 +1,6 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-    specStatus:           "NOTE",
+    specStatus:           "LCWD",
     publishDate:          "2013-03-07",
     //copyrightStart:       "2011",