Differences between revisions 75 and 76
Revision 75 as of 2008-10-17 13:20:02
Size: 2188
Editor: kfc
Comment:
Revision 76 as of 2008-10-17 16:14:28
Size: 2163
Editor: kfc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:
 * FedoraTransactionsReplacement - Detailing the use of the STATE datastream to allow for some transaction-like processes  * FedoraState - Detailing the use of object states to allow for some transaction-like processes

DON'T PANIC

A definition: A datamodel describes the content of a collection. A content model describes the content of a data object. So, a data model is a set of content models, that together describe the collection.

The DOMS datamodel describes how the Type system underlying DOMS is realised in Fedora 3. The figure above will serve as a guide through the following sections.

The entire DOMS datamodel is, in its entirety, a complex system. For proper understanding, the various components have been detailed in seperate documents. Firstly, it consist of a number of extension to the Fedora system. Secondly, it consist of a number of predefined objects. These objects make use of the extensions to Fedora. Thirdly, it consist of a number of policies for how certain tasks are achived. And fourthly, it consist of a number of API interfaces.

Fedora and DOMS are big on namespaces. To ease writing the documentation, a namespace document, DomsNameSpaces, have been written. All namespaces should be defined there, and all shorthand refer to the namespaces defined therein.

Fedora extensions

Predefined objects

Doms policies

API documentation

  • Refer to the overall [:Documentation:] page

DataModel (last edited 2010-03-17 13:13:00 by localhost)