Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

I take this further and suggest that the "Domain aspect" of this model (I.E. Communities/Collections/Items/Manifestations...) should be an abstraction modeled within the data and note expressed as a Concrete set of Java Classes. This means that a DSpaceObject is just a URI used to reference a resources that may be stored in various different states within each service. For example: an Assetstore will store the Content representation of a DSpaceObject, while the MetadataService will store a Metadata representation of the object. This means that Service can evolve seperate "non-dominant" data models that are more tailored to interacting with them. --Mark Diggory 15:49, 16 September 2008 (EDT)