--- a/ldbp.html Mon Oct 08 16:51:49 2012 -0400
+++ b/ldbp.html Sun Oct 14 22:46:45 2012 -0400
@@ -83,6 +83,21 @@
</script>
<style type="text/css">
div.rule {padding-top: 1em;}
+ div.ldp-issue {
+ border-color: #E05252;
+ background: #FBE9E9;
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+ border-left-width: .5em;
+ border-left-style: solid;
+ }
+ div.ldp-issue-title {
+ color: #E05252;
+ padding-right: 1em;
+ min-width: 7.5em;
+ }
</style>
</head>
<body>
@@ -170,6 +185,11 @@
[[HTTP11]]</dd>
</dl>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/8">ISSUE-8</a></div>
+ Better define or just not use the "Basic profile" terminology
+ </div>
+
<section>
<h2 id="conventions">Conventions Used in This Document</h2>
@@ -253,7 +273,14 @@
These predicate URIs MUST identify BPRs whose representations are
retrievable. BPR servers SHOULD provide an RDF Schema [[!RDF-SCHEMA]]
representation of these predicates.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/9">ISSUE-9</a></div>
+ Should properties used in BPR representations be BPRs?
</div>
+ </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 [[!XMLSCHEMA11-2]] and [[!RDF-PRIMER]] are to be used: </div>
@@ -278,6 +305,11 @@
<tr><td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code></td><td>Literal XML value as specified by RDF</td></tr>
</tbody>
</table>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/6">ISSUE-6</a></div>
+ Should LDBP say that any kind of user-defined simple data type is disallowed?
+ </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
@@ -296,7 +328,29 @@
</div>
<div id="bpr-4_1_13" class="rule">4.1.13 BPR server responses MUST contain accurate response <code>ETag</code>
header values.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/10">ISSUE-10</a></div>
+ Include clarifications and guidance around ETags
</div>
+ </div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/2">ISSUE-2</a></div>
+ Do BPR versions get managed in a systematic, discoverable way?
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/15">ISSUE-15</a></div>
+ sharing binary resources and metadata
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/16">ISSUE-16</a></div>
+ Redirection of non-information resources to BPRs
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/19">ISSUE-19</a></div>
+ Adressing more error cases
+ </div>
</section>
<section>
@@ -336,6 +390,11 @@
to support a more sophisticated merge of data provided by the client
with existing state stored on the server for a resource MUST use HTTP
PATCH, not HTTP PUT.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/11">ISSUE-11</a></div>
+ Do we need to define server-managed properties or do we leave them to applications?
+ </div>
</div>
<div id="bpr-4_4_2" class="rule">4.4.2 BPR clients SHOULD use the HTTP <code>If-Match</code>
header and HTTP <code>ETags</code> to ensure it isn’t
@@ -418,6 +477,15 @@
server enforcement of detailed, domain-specific constraints will
greatly restrict the types of clients who can update resources.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/12">ISSUE-12</a></div>
+ Can HTTP PATCH be used for resource creation?
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/17">ISSUE-17</a></div>
+ changesets as a recommended PATCH format
+ </div>
</section>
<section>
@@ -947,6 +1015,11 @@
from the server application vocabulary. If there is no obvious
predicate from the server application vocabulary to use, BPC servers
SHOULD use the <code>rdfs:member</code> predicate.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/21">ISSUE-21</a></div>
+ container affordances
+ </div>
</div>
<div id="bpc-5_2_4" class="rule">5.2.4 A BPC MUST contain one triple for the <code>bp:membershipSubject</code>
predicate that indicates the subject of the membership triples when container subject is not the BPC itself.
@@ -962,6 +1035,11 @@
information about the members without the client having to do a GET
on each member individually. See section <a href="#bpc-member_data">5.1.1 Container
Member Information</a> for additional details.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/13">ISSUE-13</a></div>
+ Include clarifications about BPC representations that include member triples
+ </div>
</div>
<div id="bpc-5_2_7" class="rule">5.2.7 The representation of a BPC MUST have <code>rdf:type</code>
of <code>bp:Container</code>, but it MAY have additional
@@ -970,6 +1048,11 @@
<div id="bpc-5_2_8" class="rule">5.2.8 BPCs SHOULD NOT use RDF container types <code>rdf:Bag</code>,
<code>rdf:Seq</code> and <code>rdf:List</code>.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/3">ISSUE-3</a></div>
+ Do BPC versions get managed in a systematic, discoverable way?
+ </div>
</section>
<section>
@@ -1029,12 +1112,23 @@
<div id="bpc-5_3_6_3" class="rule">5.3.6.3 The last page resource representation MUST have one triple with the subject of the
last page, predicate of <code>bp:nextPage</code> and object being <code>rdf:nil</code>.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/18">ISSUE-18</a></div>
+ container membership and robust pagination
+ </div>
+
<div id="bpc-5_3_7" class="rule">5.3.7 BPC servers MAY represent the members of a paged BPC in a sequential
order. The order MUST be specified using the <code>bp:containerSortPredicates</code>
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-QUERY]].
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/14">ISSUE-14</a></div>
+ Include clarifications about ordering in BPC representations
+ </div>
</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
@@ -1083,6 +1177,11 @@
triples whose subject is the null relative URI will usually result in
triples in the created resource whose subject is the created
resource.
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/20">ISSUE-20</a></div>
+ Identifying and naming POSTed resources
+ </div>
</div>
<div id="bpc-5_4_9" class="rule">5.4.9 BPC servers SHOULD assign the subject URI for the resource to be
created using server application specific rules.
@@ -1135,6 +1234,11 @@
method for updating BPC non-membership properties.
</div>
</section>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/7">ISSUE-7</a></div>
+ What operations are permittered on containers and how do they get invoked?
+ </div>
</section>
<section class='appendix informative'>
@@ -1153,12 +1257,13 @@
<section class='appendix informative' id="history">
<h1>Change History</h1>
<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>
- <li>2012-09-19 - Fixed rdfs:label range to be rdfs:Literal</li>
- <li>2012-09-19 - ISSUE-1 Define Turtle as the required serialization format for LDP</li>
- <li>2012-09-20 - Sent pull request re LINKED-DATA and added suggestion for <code>ldp</code> namespace</li>
+ <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> (SS)</li>
+ <li>2012-09-18 - Fixed up some links and worked on references, work left to do. (SS)</li>
+ <li>2012-09-19 - Repairing references and forward reference to biblio.js updates (SS)</li>
+ <li>2012-09-19 - Fixed rdfs:label range to be rdfs:Literal (SS)</li>
+ <li>2012-09-19 - ISSUE-1 Define Turtle as the required serialization format for LDP (SS)</li>
+ <li>2012-09-20 - Sent pull request re LINKED-DATA and added suggestion for <code>ldp</code> namespace (SS)</li>
+ <li>2012-10-14 - Added open ISSUES and formating to prep for public working draft (SS)</li>
</ul></section>
<section class='appendix informative' id="todos">
@@ -1169,6 +1274,11 @@
<li>What namespace URIs should be used for editor's and FPWD? Currently we 'borrow' open-services.net - Michael says: http://www.w3.org/ns/ldp# (we use it in the GLD for other vocab, such as <a href="http://www.w3.org/ns/org#">ORG</a>) - guess we should raise an issue for that ...</li>
<li>Confirm short name for this as 'ldbp'</li>
</ul>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/5">ISSUE-5</a></div>
+ Add a section explaining how LDBP is related to Graph Store Protocol
+ </div>
</section>
</body>