re: DSpace History System: RDF Schema Design

Implications of versioning relationships (as opposed to versioning properties)

The example on page 13 of the current draft models changes to a property of, 
for example, a DSpace Item.

This works nicely by introducing "Revision Instances" of the item.

Does this approach also work when relationships change?  For example, how 
would the following use case be modelled:

  "Remove Bitstream hdl:1234/345 from Bundle hdl:1234/234"
  "Add Bistream hdl:1234/567 to Bundle hdl:1234/234"

This would imply removal of one hasPart relationship, and addition of another.

But currently those relationships are made between the objects 
representing "universal" facets of the artifact.

I'm not sure whether or not there is an issue here.  An example of this nature 
would probably help to clarify things.

- Mick

Received on Friday, 30 May 2003 10:22:58 UTC