...
Implementation Proposal:
The Fedora 4 repository if nothing else relies heavily on metadata to describe and manage its digital content. There is a large intersection between the types of data Fedora uses in its implementation to manage data and the PREMIS standard for metadata that supports information necessary in the description of preserved digital objects. In fact Fedora currently relies on PREMIS to describe content nodes such as the properties premis:hasContentLocaiton and premis:hasSize.
The Fedora 4 repository also is build built based on the intersection of several structural concepts. There is the legacy Fedora construction of objects and datastreams adhering to a content model definitions. There is the fedora 4 ontological description of abstract resources taking the form of objects, datastreams and content. There is the modeshape node type definitions extending a base nodetype into file and folder primary types that can be extended by the addition of mixins. The PREMIS 2.2 is structured similarly, defining abstractly intellectual entities in the form of objects classified as representations, files, and bitstreams. Given these similarities, Fedora is well situated to borrow many of the concepts defined in PREMIS in particular PREMIS's definition of an event ontology to capture actions taken on objects preserved in the repository.
...