--- a/ldp.html Mon Mar 04 08:30:30 2013 -0500
+++ b/ldp.html Mon Mar 04 08:40:31 2013 -0500
@@ -957,10 +957,6 @@
</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>
@@ -1080,7 +1076,8 @@
creation of any kind of resource, for example binary resources.
</div>
<div id="ldpc-5_4_4" class="rule">5.4.4 For servers that support create, LDPC servers MUST create a LDPR from a
- RDF representation in the request entity body.
+ RDF representation in the request entity body. The LDPR could also be a LDPC, therefore servers may
+ allow the creations of LDPCs within a LDPC.
</div>
<div id="ldpc-5_4_5" class="rule">5.4.5 LDPC servers SHOULD NOT include the representation of the created
resource in the entity body of a 201 (Created) response. In other
@@ -1168,11 +1165,6 @@
</div>
<div class="ldp-issue">
- <div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/34">ISSUE-34</a></div>
- Aggregration: 2013-02-11+25 WG Resolutions - 5.6.1 and 5.6.2 updated, 5.6.3 added, for review.
- </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.
note also that 5.6.2's reminder about 5.6.1 is only sensible if there is no transactional behavior in the recursive delete.
@@ -1222,6 +1214,7 @@
<h1>Change History</h1>
<blockquote><em>First Public Working Draft</em></blockquote>
<ul>
+ <li>2013-03-04 - ISSUE-36 - Added informative text regarding creationg of containers in 5.4.4 (SS)</li>
<li>2013-03-04 - ISSUE-12 - Added section 4.7.3 not to allow PATCH for create (SS)</li>
<li>2013-03-03 - Adjustments to language about different container behavior (SS)</li>
<li>2013-03-02 - Adding trailing '/' on Container URLs to help with readability based on WG suggestion (SS)</li>