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

Arnaud, all,

recall that I proposed option D (putting the information in the HTTP header
rather than in the RDF graph) because I thought (and still think) that this
is neither a property of the container of its member, this is a property of
a given representation.

The thought came to me, though, that the problem would be slightly
different if we were talking about the *pages* of said container (because I
don't expect pages to have much variability in their representations...).
So what about applying option A to a page, as in:

# The following is the representation of
#                  http://example.org/netWorth/nw1
# and
#                  http://example.org/netWorth/nw1?firstPage
@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix ldp:      <http://www.w3.org/ns/ldp#>.
@prefix o:       <http://example.org/ontology/>.
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns>.

<nw1?firstPage>
  ldp:pageOf <nw1> ;
  ldp:nextPage rdf:nil ;
  ldp:membersInlined true.

<nw1>
  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.

Of course, option B and C could be derived similarly.

  pa



On Tue, Apr 30, 2013 at 8:51 PM, Arnaud Le Hors <lehors@us.ibm.com> wrote:

>  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
>