ISSUE-14: Include clarifications about ordering in BPC representations

Arnaud's option A

---------
1. remove the two types of container AggregateContainer and
CompositeContainter, leaving the only kind of container to be
ldp:Container

2. specify that on deleting a container LDP servers MUST delete the
container and MAY delete member resources (typically to satisfy internal
requirements).

So if I have:

<> a ldp:Container;
rdfs:member <a>.

and I create <b> using POST to the container, I end up with:

<> a ldp:Container;
rdfs:member <a>, <b>.

When I delete the container, the container gets deleted, and <a> and <b>
MAY get deleted.

3. Defer adding an operation that let's a client request a recursive
delete to a future version of LDP, and do one of the following:
---------


option B
---------

1. remove the two types of container AggregateContainer and
CompositeContainter, leaving the only kind of container to be
ldp:Container

2. add that on creating a new member resource using POST, LDP servers
SHOULD add a triple a la : <> ldp:contains <newly_created_resource> if the
resource will be deleted when the container is deleted. Note that this is
in addition to adding the appropriate ldp:membershipPredicate or
ldp:membershipPredicateInverse triple to the container representation as
currently required.

3. specify that on deleting a container LDP servers MUST delete the
container and member resources listed as contained via ldp:contains, and
MAY delete other member resources (typically to satisfy internal
requirements).

So if I have:

<> a ldp:Container;
rdfs:member <a>.

and I create <b> using POST to the container, I end up with:

<> a ldp:Container;
rdfs:member <a>, <b>;
ldp:contains <b>.

When I delete the container, both the container and <b> get deleted. <a>
MAY be deleted.

4. Defer adding an operation that let's a client request a recursive
delete to a future version of LDP:
-------------

Resolution: Close ISSUE-14, saying an LDPC server can indicate to a client the ordering of members in a container page using an ldp:containerOrder property. This property has as range a list of resources with two properties: (a) ldp:containerSortPredicate, which defines the property used for sorting; (b) ldp:containerSortOrder, which defines the ordering (ascending or descending) and is optional, (c, etc.) collation, and others.
See https://www.w3.org/2013/meeting/ldp/2013-05-06#resolution_2