W3C home > Mailing lists > Public > public-ldp@w3.org > October 2015

managing multiple relationships with the same membership-constant-URI

From: Daniel Lamb <daniel@discoverygarden.ca>
Date: Fri, 16 Oct 2015 11:49:42 -0300
Message-Id: <D12E4667-3B58-46B7-AEB8-AA5C9C7EC69C@discoverygarden.ca>
To: public-ldp@w3.org
I知 attempting to manage a relationship and its inverse on an LDP server, and started by using a using a direct container that has triples for both ldp:hasMemberRelation and ldp:isMemberOfRelation.  The LDP implementation I知 working with allows this, and some unofficial sources on the internet also support this practice.  Upon reading the spec, however, it seems that this not the way to go.

Section States:

Each LDP Direct Container representation MUST contain exactly one triple whose subject is the LDPC URI, and whose predicate is either ldp:hasMemberRelation or ldp:isMemberOfRelation. The object of the triple is constrained by other sections, such as ldp:hasMemberRelation or ldp:isMemberOfRelation, based on the membership triple pattern used by the container.

Given the conflicting information I知 reading, and what the software I知 working with allows me to do, I知 confused as how to proceed.  What is the best practice for managing multiple relationships with the same membership-constant-URI?  Should I maintain a separate container per relationship?

If so, I assume I should report this back to the maintainers of the LDP server I知 using?

Any help is greatly appreciated.

Received on Friday, 16 October 2015 20:26:47 UTC

This archive was generated by hypermail 2.3.1 : Friday, 16 October 2015 20:26:47 UTC