--- a/ldbp.html Tue Sep 18 13:39:21 2012 -0400
+++ b/ldbp.html Tue Sep 18 17:11:56 2012 -0400
@@ -32,10 +32,11 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
previousPublishDate: "2012-03-26",
- previousMaturity: "SUBM",
+ previousMaturity: "Member-SUBM",
+ 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/ldbp.html",
+ edDraftURI: "https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldbp.html",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
@@ -75,10 +76,11 @@
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/55082/status",
+ doRDFa: "1.1",
};
</script>
<style type="text/css">
- div.rule {padding-top: 1em;}
+ div.rule {padding-top: 1em;}
</style>
</head>
<body>
@@ -129,12 +131,12 @@
<section>
<h1 id="terms">Terminology</h1>
-<p>Terminology is based on W3C's Architecture of the World Wide Web [WEBARCH] and Hyper-text Transfer Protocol [RFC2616]
+<p>Terminology is based on W3C's Architecture of the World Wide Web [[WEBARCH]] and Hyper-text Transfer Protocol [[HTTP11]]
</p>
<dl class="glossary">
<dt>Link</dt>
<dd>A relationship between two resources when one resource (representation) refers to the other resource by means
- of a URI. [WEBARCH]</dd>
+ of a URI.[[WEBARCH]]</dd>
<dt>Linked Data</dt>
<dd>As defined by Tim Berners-Lee. [4Rules]</dd>
@@ -152,7 +154,7 @@
document for managing membership.</dd>
<dt>Client</dt>
- <dd>A program that establishes connections for the purpose of sending requests. [RFC2616]</dd>
+ <dd>A program that establishes connections for the purpose of sending requests. [[HTTP11]]</dd>
<dt>Server</dt>
<dd>An application
@@ -163,14 +165,14 @@
connection, rather than to the program's capabilities in general.
Likewise, any server may act as an origin server, proxy, gateway,
or tunnel, switching behavior based on the nature of each request.
- [RFC2616]</dd>
+ [[HTTP11]]</dd>
</dl>
<section>
<h2 id="conventions">Conventions Used in This Document</h2>
<p>Sample resource representations are provided in <code>text/turtle</code>
- format [TURTLE].</p>
+ format [[TURTLE]].</p>
<p>Commonly used namespace prefixes:</p>
<pre style="word-wrap: break-word; white-space: pre-wrap;">
@prefix dcterms: <http://purl.org/dc/terms/>.
@@ -212,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 [RFC2616].</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>
@@ -228,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] and RDF Schema [RDF Schema], whenever
+ [Dublin Core], RDF [[RDF-PRIMER]] and RDF Schema [RDF Schema], whenever
possible. BPRs SHOULD reuse existing vocabularies instead of creating
their own duplicate vocabulary terms.
</div>
@@ -253,7 +255,7 @@
<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] are to be used: </div>
+ Datatypes] 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>
@@ -276,7 +278,6 @@
</tbody>
</table>
- </div>
<div id="bpr-4_1_10" class="rule">4.1.10 BPRs MUST use at least one RDF triple to represent a link
(relationship) to another resource. In other words, having the source
resource’s URI as the subject and the target resource’s URI as the
@@ -286,7 +287,7 @@
</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 and JSON would be likely be common.
+ like HTML [[HTML401]]and JSON [JSON] 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
@@ -341,7 +342,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. [RFC2616]
+ 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
@@ -717,7 +718,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.</p>
+ associating SPARQL endpoints. [SPARQL]</p>
<p>
Here is an example requesting the non-member properties of a
container identified by the URL <code>http://example.org/container1</code>
@@ -912,7 +913,7 @@
o:value 50.00.
<http://example.org/netWorth/nw1/assetContainer/a3>
a o:RealEstateHolding;
- o:value 300000.</pre></div>
+ o:value 300000.</pre>
<p>
As you can see by the addition of the <code>bp:containerSortPredicates</code>
predicate, the <code>o:value</code> predicate is used
@@ -1135,11 +1136,16 @@
</section>
</section>
-
<section class='appendix'>
<h2 id="normative_refs">Normative References</h2>
- <div><dl>
+
+<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>
@@ -1149,51 +1155,16 @@
version is http://dublincore.org/documents/dcmi-terms/.
</dd>
- <dt>RDF</dt>
- <dd><cite><a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210/">Resource Description Framework (RDF): Concepts and Abstract Syntax</a></cite>, Klyne G.,
- Carroll J. (Editors), W3C Recommendation, 10 February 2004.
- This version is http://www.w3.org/TR/2004/REC-rdf-primer-20040210/.
- The <a href="http://www.w3.org/TR/rdf-concepts/">latest version</a> is http://www.w3.org/TR/rdf-concepts/.</dd>
-
- <dt>RFC2119</dt>
- <dd><cite>
- <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC 2119:
- Key words for use in RFCs to Indicate Requirement Levels
- </a></cite>, Scott Bradner, 1997. (See
- http://www.ietf.org/rfc/rfc2119.txt)
- </dd>
-
- <dt>RFC2616</dt>
- <dd><cite>
- <a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext
- Transfer Protocol - HTTP/1.1
- </a></cite>. J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T.
- Berners-Lee, June 1999. Available at
- http://www.ietf.org/rfc/rfc2616.txt.
- </dd>
-
- <dt>RFC3986</dt>
- <dd><cite>
- <a href="http://www.apps.ietf.org/rfc/rfc3986.html">Uniform
- Resource Identifier (URI): Generic Syntax
- </a></cite>, Berners-Lee, Fielding, Masinter, January 2005.
- </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>RFC3987</dt>
- <dd><cite>
- <a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized
- Resource Identifiers (IRIs)
- </a></cite>, Duerst, Suignard, January 2005.
- </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,
@@ -1207,8 +1178,13 @@
<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
@@ -1217,6 +1193,7 @@
</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
@@ -1225,68 +1202,12 @@
at: http://dublincore.org/documents/dc-rdf/.
</dd>
- <dt>HTML 4.01</dt>
- <dd><cite>
- <a href="http://www.w3.org/TR/html4/">HTML 4.01
- Specification</a></cite>, D. Raggett, A. Le Hors, and I.
- Jacobs, 1999. (See http://www.w3.org/TR/html4/)
- </dd>
-
-<dt>IANA</dt>
-<dd><cite><a href="http://www.iana.org/assignments/media-types/index.html">Internet Assigned Numbers Authority
-(IANA)</a></cite> MIME Media Types, http://www.iana.org/assignments/media-types/index.html</dd>
-
- <dt>LinkedData</dt>
- <dd><cite><a
- href="http://www.w3.org/standards/semanticweb/data">Linked Data at W3C</a></cite>,
- http://www.w3.org/standards/semanticweb/data</a>
- </dd>
-
- <dt>OSLC</dt>
- <dd><cite><a href="http://open-services.net/">Open Services for Lifecycle Collaboration (OSLC)</a></cite>, http://open-services.net</dd>
-
- <dt>RDF Primer</dt>
- <dd><cite>
- <a href="http://www.w3.org/TR/2004/REC-rdf-primer-20040210">Resource
- Description Framework (RDF): Concepts and Abstract Syntax
- </a></cite>, Klyne G., Carroll J. (Editors), W3C Recommendation, 10 February
- 2004. This version is
- http://www.w3.org/TR/2004/REC-rdf-primer-20040210/. The <a href="http://www.w3.org/TR/rdf-primer/">latest
- version</a> is http://www.w3.org/TR/rdf-primer/.
- </dd>
-
- <dt>RDF-MT</dt>
- <dd><cite>
- <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210/">RDF
- Semantics</a></cite>, P. Hayes, Editor, W3C
- Recommendation, 10 February 2004,
- http://www.w3.org/TR/2004/REC-rdf-mt-20040210/. <a
- href="http://www.w3.org/TR/rdf-mt/">Latest version
- </a> available at http://www.w3.org/TR/rdf-mt/.
- </dd>
-
- <dt>RDF-REST</dt>
- <dd><cite><a href="http://www.w3.org/2001/sw/wiki/index.php?title=REST">RDF Simple Data Interface Protocol – Level Zero</a></cite>,
- Latest version available at:
- http://www.w3.org/2001/sw/wiki/index.php?title=REST</dd>
-
- <dt>REST</dt>
- <dd><cite>
- <a
- href="http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_arch_style.htm">Representational
- State Transfer (REST)</a></cite>, R. Fielding, Ph.D. dissertation,
- 2000, <a
- href="http://www.ics.uci.edu/%7Efielding/pubs/dissertation/rest_arch_style.htm">Latest version
- </a> available at
- http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm
- .
- </dd>
-
- <dt>RW LinkedData</dt>
- <dd><cite><a href="http://www.w3.org/DesignIssues/ReadWriteLinkedData.html">Read-Write Linked Data</a></cite>,
- Berners-Lee, August 2009, http://www.w3.org/DesignIssues/ReadWriteLinkedData.html</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,
@@ -1296,40 +1217,13 @@
</a> available at http://www.w3.org/TR/rdf-sparql-query/.
</dd>
- <dt>SPARQL-HTTP</dt>
- <dd>
- SPARQL 1.1 Graph Store HTTP Protocol, Latest version available at <a
- href="http://www.w3.org/2009/sparql/docs/http-rdf-update/">http://www.w3.org/2009/sparql/docs/http-rdf-update/
- </a>
- </dd>
-
- <dt>TURTLE</dt>
- <dd><cite>
- <a href="http://www.w3.org/TeamSubmission/2011/SUBM-turtle-20110328/">Turtle -
- Terse RDF Triple Language
- </a></cite>, D. Beckett, T. Berners-Lee, Team Submission, 28 March 2011,
- http://www.w3.org/TeamSubmission/2011/SUBM-turtle-20110328/. Latest
- version available at http://www.w3.org/TeamSubmission/turtle/.
- </dd>
-
- <dt>WEBARCH</dt>
- <dd><cite>
- <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">Architecture
- of the World Wide Web, Volume One</a></cite>
- , N. Walsh, I. Jacobs, Editors,
- W3C Recommendation, 15 December 2004,
- http://www.w3.org/TR/2004/REC-webarch-20041215/. <a
- href="http://www.w3.org/TR/webarch/">Latest version
- </a> available at http://www.w3.org/TR/webarch/.
- </dd>
</dl>
</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>
+<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>
<section class='appendix informative' id="todos">
@@ -1339,7 +1233,8 @@
<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 URIs should be used for editor's and PWD? Currently we 'borrow' open-services.net</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>