That's very true, and your example is enlightening. In that case, I would reach for the (as-yet-unavailable) blank node, and develop something like:
Slide hasNext _1. _1 hasValue NextSlide1. _1 hasContext FirstPresentationVersion. and Slide hasNext _2. _2 hasValue NextSlide2. _2 hasContext OtherPresentationVersion. I don't think there's any question that the object graph can evidence either point of view, but not under the current limitation. I understand that work is getting underway to use named graphs to break this barrier? --- A. Soroka Digital Research and Scholarship R & D the University of Virginia Library On May 19, 2010, at 4:17 PM, Steve Bayliss wrote: > Maybe a better example would be a presentation composed of a number of > slides. After creating the first version, I create another version with the > slides unchanged but in a different order. In this case I think there's a > good argument for modelling order as the order of the relationships from the > slides to the version rather than treating order as a property of the > individual slides. ------------------------------------------------------------------------------ _______________________________________________ Fedora-commons-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
