Added new issues ranging from 26-43. Removed closed/deferred issues: 2 & 3
--- a/ldp.html Wed Jan 16 15:38:37 2013 -0500
+++ b/ldp.html Wed Jan 16 16:43:56 2013 -0500
@@ -150,6 +150,11 @@
narrow to provide a set of key rules for reading and writing Linked
Data that most, if not all, other specifications will depend on and
implementations will support.</p>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>
+ What is the LDP data model and the LDP interaction model?
+ </div>
</section>
<section>
@@ -256,7 +261,10 @@
<p>The following sections define the rules and
guidelines for use of LDPRs.</p>
- <!-- TODO: Consider adding RDF into the description -->
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/31">ISSUE-31</a></div>
+ Proper Conformance section for LDP
+ </div>
<section>
<h2 id="ldpr-general">General</h2>
@@ -335,10 +343,6 @@
</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 LDPR 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>
@@ -350,6 +354,14 @@
<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>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/32">ISSUE-32</a></div>
+ How can clients discover that a resource is an LDPR or LDPC, and what features are supported?
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/33">ISSUE-33</a></div>
+ Pagination for non-container resources
+ </div>
<div id="ldpr-4_1_13" class="rule">4.1.13 LDPR
servers SHOULD enable simple creation and modification of LDPRs.
@@ -502,6 +514,10 @@
<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>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/27">ISSUE-27</a></div>
+ Should the PATCH method be used, as opposed to POST with a given mime type?
</div>
</section>
@@ -1076,9 +1092,17 @@
</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 LDPC versions get managed in a systematic, discoverable way?
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/34">ISSUE-34</a></div>
+ Adding and removing arcs in weak aggregation
</div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/36">ISSUE-36</a></div>
+ Can applications create new containers?
+ </div>
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/38">ISSUE-38</a></div>
+ filtered representations and inlining
+ </div>
</section>
<section>
@@ -1185,6 +1209,12 @@
added through other means - for example through the user interface of
the site that implements the LDPC.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/35">ISSUE-35</a></div>
+ POSTing to a container MUST yield a fresh URI
+ </div>
+
<div id="ldpc-5_4_3" class="rule">5.4.3 LDPC servers MAY accept an HTTP POST of non-RDF representations for
creation of any kind of resource, for example binary resources.
</div>
@@ -1196,6 +1226,12 @@
words, clients should not expect any representation in the response
entity body on a 201 (Created) response.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/39">ISSUE-39</a></div>
+ HTTP status codes used for creation
+ </div>
+
<div id="ldpc-5_4_6" class="rule">5.4.6 LDPC servers MUST accept a request entity body with a request header
of <code>Content-Type</code> with value of <code>text/turtle</code> [[!TURTLE]].
</div>
@@ -1216,9 +1252,17 @@
Identifying and naming POSTed resources
</div>
</div>
+
<div id="ldpc-5_4_9" class="rule">5.4.9 LDPC servers SHOULD assign the subject URI for the resource to be
created using server application specific rules.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/43">ISSUE-43</a></div>
+ hint at naming a resource on creation
+ </div>
+
+
<div id="ldpc-5_4_10" class="rule">5.4.10 LDPC servers SHOULD allow clients to create new resources without
requiring detailed knowledge of application-specific constraints.
This is a consequence of the requirement to
@@ -1255,6 +1299,11 @@
delete the resources that are referenced as its contents. The LDPC memebership triple MUST also be updated as defined
by <a href="#ldpc-5_6_1">5.6.1</a> above.
</div>
+
+ <div class="ldp-issue">
+ <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/28">ISSUE-28</a></div>
+ transaction/rollback when deleting resources from a LDPC
+ </div>
</section>
@@ -1317,7 +1366,9 @@
Text being repeated in several places centralized and cross-linked. Made printed code output easier to read
on black & white printers. Exposed terms defined in-line under LDPC as Terminology (tentatively). Removed non-normative
qualifer from section 5.2. Added "several" editors' to-dos.(JA)</li>
- <li>2013-01-16 - ISSUE-25 Updated introduction. 5.2.2 changed to MUST NOT be in multiple containers. Flipped 5.6.1/2 as first rule leads to 2nd. 5.6.2(was .1) Delete LDPC MUST also delete members.</li>
+ <li>2013-01-16 - ISSUE-25 Updated introduction. 5.2.2 changed to MUST NOT be in multiple containers. Flipped 5.6.1/2 as
+ first rule leads to 2nd. 5.6.2(was .1) Delete LDPC MUST also delete members. (SS)</li>
+ <li>2013-01-16 - Added new issues ranging from 26-43. Removed closed/deferred issues: 2 & 3 (SS)</li>
</ul></section>
<section class='appendix informative' id="todos">