Last active
December 9, 2015 14:11
-
-
Save elrayle/b62003b432e0722c8c72 to your computer and use it in GitHub Desktop.
ordered_members vs. members and their interactions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # How do ordered_members and members behave and interact | |
| # Setup | |
| col1 = Hydra::Works::Collection.new(id: 'c1') | |
| wrk1 = Hydra::Works::Work.new(id: 'w1') | |
| wrk2 = Hydra::Works::Work.new(id: 'w2') | |
| wrk3 = Hydra::Works::Work.new(id: 'w3') | |
| wrk4 = Hydra::Works::Work.new(id: 'w4') | |
| # 1. adding to members does NOT add to ordered members | |
| col1.members << wrk1 | |
| col1.members.size # => 1 -- w1 | |
| Array(col1.ordered_members).size # => 0 | |
| # 2. adding to ordered_members does add to members | |
| col1.ordered_members << wrk4 | |
| col1.members.size # => 2 -- w1, w4 (order unimportant) | |
| Array(col1.ordered_members).size # => 1 -- w4 | |
| # 3. adding the same object again to ordered_members does NOT add to members | |
| col1.ordered_members << wrk4 | |
| col1.members.size # => 2 -- w1, w4 (order unimportant) | |
| Array(col1.ordered_members).size # => 2 -- w4, w4 (precise order) | |
| # add a few more to work with for deletes | |
| col1.ordered_members << wrk2 | |
| col1.ordered_members << wrk3 | |
| col1.members.size # => 4 -- w1, w2, w3, w4 (order unimportant) | |
| Array(col1.ordered_members).size # => 4 -- w4, w4, w2, w3 (precise order) | |
| # 3. deleting from members does NOT effect ordered_members | |
| col1.members.delete(wrk3) | |
| col1.members.size # => 3 -- w1, w2, w4 (order unimportant) | |
| Array(col1.ordered_members).size # => 4 -- w4, w4, w2, w3 (precise order) | |
| # 4. deleting from ordered_members does NOT effect members | |
| col1.ordered_members.delete_at(2) | |
| col1.members.size # => 3 -- w1, w2, w4 (order unimportant) | |
| Array(col1.ordered_members).size # => 2 -- w4, w4, w3 (precise order) | |
Author
The expectations
members should always be the set view of ordered members
ordered members will have every member of the set members at least once
are flawed, in my view. ORE's strength is that ordering is optional for a given set of aggregated resources and we should leverage that strength in our API. I think a more reasonable expectation is
- ordered_members should always be a subset of members.
Author
Approach 2: set of unique objects in ordered_members is a subset of members
members and ordered_members
Terminology
- members - A set with each member in the set existing only once. Order is unimportant and not guaranteed to be the same for each retrieval.
- ordered_members - An ordered list where the same member may exist in the list multiple times. The order is precise and will be returned in the same order for every retrieval.
General expectation...
- members should always be the set view of ordered members and may have additional members not in ordered_members
- the set of unique ordered_members will be a subset of members
Example:
- ordered_members = A, C, D, C, D --> unique set = A, C, D
- members = A, B, C, D --> has unique set from order_members + B which is only in members
NOTE: You will not see a member in ordered_members that is not in members.
Specific behaviors for add and delete...
Add to members:
- add to members one object with << will NOT append the object to ordered_members
- add to members array of objects with += will NOT append any objects of the array to ordered_members
- set members with = will remove from ordered_members any object that is no longer in members
Add to ordered_members:
- append one object to ordered_members with << will add it to members set iff the object is not already a part of the members set
- append array of objects in order to ordered_members with += will add each object to members set iff the object is not already a part of the members set
- set array of objects in order to ordered_members with = will add each object to members set iff the object was not already added to the members set
Delete from members:
- delete(object) from members also deletes all instances of object from the ordered_members list
Delete from ordered_members:
- delete_at(idx) from ordered_members will NOT delete anything from members
? Are there other delete methods ?
Move object in ordered_members:
? Are there any move methods yet ?
Author
ORE Examples
NOTE: These examples come from a different domain, but are representative of ORE implementation of sets, fully ordered lists, and partially ordered lists.
Example ORE triples for an unordered set
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
<http://localhost:3000/individual/vc255> a ore:Aggregation ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652234> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652543> .
Example ORE triples for a fully ordered list
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
<http://localhost:3000/individual/vc155> a ore:Aggregation ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652234> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652446> .
<http://localhost:3000/individual/vci162> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652730> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:next <http://localhost:3000/individual/vci163> .
<http://localhost:3000/individual/vci163> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652234> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:prev <http://localhost:3000/individual/vci162> ;
iana:next <http://localhost:3000/individual/vci165> .
<http://localhost:3000/individual/vci165> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652446> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:prev <http://localhost:3000/individual/vci163> .
Example ORE triples for a partially ordered list
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
<http://localhost:3000/individual/vc155> a ore:Aggregation ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652730> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652234> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652782> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652446> ;
ore:aggregates <http://da-rdf.library.cornell.edu/individual/b3652543> .
<http://localhost:3000/individual/vci162> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652730> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:next <http://localhost:3000/individual/vci163> .
<http://localhost:3000/individual/vci163> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652234> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:prev <http://localhost:3000/individual/vci162> ;
iana:next <http://localhost:3000/individual/vci165> .
<http://localhost:3000/individual/vci165> a ore:Proxy ;
ore:proxyFor <http://da-rdf.library.cornell.edu/individual/b3652446> ;
ore:proxyIn <http://localhost:3000/individual/vc155> ;
iana:prev <http://localhost:3000/individual/vci163> .
Author
Approach 3: members
members
Terminology
members can be...
- set - A set with each member in the set existing only once. Order is unimportant and not guaranteed to be the same for each retrieval.
- fully ordered list - An ordered list where the same member may exist in the list multiple times. All members have at least one proxy defining their order in the list. Members can repeat by having additional proxies. The order is precise and will be returned in the same order for every retrieval.
- partially ordered list - An list where some members have proxies defining their order and others do not. The same member may exist in the list multiple times by having additional proxies. The order for members with proxies is precise and will be returned in the same order for every retrieval. Unordered members do not guarantee to be returned in the same order for each retrieval.
General expectation...
There is only one data structure and nothing to keep in sync.
- Certain methods add members without order. If only these methods are used, then the aggregation will be a set.
- Certain methods add members with order. If only these methods are used, then the aggregation will be a fully ordered list.
- If a combination of these methods are used, then the aggregation will be a partially ordered list.
The aggregation type is not codified by a triple value, but is a characteristic assessed by the triples that are used for members. An aggregation can change from a set to a partially ordered list by adding member(s) with order. A fully ordered list can be come a partially ordered list by adding member(s) without order.
Specific behaviors for add and delete...
Adding without order:
- members.add(object) - add object without a proxy
- members.add([Array]objects) - add all objects in the array without proxies
Adding with order:
- members.add_at(object,idx) - add object at location idx and insert a proxy between idx-1 and current idx
- members.add_at([Array]objects,idx) - add all objects in the array starting at location idx and insert proxies for each between idx-1 and current idx
- members << object - add object to the end and adding its proxy as the tail
- members += [Array]objects - add all objects to the end and add a proxy for each in order with the last object in the array as the tail
- members = [Array]objects - replace current members with objects and add a proxy for each in order of the array
NOTE: idx can be negative to be relative to the end of the list
Delete:
- members.delete_all(object) - delete all occurrences in members of object updating surrounding proxies of each if any
- members.delete(object,nth) - delete the nth occurrence of object updating surrounding proxies (default nth=1)
NOTE: nth can be negative to be relative to the end of the list
Quick question: if proxies for ordering allow for multiple different orderings of the same members, is that accommodated in the API?
@baxter-brad Multiple orderings in PCDM are handled via extra objects. There's one ordering per pcdm:object
Author
Blend of Approach 2 and 3
Approach 2 could become more intuitive with some adjustments to the API. Currently, it seems like there are two lists (members and ordered_members) being kept for one aggregation. They seem to effect each other in a non-intuitive way. There aren’t actually two lists, but the API treats them in a way that implies they are separate. Trey pointed out in another email that "#ordered_members is a convenience method for returning the proxyFor objects, in order, pointed at from the ordered list.”
A potential change to the API could strengthen the concept that members is a single aggregation. Method changes to support this could be a blend of Approach 2 and 3. Keep the infrastructure currently in place with Approach 2. Change the public methods to be those of Approach 3 where all changes are made to members to effect set operations and ordered list operations. col1.ordered_members would not be a valid call anymore. Instead views into the aggregation as a set or list would be handled by the following methods. NOTE: col1 is an example PCDM:Collection that has aggregation members.
- col1.members.set - returns each unique member which represents the set
- col1.members.ordered - returns only members that have proxies which implies ordering (under the covers, this can still be the code run in the current convenience method ordered_members for returning the proxyFor objects)
- col1.members - by itself returns all members whether they have a proxy or not. This will be a set if no ordering was ever added, a fully ordered list if ordering was always added, or a partially ordered list if some members were added with and some without ordering.
@tpendragon is that actually specified in PCDM?
Author
Actual triples created in Fedora
NOTE: These examples only include triples related to PCDM, ORE, and LDP. Fedora keeps additional triples and each object has additional rdf types that aren't shown here.
Set: Add one work to a collection without order
Code to create set:
col1.members << work1
col1.members << work2
col1.members << work3
Triples in Fedora necessary to represent a set using ORE:
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
<http://localhost:8983/fedora/rest/dev/col-1> a pcdm:Collection ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> .
Triples in Fedora for LDP and ORE: (includes the ORE triples from above)
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
<http://localhost:8983/fedora/rest/dev/col-1> a pcdm:Collection, ldp:Container, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-1/members> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> .
<http://localhost:8983/fedora/rest/dev/col-1/members> a ldp:Container, ldp:IndirectContainer, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-1/members/2aa40a84-8011-4bcd-8167-15f115b55d06> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-1/members/62fc559f-641a-43dc-9951-8425ed690037> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-1/members/9cfcdcdd-ab10-4822-9293-c4e100fc96e8> ;
ldp:hasMemberRelation pcdm:hasMember ;
ldp:insertedContentRelation ore:proxyFor ;
ldp:membershipResource <http://localhost:8983/fedora/rest/dev/col-1> .
<http://localhost:8983/fedora/rest/dev/col-1/members/2aa40a84-8011-4bcd-8167-15f115b55d06> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-2> .
<http://localhost:8983/fedora/rest/dev/col-1/members/62fc559f-641a-43dc-9951-8425ed690037> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-3> .
<http://localhost:8983/fedora/rest/dev/col-1/members/9cfcdcdd-ab10-4822-9293-c4e100fc96e8> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> .
Fully Ordered List: Add three works to a collection with order
Code to create fully ordered list:
col2.ordered_members << work1
col2.ordered_members << work2
col2.ordered_members << work3
Triples in Fedora necessary to represent a fully ordered list using ORE:
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
<http://localhost:8983/fedora/rest/dev/col-2> a pcdm:Collection ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> .
NOTE: Each of the list_source proxies should have an rdf type of ore:proxy. Not sure why they don't.
Triples in Fedora for LDP and ORE: (includes the ORE triples from above)
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
@prefix dct: <http://purl.org/dc/terms/> .
<http://localhost:8983/fedora/rest/dev/col-2> a pcdm:Collection, ldp:Container, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-2/list_source> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-2/members> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> .
<http://localhost:8983/fedora/rest/dev/col-2/members> a ldp:Container, ldp:IndirectContainer, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-2/members/bac2feff-8010-4011-9192-de0a79dd13f7> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-2/members/e148c0f5-3038-4311-b39f-0dc4eb7d783a> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-2/members/fd47fa85-08b4-4b27-86d0-329d7d8bc371> ;
ldp:hasMemberRelation pcdm:hasMember ;
ldp:insertedContentRelation ore:proxyFor ;
ldp:membershipResource <http://localhost:8983/fedora/rest/dev/col-2> .
<http://localhost:8983/fedora/rest/dev/col-2/members/bac2feff-8010-4011-9192-de0a79dd13f7> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> .
<http://localhost:8983/fedora/rest/dev/col-2/members/e148c0f5-3038-4311-b39f-0dc4eb7d783a> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-3> .
<http://localhost:8983/fedora/rest/dev/col-2/members/fd47fa85-08b4-4b27-86d0-329d7d8bc371> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-2> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source> a ldp:Container, ldp:RDFSource ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099634570060> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> .
<http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638308040> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-2> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-2/list_source#g70099638588660> .
Partially Ordered List: Add three works to a collection with order and 3 without order
Code to create partially ordered list:
col3.members << work1
col3.ordered_members << work2
col3.ordered_members << work3
col3.members << work4
col3.ordered_members << work5
col3.members << work6
Triples in Fedora necessary to represent a partially ordered list using ORE:
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
<http://localhost:8983/fedora/rest/dev/col-3> a pcdm:Collection ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-4> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-5> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-6> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-2> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-3> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-5> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> .
NOTE: Each of the list_source proxies should have an rdf type of ore:proxy. Not sure why they don't.
Triples in Fedora for LDP and ORE: (includes the ORE triples from above)
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix pcdm: <http://pcdm.org/models#> .
@prefix ore: <http://www.openarchives.org/ore/terms/> .
@prefix iana: <http://www.iana.org/assignments/relation/> .
@prefix dct: <http://purl.org/dc/terms/> .
<http://localhost:8983/fedora/rest/dev/col-3> a pcdm:Collection, ldp:Container, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/list_source> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-1> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-2> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-3> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-4> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-5> ;
pcdm:hasMember <http://localhost:8983/fedora/rest/dev/work-6> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> .
<http://localhost:8983/fedora/rest/dev/col-3/members> a ldp:Container, ldp:IndirectContainer, ldp:RDFSource ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/b362baa2-f803-4c6b-b8e8-44a25d64ea71> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/be70870b-54c1-4632-8347-d685ec756d44> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/c845ffbd-cdc3-42ca-8334-6f61cc20b9c3> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/d74e2ea1-dd0d-48b9-a5d7-942d732fc06b> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/e0ffc9a7-8934-4ce0-995f-a9ac8d93f554> ;
ldp:contains <http://localhost:8983/fedora/rest/dev/col-3/members/e1bf5600-860d-47cb-bad4-0326a9376c0a> ;
ldp:hasMemberRelation pcdm:hasMember ;
ldp:insertedContentRelation ore:proxyFor ;
ldp:membershipResource <http://localhost:8983/fedora/rest/dev/col-3> .
<http://localhost:8983/fedora/rest/dev/col-3/members/b362baa2-f803-4c6b-b8e8-44a25d64ea71> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-1> .
<http://localhost:8983/fedora/rest/dev/col-3/members/be70870b-54c1-4632-8347-d685ec756d44> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-3> .
<http://localhost:8983/fedora/rest/dev/col-3/members/c845ffbd-cdc3-42ca-8334-6f61cc20b9c3> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-2> .
<http://localhost:8983/fedora/rest/dev/col-3/members/d74e2ea1-dd0d-48b9-a5d7-942d732fc06b> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-4> .
<http://localhost:8983/fedora/rest/dev/col-3/members/e0ffc9a7-8934-4ce0-995f-a9ac8d93f554> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-6> .
<http://localhost:8983/fedora/rest/dev/col-3/members/e1bf5600-860d-47cb-bad4-0326a9376c0a> a ore:Proxy, ldp:Container, ldp:RDFSource ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-5> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source> a ldp:Container, ldp:RDFSource ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> ;
dct:hasPart <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:first <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:last <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-2> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-3> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159014522900> ;
iana:next <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> .
<http://localhost:8983/fedora/rest/dev/col-3/list_source#g70158983424840> a ;
ore:proxyFor <http://localhost:8983/fedora/rest/dev/work-5> ;
ore:proxyIn <http://localhost:8983/fedora/rest/dev/col-3> ;
iana:prev <http://localhost:8983/fedora/rest/dev/col-3/list_source#g70159013851360> .
Author
The set of triples that are being generated in Fedora do not appear to match the concept of Resource Map described in the ORE spec. If you see this differently, can you explain how you understand this implementation to match ORE Resource Maps?
What is a use case for a partial_ordered list?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NOTE: This approach will NOT be adopted.
Approach 1: members and ordered_members stay in sync
members and ordered_members
Terminology
General expectation...
Specific behaviors for add and delete...
Add to members:
Add to ordered_members:
Delete from members:
Delete from ordered_members: