--- a/ldp-ucr.html Sun Dec 16 11:07:50 2012 -0500
+++ b/ldp-ucr.html Sun Dec 16 11:37:08 2012 -0500
@@ -102,31 +102,20 @@
</head>
<body>
<section id='abstract'>
-A set of best practices and simple approach for a read-write Linked Data architecture, based on
-HTTP access to web resources that describe their state using RDF.
+A set of user stories, use cases, scenarios and requirements that motivate a simple
+approach for a read-write Linked Data architecture, based on HTTP access to web
+resources that describe their state using RDF.
</section>
<section id='status'>
-<p>
-This document is currently under review pending release as a First Public Working Draft. While the
-editors have made every effort to identify a set of use-cases that are both evidenced in user-stories
-and in-scope of the charter, the document may yet be missing some key unidentified use-cases, or indeed, m
-ay include use-cases that ought to be removed. Furthermore, the coarse grouping of use-cases to avoid CRUDdy
-operations may not be to people's taste and is open to challenge.</p>
-<p>
-Following feedback from the face-to-face, the use-cases are captured in a narrative style that describes a behaviour, or set of behaviours drawn from user-stories. They are embellished with concrete examples drawn from representative user-stories. The aim throughout has been to avoid details of protocol (specifically the HTTP protocol), and use of any specific vocabulary that might be introduced by the LDP specification.
-</p>
+
</section>
<section>
<h1 id="scope">Scope and Motivation</h1>
<p>
Linked Data was defined by Tim Berners-Lee with the following
- guidelines <a
- href="http://www.w3.org/DesignIssues/LinkedData.html"
- class="external autonumber"
- title="http://www.w3.org/DesignIssues/LinkedData.html"
- rel="nofollow">[1]</a>:
+ guidelines [[LINKED-DATA]]:
</p>
<ol>
<li>Use URIs as names for things</li>
@@ -208,6 +197,13 @@
<section>
<h1 id="org">Organization of this Document</h1>
+
+<p>
+ Use-cases are captured in a narrative style that describes a
+ behavior, or set of behaviors drawn from user-stories. They are embellished with concrete examples drawn
+ from representative user-stories. The aim throughout has been to avoid details of protocol (specifically
+ the HTTP protocol), and use of any specific vocabulary that might be introduced by the LDP specification.
+</p>
<p>This document is organized as follows:</p>
<ul>
<li><b><a href="#user-stories" title=""> User Stories</a></b>