Triples in the Resource Index
The resource index stores system and user-controlled metadata about each object in the repository in the form of RDF triples. The number and type of triples stored depends on the content of the object. This document describes the triples that may exist in the resource index for a given object. The color of each row indicates how many of each kind of RDF triple can be expected. See the key on the right. |
|
Namespaces Used
For brevity, the URIs used in this document are shown in abbreviated form. To determine the unabbreviated form of any such URI, replace the Prefix with the associated Namespace URI below.
info:fedora/fedora-system:def/model# |
|
info:fedora/fedora-system:def/view# |
|
|
Breakdown
Base Triples
The following triples will exist for any object, irrespective of its Datastream content.
fedora-view:lastModifiedDate |
|
fedora-model:Active
fedora-model:Inactive
fedora-model:Deleted |
|
|
Dublin Core Triples
Every object in Fedora has a Dublin Core ("DC") Datastream. The following triples are derived from its content, which may consist of any number of each of the 15 unqualified Dublin Core elements. If unprovided at ingest, the DC Datastream will be automatically created with minimal information (a dc:title and a dc:identifier).
RELS-EXT and RELS-INT Triples
(any non-reserved predicate) |
|
|
Content Model Architecture Triples
Note: If not explicitly provided the Fedora Repository will assume there is a fedora-model:hasModel
relation asserted from a Data Object to a system-supplied base CModel Object satisfying the cardinality constraint. This relation should be explicitly stated in the REL-EXT Datastream as a recommended practice. Also note that, while CModel, SDef, and SDep objects may be created without asserting their respective relations, they will not perform their functions without them.
Note: In Fedora 3.0, though permitted, it is not recommended that one SDep object be used to deploy a service for more than one CModel-SDef pair. Future versions of Fedora are likely to provide better support for this configuration.
fedora-model:isDeploymentOf |
|
fedora-model:isContractorOf |
|
|
Datastream Triples
fedora-view:disseminationType |
|
fedora-view:lastModifiedDate |
|
fedora-model:Active
fedora-model:Inactive
fedora-model:Deleted |
|
(true if R or E, false if M or X) |
|
|
Calculating Triples/Object
You can use the following table to estimate the number of triples for each kind of object in your Fedora repository.
Every object automatically gets the following triples:
- Base: 6
- Dublin Core (dc:title and dc:identifier): 2
- Content Model Architecture (fedora-model:hasContentModel): 1
- Datastream Triples (for DC): 6
|
|
If the DC datastream has any elements besides the standard dc:title and dc:identifier, add 1 for each additional element. |
|
If the object has a RELS-EXT and/or a RELS-INT datastream, add 7, then add 1 for each statement asserted therein (except fedora-model:hasContentModel which has been counted above). |
|
For each additional datastream, add 7. |
|
|