ISSUE-89: Tie the interaction model with the LDP data model through the notion of Managed Resources

Managed Resources

Tie the interaction model with the LDP data model through the notion of Managed Resources

State:

CLOSED

Product:

Linked Data Platform Spec

Raised by:

Alexandre Bertails

Opened on:

2013-11-18

Description:

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`).

Related Actions Items:

No related actions

Related emails:

1. Re: limits on HTTP Prefer Request Header in [ISSUE-89] resolution (from johnarwe@us.ibm.com on 2014-01-27)
2. limits on HTTP Prefer Request Header in [ISSUE-89] resolution (from tthibodeau@openlinksw.com on 2014-01-27)
3. Re: Getting to closure on the remaining issues (from bertails@w3.org on 2014-01-23)
4. Re: Networth example with ldp:contains (from henry.story@bblfish.net on 2014-01-15)
5. Re: Networth example with ldp:contains (from bertails@w3.org on 2014-01-15)
6. Re: Networth example with ldp:contains (from henry.story@bblfish.net on 2014-01-15)
7. Re: issue-89 proposals (from johnarwe@us.ibm.com on 2014-01-07)
8. Re: issue-89 proposals (from bertails@w3.org on 2014-01-06)
9. Re: issue-89 proposals (from bertails@w3.org on 2014-01-06)
10. Re: issue-89 proposals (from bertails@w3.org on 2014-01-06)
11. Re: issue-89 proposals (from johnarwe@us.ibm.com on 2013-12-18)
12. Re: issue-89 proposals (from bertails@w3.org on 2013-12-16)
13. issue-89 proposals (from johnarwe@us.ibm.com on 2013-12-16)
14. Re: issue 90 proposals (from bertails@w3.org on 2013-12-16)
15. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from sspeiche@gmail.com on 2013-12-15)
16. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-14)
17. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-13)
18. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from sspeiche@gmail.com on 2013-12-13)
19. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from lehors@us.ibm.com on 2013-12-13)
20. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-13)
21. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from lehors@us.ibm.com on 2013-12-13)
22. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-13)
23. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from lehors@us.ibm.com on 2013-12-13)
24. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from roger.menday@uk.fujitsu.com on 2013-12-13)
25. Re: ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from bertails@w3.org on 2013-12-13)
26. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-12)
27. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from sspeiche@gmail.com on 2013-12-12)
28. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-12)
29. Re: Issue-89, proposal 3: Duplication of triples & inferencing (from lehors@us.ibm.com on 2013-12-12)
30. Issue-89, proposal 3: Duplication of triples & inferencing (from henry.story@bblfish.net on 2013-12-12)
31. Re: ISSUE-89 - proposal 3 - propertiesOnlyResource (from henry.story@bblfish.net on 2013-12-10)
32. ISSUE-89 - proposal 3 - propertiesOnlyResource (from henry.story@bblfish.net on 2013-12-10)
33. LDP Agenda for 9 December (from lehors@us.ibm.com on 2013-12-06)
34. Re: ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from henry.story@bblfish.net on 2013-12-06)
35. Re: About the ldp:xyz relationship (from henry.story@bblfish.net on 2013-12-06)
36. Re: About the ldp:xyz relationship (from henry.story@bblfish.net on 2013-12-06)
37. Re: ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from lehors@us.ibm.com on 2013-12-05)
38. Re: ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from bertails@w3.org on 2013-12-05)
39. Re: ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from lehors@us.ibm.com on 2013-12-05)
40. Re: About the ldp:xyz relationship (from bertails@w3.org on 2013-12-05)
41. ACTION-115 / ACTION-116 (proposing text for ISSUE-89 and ISSUE-90) (from bertails@w3.org on 2013-12-05)
42. Re: About the ldp:xyz relationship (from henry.story@bblfish.net on 2013-12-05)
43. About the ldp:xyz relationship (from lehors@us.ibm.com on 2013-12-04)
44. Re: What does "being a member" mean? (from henry.story@bblfish.net on 2013-11-23)
45. Re: What does "being a member" mean? (from eric@w3.org on 2013-11-23)
46. Re: What does "being a member" mean? (from henry.story@bblfish.net on 2013-11-23)
47. Re: What does "being a member" mean? (from eric@w3.org on 2013-11-23)
48. Re: Another approach to containers (from henry.story@bblfish.net on 2013-11-23)
49. Re: What does "being a member" mean? (from henry.story@bblfish.net on 2013-11-23)
50. Another approach to containers (from lehors@us.ibm.com on 2013-11-22)
51. Re: What does "being a member" mean? (from bertails@w3.org on 2013-11-22)
52. Re: What does "being a member" mean? (from ashok.malhotra@oracle.com on 2013-11-22)
53. Re: What does "being a member" mean? (from henry.story@bblfish.net on 2013-11-22)
54. Re: What does "being a member" mean? (from eric@w3.org on 2013-11-22)
55. Re: What does "being a member" mean? (from lehors@us.ibm.com on 2013-11-21)
56. Re: ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec] (from henry.story@bblfish.net on 2013-11-20)
57. Re: ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec] (from bertails@w3.org on 2013-11-18)
58. Re: ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec] (from sspeiche@gmail.com on 2013-11-18)
59. Re: ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec] (from henry.story@bblfish.net on 2013-11-18)
60. ldp-ISSUE-89 (ldp:xyz): Tie the interaction model with the LDP data model through the notion of Managed Resources [Linked Data Platform Spec] (from sysbot+tracker@w3.org on 2013-11-18)

Related notes:

Display change log