Re: managing multiple relationships with the same membership-constant-URI

Hi Daniel,

Answers inlined below

On Fri, Oct 16, 2015 at 7:49 AM, Daniel Lamb <daniel@discoverygarden.ca>
wrote:

> I’m 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’m 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 5.4.1.4 States:
>
> Each LDP Direct Container
> <http://www.w3.org/TR/ldp/#dfn-linked-data-platform-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
> <http://www.w3.org/TR/ldp/#ldpdc-containtriple-relation> or
> ldp:isMemberOfRelation
> <http://www.w3.org/TR/ldp/#ldpdc-containtriple-byrelation>, based on the membership
> triple <http://www.w3.org/TR/ldp/#dfn-membership-triples> pattern used by
> the container.
>
> Given the conflicting information I’m reading, and what the software I’m
> working with allows me to do, I’m 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?
>
Do you intend to have a combination of membership triples? Some with
ldp:hasMemberRelation and others with ldp:isMemberOfRelation?
If they are the same, then I would use only one as the spec defines and
simply use an inference rule:
   (*isMembershipPredicate* owl:inverseOf *memberOfPredicate*)

If they are different, I'd used use separate containers.


> If so, I assume I should report this back to the maintainers of the LDP
> server I’m using?
>
I'd recommend reporting it. It might be good to see what their LDP Test
Suite compliance report looks like. It appears this case is covered:
http://w3c.github.io/ldp-testsuite/manifest/

Regards,
Steve Speicher



>
> Any help is greatly appreciated.
>
> ~Danny
>
>
>
>
>