ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec]

ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec]

http://www.w3.org/2012/ldp/track/issues/89

Raised by: Alexandre Bertails
On product: Linked Data Platform Spec

Proposal: make `ldp:xyz` mandatory.

`ldp:xyz` as a URI is left open for discussion, this issue is about the requirements and the invariants for the needed feature.

This proposal has *no intention* to mix with the notion of membership as defined by the specification at the time I created this issue.

The idea for `ldp:xyz` is to answer the question of what resources are *managed* by an LDPC (it's not about membership). *Being managed* is defined by any successful REST interaction (with side-effects) with an LDPC/LDPR, eg. creation through POST on LDPC or deletion through DELETE on LDPR.

Corollary: the presence/absence of `ldp:xyz` triples is directly derived from the REST interactions. And they entail the possible interactions.

Note: the membership relations can be derived from an LDP model having `ldp:xyz` at its heart, as showed by Henry at http://www.w3.org/2012/ldp/wiki/Issue-88#make_ldp:member_mandatory (where Henry uses `ldp:member` instead of `ldp:xyz`).

Received on Monday, 18 November 2013 16:19:51 UTC