--- a/ldbp.html Tue Sep 18 17:11:56 2012 -0400
+++ b/ldbp.html Wed Sep 19 09:14:38 2012 -0400
@@ -36,7 +36,7 @@
previousURI: "http://www.w3.org/Submission/2012/SUBM-ldbp-20120326/",
// if there a publicly available Editor's Draft, this is the link
- edDraftURI: "https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldbp.html",
+ edDraftURI: "http://www.w3.org/2012/ldp/hg/ldbp.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -95,7 +95,7 @@
of HTTP for accessing, updating, creating and deleting resources from
servers that expose their resources as Linked Data. It provides some
new rules as well as clarifications and extensions of the four rules
- of Linked Data [4Rules]</p>
+ of Linked Data [[LINKED-DATA]]</p>
<p>1. Use URIs as names for things</p>
<p>2. Use HTTP URIs so that people can look up those
names</p>
@@ -139,7 +139,7 @@
of a URI.[[WEBARCH]]</dd>
<dt>Linked Data</dt>
- <dd>As defined by Tim Berners-Lee. [4Rules]</dd>
+ <dd>As defined by Tim Berners-Lee. [[LINKED-DATA]]</dd>
<dt>Profile</dt>
<dd>A specification that defines the needed components from other specifications as
@@ -194,7 +194,7 @@
that contain data for an entity in some domain, which could be
commercial, governmental, scientific, religious, or other.</p>
<p>Some of the rules defined in this document provide
- clarification and refinement of the base Linked Data rules [4Rules],
+ clarification and refinement of the base Linked Data rules [[LINKED-DATA]],
others address additional needs.</p>
<p>The rules for Basic Profile Resources address basic
questions such as:</p>
@@ -214,7 +214,7 @@
<section>
<h2 id="bpr-general">General</h2>
- <div id="bpr-4_1_1" class="rule">4.1.1 BPR servers MUST at least be HTTP/1.1 conformant servers [[HTTP11]].</div>
+ <div id="bpr-4_1_1" class="rule">4.1.1 BPR servers MUST at least be HTTP/1.1 conformant servers [[!HTTP11]].</div>
<div id="bpr-4_1_2" class="rule">4.1.2 BPR servers MUST provide an RDF representation for BPRs. The subject
is typically the BPR itself.
</div>
@@ -230,7 +230,7 @@
BPR. Clients SHOULD use that canonical URL to identify the BPR.
</div>
<div id="bpr-4_1_5" class="rule">4.1.5 BPR predicates SHOULD use standard vocabularies such as Dublin Core
- [Dublin Core], RDF [[RDF-PRIMER]] and RDF Schema [RDF Schema], whenever
+ [[!DC-TERMS]], RDF [[!RDF-PRIMER]] and RDF Schema [[!RDF-SCHEMA]], whenever
possible. BPRs SHOULD reuse existing vocabularies instead of creating
their own duplicate vocabulary terms.
</div>
@@ -241,7 +241,7 @@
<div id="bpr-4_1_6_1" class="rule">4.1.6.1 BPRs MUST use the predicate <code>rdf:type</code> to
represent the concept of type. The use of non-standard type
predicates, as well as <code>dcterms:type</code>, is
- discouraged. [DC-RDF]
+ discouraged. [[!DC-RDF]]
</div>
<div id="bpr-4_1_7" class="rule">4.1.7 BPR representations SHOULD have at least one <code>rdf:type</code>
set explicitly. This makes the representations much more useful to
@@ -249,13 +249,12 @@
</div>
<div id="bpr-4_1_8" class="rule">4.1.8 Predicate URIs used in BPR representations SHOULD be HTTP URLs.
These predicate URIs MUST identify BPRs whose representations are
- retrievable. BPR servers SHOULD provide an RDF Schema [RDF Schema]
+ retrievable. BPR servers SHOULD provide an RDF Schema [[!RDF-SCHEMA]]
representation of these predicates.
</div>
<div id="bpr-4_1_9" class="rule">4.1.9 BPR representations MUST use only the following standard datatypes.
RDF does not by itself define datatypes to be used for literal
- property values, therefore a set of standard datatypes based on [XSD
- Datatypes] and [[RDF-PRIMER]] are to be used: </div>
+ property values, therefore a set of standard datatypes based on [[!XMLSCHEMA11-2]] and [[!RDF-PRIMER]] are to be used: </div>
<table border="1" cellspacing="5" summary="Datatype to use with RDF literals">
<thead>
<tr><th>URI</th><th>Description</th></tr>
@@ -287,11 +286,11 @@
</div>
<div id="bpr-4_1_11" class="rule">4.1.11 BPR servers MAY support additional standard representations. These
could be other RDF formats, like N3 or NTriples, but non-RDF formats
- like HTML [[HTML401]]and JSON [JSON] would be likely be common.
+ like HTML [[!HTML401]]and JSON [[!RFC4627]] would be likely be common.
</div>
<div id="bpr-4_1_12" class="rule">4.1.12 BPRs MAY be created, updated and deleted using methods not defined in
this document, for example through application-specific means, SPARQL
- UPDATE, etc. [SPARQL-UPDATE]
+ UPDATE, etc. [[!RDF-SPARQL-UPDATE]]
</div>
<div id="bpr-4_1_13" class="rule">4.1.13 BPR server responses MUST contain accurate response <code>ETag</code>
header values.
@@ -342,7 +341,7 @@
its representation. BPR servers SHOULD require the HTTP <code>If-Match</code> header and HTTP <code>ETags</code>
to detect collisions. BPR servers MUST respond with status code 412
(Condition Failed) if <code>ETag</code>s fail to match if there are no other
- errors with the request. [[HTTP11]]
+ errors with the request. [[!HTTP11]]
</div>
<div id="bpr-4_4_3" class="rule">4.4.3 BPR clients SHOULD always assume that the set of predicates for a
resource of a particular type at an arbitrary server is open in the
@@ -361,7 +360,7 @@
it doesn’t change whether it understands the predicates or not, when
its intent is to perform an update using HTTP PUT. The use of HTTP
PATCH instead of HTTP PUT for update avoids this burden for clients
- [RFC5789].
+ [[RFC5789]].
</div>
<div id="bpr-4_4_6" class="rule">4.4.6 BPR servers MAY choose to allow the creation of new resources using HTTP PUT.
</div>
@@ -406,7 +405,7 @@
<section>
<h2 id="bpr-HTTP_PATCH">HTTP PATCH</h2>
<div id="bpr-4_7_1" class="rule">4.7.1 BPR servers MAY implement HTTP PATCH to allow modifications,
- especially partial replacement, of their resources. [RFC5789] No
+ especially partial replacement, of their resources. [[!RFC5789]] No
minimal set of patch document formats is mandated by this document.
</div>
<div id="bpr-4_7_2" class="rule">4.7.2 BPR servers SHOULD allow clients to update resources without
@@ -502,7 +501,7 @@
<p>
The predicate <code>dcterms:type</code> SHOULD NOT be
- used, instead use <code>rdf:type</code>. [DC-RDF].
+ used, instead use <code>rdf:type</code>. [[!DC-RDF]].
</p>
<div id="bpr-4_8_2" class="rule">4.8.2 From RDF</div>
@@ -656,7 +655,7 @@
</p>
<div id="bpc-member_data" class="rule">5.1.1 Container Member Information</div>
- <em>This section is informative</em>
+ <em>This section is non-normative</em>
<p>In many – perhaps most – applications
involving containers, it is desirable for the client to be able to
get information about each container member without having to do a
@@ -704,7 +703,7 @@
<div id="bpc-get_non-member_props" class="rule">5.1.2 Retrieving Only Non-member Properties
</div>
- <em>This section is informative</em>
+ <em>This section is non-normative</em>
<p>The representation of a container
that has many members will be large. There are several important
cases where clients need to access only the non-member properties of
@@ -718,7 +717,7 @@
a simple case where only a few simple non-member properties are
retrieved. In real world situations more complex cases are likely, such as those that add other predicates to
containers, for example providing validation information and
- associating SPARQL endpoints. [SPARQL]</p>
+ associating SPARQL endpoints. [[RDF-SPARQL-QUERY]]</p>
<p>
Here is an example requesting the non-member properties of a
container identified by the URL <code>http://example.org/container1</code>
@@ -746,7 +745,7 @@
dcterms:publisher <http://acme.com/>.</pre>
<div id="bpc-paging" class="rule">5.1.3 Paging</div>
- <em>This section is informative</em>
+ <em>This section is non-normative</em>
<p>It sometimes happens that a
container is too large to reasonably transmit its representation in a
single HTTP response. This will be especially true if the container
@@ -852,7 +851,7 @@
for the member.</p>
<div id="bpc-ordering" class="rule">5.1.4 Ordering</div>
- <em>This section is informative</em>
+ <em>This section is non-normative</em>
<p>
There are many cases where an ordering of the members of the
container is important. BPC does not provide any particular support
@@ -1033,7 +1032,7 @@
predicate whose subject is that of the page and object is a list of
BPC ordinal predicates. The default ordering is ascending. The only
ordinal predicate literal data types supported are those as defined
- by SPARQL SELECT’s ORDER BY clause [SPARQL].
+ by SPARQL SELECT’s ORDER BY clause [[!RDF-SPARQL-QUERY]].
</div>
<div id="bpc-5_3_7_1" class="rule">5.3.7.1 The object of <code>bp:containerSortPredicates</code>’,
the predicate used to indicate ordering, MUST NOT change between
@@ -1136,119 +1135,36 @@
</section>
</section>
-<section class='appendix'>
-<h2 id="normative_refs">Normative References</h2>
-
-<div class='note'>
-<p>Working to fold these references into auto generated ReSpec but missing from biblio</p>
-</div>
-
- <dl>
- <dt>Dublin Core</dt>
- <!-- TODO: I see DC Elements in biblio but not DC Terms -->
- <dd><cite>
- <a href="http://dublincore.org/documents/2010/10/11/dcmi-terms/">Dublin Core
- Metadata Initiative</a></cite>
- <a href="http://dublincore.org/documents/2010/10/11/dcmi-terms/"> Terms
- </a>, DCMI Recommendation, 11 October 2010. This version is
- http://dublincore.org/documents/2010/10/11/dcmi-terms/. The latest
- version is http://dublincore.org/documents/dcmi-terms/.
- </dd>
-
- <dt>RFC5789</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd><cite>
- <a href="http://tools.ietf.org/html/rfc5789">PATCH Method for HTTP
- </a></cite>, L Dusseault, J. Snell, March 2010. Available at
- http://tools.ietf.org/html/rfc5789
- </dd>
-
- <dt>SPARQL-UPDATE</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd><cite>
- <a href="http://www.w3.org/TR/2010/WD-sparql11-update-20100126/">
- SPARQL 1.1 Update</a></cite>, S. Schenk, P. Gearon, Editor,
- W3C Working Draft, 26 January 2010,
- http://www.w3.org/TR/2010/WD-sparql11-update-20100126/. <a
- href="http://www.w3.org/TR/sparql11-update/">Latest version
- </a> available at http://www.w3.org/TR/sparql11-update/.
- </dd>
- </dl>
-</section>
+<section class='appendix informative'>
+<h2>Acknowledgements</h2>
+
+ <p>The following people have been instrumental in providing thoughts, feedback,
+reviews, criticism and input in the creation of this specification:</p>
-<section class='appendix'>
-<h2 id="informative_refs">Informative References</h2>
-
-<div class='note'>
-<p>Working to fold these references into auto generated ReSpec but missing from biblio</p>
-</div>
- <dl>
- <dt>4Rules</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd><cite>
- <a href="http://www.w3.org/DesignIssues/LinkedData.html">Linked Data
- Design Issues</a></cite>, Tim Berners-Lee, 27 July 2006, <a
- href="http://www.w3.org/DesignIssues/LinkedData.html">http://www.w3.org/DesignIssues/LinkedData.html
- </a>
- </dd>
-
- <dt>DC-RDF</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd><cite>
- <a href="http://dublincore.org/documents/dc-rdf/">Expressing
- Dublin Core metadata using the Resource Description Framework
- (RDF)</a></cite>, M. Nilsson and all, 14 January 2008,
- http://dublincore.org/documents/2008/01/14/dc-rdf/. Latest available
- at: http://dublincore.org/documents/dc-rdf/.
- </dd>
-
- <dt>JSON</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd>JSON reference</dd>
-
- <dt>SPARQL</dt>
- <!-- TODO: Doesn't appear to be in biblio -->
- <dd><cite>
- <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/">SPARQL Query
- Language for RDF</a></cite>, E. Prud'hommeaux, A. Seaborne,
- Editor, W3C Recommendation, 15 January 2008,
- http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/. <a
- href="http://www.w3.org/TR/rdf-sparql-query/">Latest version
- </a> available at http://www.w3.org/TR/rdf-sparql-query/.
- </dd>
-
- </dl>
+ <ul>
+ <li>Martin P. Nally</li>
+ <li>John Arwe</li>
+ <li>Arnaud le Hors</li>
+ </ul>
</section>
-
+
<section class='appendix informative' id="history">
<h1>Change History</h1>
-<p>2012-09-18 - Initial ReSpec'ing of <a href="http://www.w3.org/Submission/ldbp/">Member Submission - Linked Data Basic Profile 1.0</a>
-<p>2012-09-18 - Fixed up some links and worked on references, work left to do.</p>
-</section>
+<ul>
+ <li>2012-09-18 - Initial ReSpec'ing of <a href="http://www.w3.org/Submission/ldbp/">Member Submission - Linked Data Basic Profile 1.0</a></li>
+ <li>2012-09-18 - Fixed up some links and worked on references, work left to do.</li>
+ <li>2012-09-19 - Repairing references and forward reference to biblio.js updates</li>
+</ul></section>
<section class='appendix informative' id="todos">
<h1>Editor Todos and Notes</h1>
<p>Other than LDP <a href="http://www.w3.org/2012/ldp/track/actions">open actions</a> and <a href="http://www.w3.org/2012/ldp/track/issues">issues</a>, included here are transient tasks and notes
editors use. They have not meaning in final product of a published working draft and will be removed prior to publishing.</p>
<ul>
- <li>Fix up h3 references which are hacked div's at the moment</li>
- <li>References don't follow ReSpec's handy format</li>
<li>What namespace URIs should be used for editor's and FPWD? Currently we 'borrow' open-services.net</li>
<li>Confirm short name for this as 'ldbp'</li>
</ul>
</section>
-
- <section class='appendix informative'>
- <h2>Acknowledgements</h2>
-
- <p>The following people have been instrumental in providing thoughts, feedback,
- reviews, criticism and input in the creation of this specification:</p>
-
- <ul>
- <li>Martin P. Nally (IBM)</li>
- <li>John Arwe (IBM)</li>
- <li>Arnaud le Hors (IBM)</li>
- </ul>
- </section>
+
</body>
</html>