ISSUE-76: rename the ldp:membershipXXX properties

rename membershipXXX

rename the ldp:membershipXXX properties

State:

CLOSED

Product:

Linked Data Platform Spec

Raised by:

Henry Story

Opened on:

2013-05-29

Description:

The ldp:membershipXXX properties are very weakly connected to rdf:member-ship of an LDPC. It is suggested that this relation be fully disconnected from rdf:member-ship, and renamed to something else. Possible names are:

- ldp:relationship{Property,Subject,Object}
- ldp:relation{Property,Subject,Object}

There would be no default property for these relationships to avoid monotonicity ISSUE-75. As expressed in ISSUE-73: POSTing to a container would just add to the LDPC the rdf:member relation pointing from the LDPC to the created LDPR. A container whose representation listed these relationships be a way for the requesting client to know that POSTing to the container will also have as an effect to add the relationship constructed using the relationshipXX logic to some resource ( and that seems to be in need of clarification)

Related Actions Items:

No related actions

Related emails:

1. Re: Missing use case for supporting ldp:membershipPredicate/Subject (from henry.story@bblfish.net on 2013-05-30)
2. Re: Missing use case for supporting ldp:membershipPredicate/Subject (from sspeiche@gmail.com on 2013-05-29)
3. Re: Missing use case for supporting ldp:membershipPredicate/Subject (from henry.story@bblfish.net on 2013-05-29)
4. ldp-ISSUE-76 (rename membershipXXX): rename the ldp:membershipXXX properties [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-05-29)

Related notes:

Display change log