ISSUE-34: Adding and removing arcs in weak aggregation

aggregation

Adding and removing arcs in weak aggregation

State:

CLOSED

Product:

Linked Data Platform Spec

Raised by:

Richard Cyganiak

Opened on:

2012-11-05

Description:

LDPCs provide a way of managing groups of resources with composition semantics. But it is unclear how to do the same for groups of resources with simple aggregation semantics.

Many resources in a graph have lots of in- or outlinks with the same property: a person's friends, an author's publications, a company's employees, a class's members, a geographical area's contained entities, and so on. This is simple “weak” aggregation—we merely have lots of resources connected to one other via the same property from a domain vocabulary, with no additional LDP-related semantics.

If a node has many arcs, the representation can become way too large, so that PUT becomes impractical as a means of adding and removing arcs from the resource. However, the ability to handle graphs with such resources seems quite important. ISSUE-33 (paging) is one piece of this. How to add and remove arcs is another one.

PATCH, if supported, may be one answer to this; but only if a patch format is specified.

Something that allows adding and removing arcs via POST might be another answer.

Related Actions Items:

• ACTION-23 on Richard Cyganiak to Create a new issue on managing weak aggregation, to subsume ISSUE-7; PATCH might be one way to do it - due 2012-11-09, closed

Related emails:

1. LDP Rec (from eric@w3.org on 2015-02-20)
2. Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior - take #2 (from henry.story@bblfish.net on 2013-04-29)
3. Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior (from henry.story@bblfish.net on 2013-04-20)
4. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
5. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from sspeiche@gmail.com on 2013-04-04)
6. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from henry.story@bblfish.net on 2013-03-19)
7. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from sspeiche@gmail.com on 2013-03-19)
8. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from henry.story@bblfish.net on 2013-03-19)
9. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from lehors@us.ibm.com on 2013-03-19)
10. ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-03-19)
11. Re: Aggregate/Container (from sspeiche@gmail.com on 2013-03-08)
12. Aggregate/Container (from henry.story@bblfish.net on 2013-03-08)
13. Re: The Intuitive/ Requirement (from Roger.Menday@uk.fujitsu.com on 2013-03-07)
14. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-28)
15. Re: Issue-34 Back_to_Basics proposal (from Erik.Wilde@emc.com on 2013-02-28)
16. Re: Issue-34 Back_to_Basics proposal (from roger.menday@uk.fujitsu.com on 2013-02-27)
17. Re: Issue-34 Back_to_Basics proposal (from Roger.Menday@uk.fujitsu.com on 2013-02-27)
18. Re: Issue-34 Back_to_Basics proposal (from ashok.malhotra@oracle.com on 2013-02-22)
19. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-22)
20. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-11)
21. Re: Issue-34 Back_to_Basics proposal (from sergio.fernandez@salzburgresearch.at on 2013-02-11)
22. Re: Issue-34 Back_to_Basics proposal (from roger.menday@uk.fujitsu.com on 2013-02-10)
23. Re: Issue-34 Back_to_Basics proposal (from ashok.malhotra@oracle.com on 2013-02-08)
24. Re: Issue-34 Back_to_Basics proposal (from lehors@us.ibm.com on 2013-02-08)
25. Issue-34 Back_to_Basics proposal (from ashok.malhotra@oracle.com on 2013-02-08)
26. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-08)
27. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-05)
28. Re: Issue-34 Back_to_Basics proposal (from sergio.fernandez@salzburgresearch.at on 2013-02-05)
29. Re: Issue-34 Back_to_Basics proposal (from sergio.fernandez@salzburgresearch.at on 2013-02-05)
30. Re: Issue-34 Back_to_Basics proposal (from henry.story@bblfish.net on 2013-02-04)
31. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
32. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
33. Re: Issue-34 Back_to_Basics proposal (from roger.menday@uk.fujitsu.com on 2013-02-04)
34. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
35. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
36. Re: Issue-34 Back_to_Basics proposal (from roger.menday@uk.fujitsu.com on 2013-02-04)
37. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
38. Re: Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-02-04)
39. Re: Issue-34 Back_to_Basics proposal (from henry.story@bblfish.net on 2013-02-03)
40. Re: Issue-34 Back_to_Basics proposal (from steve.battle@sysemia.co.uk on 2013-02-02)
41. Re: Issue-34 Back_to_Basics proposal (from lehors@us.ibm.com on 2013-02-01)
42. Re: Issue-34 Back_to_Basics proposal (from ashok.malhotra@oracle.com on 2013-02-01)
43. Re: Issue-34 Back_to_Basics proposal (from lehors@us.ibm.com on 2013-02-01)
44. Re: Issue-34 Back_to_Basics proposal (from henry.story@bblfish.net on 2013-02-01)
45. Re: Issue-34 Back_to_Basics proposal (from sspeiche@gmail.com on 2013-02-01)
46. Re: Issue-34 Back_to_Basics proposal (from sspeiche@gmail.com on 2013-02-01)
47. Re: ISSUE-37 WAS:Proposal for containers (from henry.story@bblfish.net on 2013-02-01)
48. Re: Issue-34 Back_to_Basics proposal (from Erik.Wilde@emc.com on 2013-02-01)
49. Issue-34 Back_to_Basics proposal (from johnarwe@us.ibm.com on 2013-01-31)
50. Re: Proposal for containers (from ashok.malhotra@oracle.com on 2013-01-31)
51. Re: Proposal for containers (from henry.story@bblfish.net on 2013-01-31)
52. Re: recursive deletion (Re: Model questions) (from roger.menday@uk.fujitsu.com on 2013-01-29)
53. Re: composition and aggregation (from henry.story@bblfish.net on 2013-01-29)
54. composition and aggregation (from Erik.Wilde@emc.com on 2013-01-29)
55. Re: recursive deletion (Re: Model questions) (from henry.story@bblfish.net on 2013-01-29)
56. Re: recursive deletion (Re: Model questions) (from ashok.malhotra@oracle.com on 2013-01-29)
57. Re: recursive deletion (Re: Model questions) (from eric@w3.org on 2013-01-29)
58. Re: Model questions (from sergio.fernandez@salzburgresearch.at on 2013-01-29)
59. Re: Model questions (from henry.story@bblfish.net on 2013-01-29)
60. recursive deletion (Re: Model questions) (from roger.menday@uk.fujitsu.com on 2013-01-29)
61. Model questions (from ashok.malhotra@oracle.com on 2013-01-28)
62. Re: Interaction model vs data model (from johnarwe@us.ibm.com on 2013-01-25)
63. Re: issue-34 example (from henry.story@bblfish.net on 2013-01-22)
64. Re: issue-34 example (from lehors@us.ibm.com on 2013-01-21)
65. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-21)
66. Re: Feedback on Henry's proposal for ISSUE-34 (from johnarwe@us.ibm.com on 2013-01-21)
67. Re: issue-34 example (from Erik.Wilde@emc.com on 2013-01-21)
68. Re: issue-34 example (from david@3roundstones.com on 2013-01-21)
69. Re: issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-21)
70. Re: issue-34 example (from henry.story@bblfish.net on 2013-01-21)
71. Re: issue-34 example (from Erik.Wilde@emc.com on 2013-01-21)
72. Re: issue-34 example (from johnarwe@us.ibm.com on 2013-01-21)
73. Re: issue-34 example (from Erik.Wilde@emc.com on 2013-01-21)
74. Re: issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-21)
75. Re: issue-34 example (from Erik.Wilde@emc.com on 2013-01-21)
76. Re: issue-34 example (from henry.story@bblfish.net on 2013-01-21)
77. Re: issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-21)
78. Re: issue-34 example (from andy.seaborne@epimorphics.com on 2013-01-20)
79. Re: issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-20)
80. Re: issue-34 example (from andy.seaborne@epimorphics.com on 2013-01-20)
81. Re: Feedback on Henry's proposal for ISSUE-34 (from kidehen@openlinksw.com on 2013-01-20)
82. Re: Feedback on Henry's proposal for ISSUE-34 (from nmihindu@fi.upm.es on 2013-01-20)
83. Re: Feedback on Henry's proposal for ISSUE-34 (from roger.menday@uk.fujitsu.com on 2013-01-20)
84. Re: issue-34 example (from Roger.Menday@uk.fujitsu.com on 2013-01-20)
85. Re: issue-34 example (from henry.story@bblfish.net on 2013-01-20)
86. Re: issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-20)
87. Re: Feedback on Henry's proposal for ISSUE-34 (from nmihindu@fi.upm.es on 2013-01-20)
88. Re: Feedback on Henry's proposal for ISSUE-34 (from nmihindu@fi.upm.es on 2013-01-20)
89. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-20)
90. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-20)
91. Re: Feedback on Henry's proposal for ISSUE-34 (from kidehen@openlinksw.com on 2013-01-19)
92. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-19)
93. Re: Feedback on Henry's proposal for ISSUE-34 (from sspeiche@gmail.com on 2013-01-19)
94. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-19)
95. Re: Feedback on Henry's proposal for ISSUE-34 (from henry.story@bblfish.net on 2013-01-19)
96. Re: Feedback on Henry's proposal for ISSUE-34 (from lehors@us.ibm.com on 2013-01-18)
97. Feedback on Henry's proposal for ISSUE-34 (from sspeiche@gmail.com on 2013-01-18)
98. Re: issue-34 example (from lehors@us.ibm.com on 2013-01-18)
99. Re: issue-34 example (from nmihindu@fi.upm.es on 2013-01-18)
100. Re: issue-34 example (from andy.seaborne@epimorphics.com on 2013-01-18)
101. Re: Aggregation: simple proposal (from henry.story@bblfish.net on 2013-01-18)
102. Re: Aggregation: simple proposal (from henry.story@bblfish.net on 2013-01-18)
103. Re: Aggregation: simple proposal (from nmihindu@fi.upm.es on 2013-01-18)
104. Re: issue-34 example (from lehors@us.ibm.com on 2013-01-17)
105. issue-34 example (from roger.menday@uk.fujitsu.com on 2013-01-17)
106. Re: container/member models (from roger.menday@uk.fujitsu.com on 2013-01-17)
107. Re: container/member models (from lehors@us.ibm.com on 2013-01-17)
108. Re: Aggregation: simple proposal (from henry.story@bblfish.net on 2013-01-16)
109. Approach to spec changes for resolution of ISSUE-25 Weak aggregation and strong composition in containers (from sspeiche@us.ibm.com on 2012-11-19)
110. Re: Can ISSUE-7 be closed? (from andy.seaborne@epimorphics.com on 2012-11-07)
111. Re: (un)blessed container use cases and implementation expectations (from andy.seaborne@epimorphics.com on 2012-11-07)
112. Re: Can ISSUE-7 be closed? (from lehors@us.ibm.com on 2012-11-06)
113. Can ISSUE-7 be closed? (from richard@cyganiak.de on 2012-11-06)
114. Re: (un)blessed container use cases and implementation expectations (from richard@cyganiak.de on 2012-11-06)
115. ldp-ISSUE-34 (aggregation): Adding and removing arcs in weak aggregation [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-05)

Related notes:

Display change log