W3C home > Mailing lists > Public > public-ldp-wg@w3.org > April 2013

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

From: Arnaud Le Hors <lehors@us.ibm.com>
Date: Tue, 30 Apr 2013 11:51:30 -0700
To: public-ldp-wg@w3.org
Message-ID: <OFCEE7DE1B.12E3BF8B-ON88257B5D.005F8D66-88257B5D.006797EA@us.ibm.com>
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
Received on Tuesday, 30 April 2013 18:52:02 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2013 13:44:31 UTC