2013-02-25 WG resolution on introspection
authorJohn Arwe
Mon, 25 Feb 2013 12:21:15 -0500
changeset 68 2160e1811b59
parent 67 adb1df6c5074
child 69 0f9825dea52b
2013-02-25 WG resolution on introspection
ldp.html
ldp.ttl
--- a/ldp.html	Fri Feb 22 12:03:44 2013 -0500
+++ b/ldp.html	Mon Feb 25 12:21:15 2013 -0500
@@ -1146,19 +1146,25 @@
 		only when a LDPC supports that method.  This specification does not impose any
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
-	<div id="ldpc-5_6_1" class="rule">5.6.1 When a LDPC member resource originally created by the LDPC (for example one referenced by
+	<div id="ldpc-5_6_1" class="rule">5.6.1 When a LDPC member resource originally created by the LDPC (for example, one referenced by
 		a membership triple) is deleted, and the LDPC server is aware of the member's deletion
 		(for example, the member is managed by the same server), the LDPC server MUST also remove it from
 		the LDPC by removing the corresponding membership triple.
 	</div>	
-	<div id="ldpc-5_6_2" class="rule">5.6.2 If a LDPC server supports deletion of the LDPC, the server MAY also
-		delete the resources that are referenced as its contents.  The LDPC membership triple MUST also be updated as defined
-		by <a href="#ldpc-5_6_1">5.6.1</a> above.
+	<div id="ldpc-5_6_2" class="rule">5.6.2 If a LDPC server supports deletion of the LDPC, 
+		and the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:AggregateContainer</code>,
+		the server MAY also delete the resources that are referenced as its contents.  
+		The LDPC membership triple MUST also be updated as defined by <a href="#ldpc-5_6_1">5.6.1</a> above.
+	</div>
+	<div id="ldpc-5_6_3" class="rule">5.6.3 If a LDPC server supports deletion of the LDPC, 
+		and the LDPC includes an <code>rdf:type</code> predicate with an object of <code>ldp:CompositeContainer</code>,
+		the server MUST also delete the resources that are referenced as its contents.  
+		The LDPC membership 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/34">ISSUE-34</a></div>
-	Aggregration: 2013-02-11 WG Resolution - 5.6.1 and 5.6.2 updated for review.
+	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">
--- a/ldp.ttl	Fri Feb 22 12:03:44 2013 -0500
+++ b/ldp.ttl	Mon Feb 25 12:21:15 2013 -0500
@@ -26,30 +26,38 @@
     a rdfs:Class;
 	rdfs:subClassOf :Resource;
 	rdfs:comment "A Linked Data Platform Resource (LDPR) that also conforms to 
-	additional patterns and conventions for managing membership.";
+	additional patterns and conventions for managing membership.
+	Readers should refer to the specification defining this ontology for the list of 
+	behaviors associated with it.";
 	vs:term_status "unstable";
 	rdfs:isDefinedBy :;
 	rdfs:label "Container".
 	
-:Aggregation
+:AggregateContainer
     a rdfs:Class;
 	rdfs:subClassOf :Container;
 	rdfs:comment "A Linked Data Platform Container (LDPC) that also conforms to 
-	additional patterns and conventions for managing members, for example its 
-	members may continue to exist after its deletion.";
+	additional patterns and conventions for managing members.  It is distinguished from
+	CompositeContainer by the following behaviors; while every attempt is made to be
+	complete in this list, readers should also refer to the specification defining this ontology.
+	(1) Clients cannot assume that an AggregateContainer, when deleted, deletes its members.
+	";
 	vs:term_status "unstable";
 	rdfs:isDefinedBy :;
-	rdfs:label "Aggregation".
+	rdfs:label "AggregateContainer".
 	
-:Composition
+:CompositeContainer
     a rdfs:Class;
 	rdfs:subClassOf :Container;
 	rdfs:comment "A Linked Data Platform Container (LDPC) that also conforms to 
-	additional patterns and conventions for managing members, for example its 
-	members are deleted as part of its deletion.";
+	additional patterns and conventions for managing members.  It is distinguished from
+	AggregateContainer by the following behaviors; while every attempt is made to be
+	complete in this list, readers should also refer to the specification defining this ontology.
+	(1) An CompositeContainer, when deleted, must delete all its members.
+	";
 	vs:term_status "unstable";
 	rdfs:isDefinedBy :;
-	rdfs:label "Composition".
+	rdfs:label "CompositeContainer".
 	
 :containerSortPredicates
  	a rdf:Property;