- From: Roger Menday <roger.menday@uk.fujitsu.com>
- Date: Fri, 9 May 2014 10:51:11 +0100
- To: Nandana Mihindukulasooriya <nmihindu@fi.upm.es>
- CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
- Message-ID: <90AB46BF-5C9D-48B8-99BE-B023D3847A6F@uk.fujitsu.com>
hi Nandana, It's an interesting point. Especially the line you have highlighted: "allows members to be any resources, not only documents". I'm looking forward to getting some perspective on that - especially from the spec authors. regards, Roger On 8 May 2014, at 11:36, Nandana Mihindukulasooriya wrote: > Hi, > > In the LDP spec, one form of a membership triple can be as following. > > (membership-constant-URI, membership-predicate, member-derived-URI) > > In this case, what we call the 'member-derived-URI' resource is the member, isn't it ? I am not sure the name of the 'membership-constant-URI' resource but it is not the member, I assume. > > The definition of the LDP-DC says, > An LDPC that adds the concept of membership, allowing the flexibility of choosing what form its membership triples take, and allows members to be any resources, not only documents. > > LDP-DC allows membership-constant-URI to be any resource but the member-derived-URI (or member) will always be the created document. So I am not sure whether the latter part of the definition is correct but that depends on the answer to the first question. > > I assume the answer should be yes, because the definition of the LDP-IC says > An LDPC similar to a LDP-DC that is also capable of having members whose URIs are based on the content of its contained documents rather than the URIs assigned to those documents. > > Best Regards, > Nandana
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Friday, 9 May 2014 09:51:40 UTC