## page was renamed from A.2.1. Fedora-typesystem
##Task
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.

= A.2.1. Fedora-typesystem =

## Valid states: "Not started", "In progress" and "Finished"
'''State:''' In progress

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''Time used:''' Not reported

== Description ==

## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.

Fedora is a very flexible system and puts little contraint on the possible kinds of data it can store. This is a good thing, however a system for describing the specific datamodel of an object (it's "type") is desirable, both for documentation and validity and integrity checking.

This task is to define how we describe the type of an object in Fedora in a way that is machine readable. Note that a later task, [[TaskA.4.1]], should implement validity checking using this type system.

We have already done some work on this in the pre-analysis project, this work is described in the analysis document.

##
## == Sub tasks ==
## 
##  * Add sub task link 1 here
##  * Add sub task link 2 here
##  *         ..[[BR]]
##  *         ..[[BR]]
##  *         ..
##  * Add sub task link N here

== Documentation ==

## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page.
## This should be a proper default, however, it may be changed.
 
 * [[TaskA.2.1AnalysisDocument| Analysis Document]]
 * [[TaskA.2.1DesignDocument| Design Document]]
 * [[TaskA.2.1SystemMaintenanceDocument| System Set-up and Maintenance Document]]

== Parent task ==
 * [[TaskA.2]]

== Progress history ==

<<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskA.2.1)>>

A standard of sorts have been made for MiniDOMS, to be found in DataModel. This must be changed to accomedate the introduction of Content Models in Fedora 3.


## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.