Re: On ISSUE-58: Property for asserting that complete description of members is included in LDPC representation

My preference would be for option D (I was convinced by Pierre-Antoine's argumentation a few weeks ago). 

But, I don't see why the language has to be so container specific. 
For me this is one of those features where LDP is helping with reading of any kind of Linked Data.

regards, 
Roger


> Looking back at what has been said on this issue, I see several possible paths forward: 
> 
> Option A: Richard's original proposal (without all the details): 
> 
> Add to ldp:Container a boolean property which, when true, indicates that a complete description of all the members is inlined in the container document. 
> 
> Option B: 
> 
> Add to ldp:Container a property ldp:memberInlined which indicates the members for which a complete description is inlined in the container document. 
> 
> Option C: 
> 
> Add a boolean property ldp:memberInlined which, when true, indicates that a complete description of that member is inlined in the container document. 
> 
> Option D: 
> 
> Add a repeatable HTTP Header, such as X-Cacheable-for, which when set to a member URI means that a complete description of that member is inlined in the container document. 
> 
> 
> Here are some examples for each options: 
> 
> Option A: 
> 
> # The following is the representation of
> #                  http://example.org/netWorth/nw1
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp:      <http://www.w3.org/ns/ldp#>.
> @prefix o:       <http://example.org/ontology/>.
> 
> <>
>   a o:NetWorth, ldp:Container;
>   ldp:membershipPredicate o:asset;
>   o:asset <a1>, <a2>; 
>    ldp:membersInlined true.
> 
> <a1>
>    a o:Stock;
>    o:value 10000.
> <a2>
>    a o:Bond;
>    o:value 20000. 
> 
> 
> Option B: 
> 
> # The following is the representation of
> #                  http://example.org/netWorth/nw1
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp:      <http://www.w3.org/ns/ldp#>.
> @prefix o:       <http://example.org/ontology/>.
> 
> <>
>   a o:NetWorth, ldp:Container;
>   ldp:membershipPredicate o:asset;
>   o:asset <a1>, <a2>; 
>    ldp:memberInlined <a1>, <a2>.
> 
> <a1>
>    a o:Stock;
>    o:value 10000.
> <a2>
>    a o:Bond;
>    o:value 20000. 
> 
> Option C: 
> 
> # The following is the representation of
> #                  http://example.org/netWorth/nw1
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp:      <http://www.w3.org/ns/ldp#>.
> @prefix o:       <http://example.org/ontology/>.
> 
> <>
>   a o:NetWorth, ldp:Container;
>   ldp:membershipPredicate o:asset;
>   o:asset <a1>, <a2>.
> 
> <a1>
>    a o:Stock;
>    o:value 10000; 
>    ldp:memberInlined true.
> <a2>
>    a o:Bond;
>    o:value 20000; 
>    ldp:memberInlined true. 
> 
> Option D: 
> 
> # The following is the representation of
> #                  http://example.org/netWorth/nw1
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp:      <http://www.w3.org/ns/ldp#>.
> @prefix o:       <http://example.org/ontology/>.
> 
> <>
>   a o:NetWorth, ldp:Container;
>   ldp:membershipPredicate o:asset;
>   o:asset <a1>, <a2>.
> 
> <a1>
>    a o:Stock;
>    o:value 10000.
> <a2>
>    a o:Bond;
>    o:value 20000. 
> 
> HTTP Headers: 
> X-Cacheable-for: http://example.org/netWorth/nw1/a1 
> X-Cacheable-for: http://example.org/netWorth/nw1/a2 
> 
> Comments anyone? 
> --
> Arnaud  Le Hors - Software Standards Architect - IBM Software Group