Content Model discussion from 31/8-06

We envision a hierarchy of content models - on top we define the SB content model, that defines datastreams, relations and disseminators we might expect on any object.

Subtypes include a FILE content model, that defines further things we might

The definition work seems to suggest we have some further internal content models: RIGHTS, ADMINISTRATIVE, FILETYPEDEFINITION, OBJECTTYPEDEFINITION - also subtypes of SB

Apart from that, each inidividual project defines it's own SUBTYPES.

CMODEL - SB

Dublin Core

Datastreams

Relations

Disseminators

Note the above are to be defined by the individual objects - so for instance an image file object would give the actual image (possibly scaled) in IMAGE_PRESENTATION, while an object representing a CD album might have a cover it can give as representation.

We expect to cache the result of calls to these disseminators.

Note that VIDEO/SOUND/TEXT_PRESENTATION(0, MaxInt) will give the entire stream, while IMAGE_PRESENTATION(maxInt,maxInt) will give the entire image.

IMAGE_PRESENTATION(64,64) might be used for thumbnails.

This gives a unified representation of this object for indexing purposes. It's supposed to return only something on indexable objects, but in those cases it will return information that might be extracted from an entire graph of objects. For instance a CD might collect information about all tracks from sub-objects.

CMODEL - FILE

Dublin Core

Datastreams

Relations

Note there is not a relation to the logical object - any logical object is expected to point to this.

CMODEL - IMAGE

Relations

CMODEL - AUDIO

Relations

CMODEL - VIDEO

Relations

CMODEL - TEXT

Relations

DOMS Content Model (last edited 2010-03-17 13:09:09 by localhost)