OAI-ORE: Object Reuse and Exchange(From PeteJohnston)
It's probably not a perfect analogy with the ORE Proxy notion but it's close, I think e.g.
- (Aggregated Resource) Photo P1000284
- (Aggregation) EF Photostream
- (Aggregation) Set efsym2008
- (Proxy) Photo P100284 in EF Photostream
5. (Proxy) Photo P100284 in Set efsym2008
And the representations of (1) & (4) are the same. But the representation of (5) is slightly different. For (1) & (4) the right-hand column shows it as a member of EF's photostream and it "also belongs to" the efsym2008 set. For (5) the right hand colum shows the efsym2008 set highlighted as the "current" set, and the "photostream" thumbnail navigator is "closed" by default.
And the "next image in set" links in the thumbnail navigator use the "Proxy" URI, because sequencing is specific to the set/Aggregation.
So Flickr provides URIs which allow me to refer to a photo "in the context of" a specific set, which is what we wanted for Aggregated Resources in ORE.
One of the consequences (and you see this sometimes when people cite Flickr pics) is that often people really do just want to cite the photo (regardless of in-set "context") but person X uses URI (1), person Y uses URI (4) and person Z uses URI (5) (probably based on copying from the browser address, after having navigated to it by different paths) (Unless like me, they are aware of it and now always "edit down" to a "non-Proxy" URI!)