...
A named role, such as "writer", assigned to a user, a group, or some other identifying agent within the repository. Roles may be used by the policy enforcement point (PEP) to authorize actions taken in the repository.
...
A binary in a Fedora repository is a nonRdfSource 178883319 resource. In other contexts, binaries would sometimes be described as bitstreams or files. Binaries are always accompanied by a 178883319 nonRdfSourceDescription.
Checksum Anchor checksum checksum
| checksum | |
| checksum |
A computed fingerprint for binary content, used to ensure a complete transfer or the 178883319 fixity of stored information. Fedora supports the SHA-1 checksum algorithm by default, but can also support SHA-256 and MD5.
...
The resources that are immediate children of a given 178883319 container. Properties are not children.
Container
| Anchor | ||||
|---|---|---|---|---|
|
A container is a 178883319resource that represents intellectual entities and can also be used to aggregate other resources in a Fedora repository. Containers may contain other containers or binaries and their nonRdfSourceDescriptions.
Datastream
| Anchor | ||||
|---|---|---|---|---|
|
Datastream is principally a Fedora 3 concept. Within the Fedora 4 model, the closest equivalent to a datastream is a 178883319 binary and its 178883319 NonRdfSourceDescription. Treat both together as a datastream; they only ever occur in a pair.
...
Federation (aka Projection) Anchor federation federation
| federation | |
| federation |
See: Projection
Fixity
| Anchor | ||||
|---|---|---|---|---|
|
Fixity is a measurement or characterization of stored information at a given time, a reference to the stored information being 'fixed' or otherwise unchanged. Comparing two values of fixity generated at different times, such as comparing two checksums for a given binary file with one having bee generated before ingest to a repository and the second after ingest, provides a means to determine whether the information has changed.
...
Managed External Content is content that resides outside of the Fedora 5 repository, but is managed by Fedora through a projection. Managed external content can be accessible via the Fedora API as well as have Fedora-managed audits.
...
A namespace is a container for a set of identifiers (also known as symbols, names). In Fedora 5, 178883319 resource properties may belong to any namespace. Namespaces are restricted to being an empty string or to a URI as defined in section 3 of RFC3986. An example of a namespace would be "http://purl.org/dc/elements/1.1/".
NonRdfSourceDescription (formerly the properties of a Fedora 3 Datastream)
| Anchor | ||||
|---|---|---|---|---|
|
A nonRdfSourceDescription is a 178883319 resource that describes a 178883319 binary resource within the Fedora repository. A nonRdfSourceDescription is always accompanied by a 178883319 binary, and vice versa.
Policy Enforcement Point (PEP)
| Anchor | ||||
|---|---|---|---|---|
|
This is a pluggable component in the Fedora framework that is responsible for authorizing all actions take on resources.
Predicate
| Anchor | ||||
|---|---|---|---|---|
|
A predicate expresses a relationship between the subject and the object of a 178883319 triple.
Prefix
| Anchor | ||||
|---|---|---|---|---|
|
Typically a short string representation of an associated 178883319 namespace. For example the prefix "dc" is frequently used to represent the namespace "http://purl.org/dc/elements/1.1/". When using defined namespace prefixes, it is possible, for example, to use "dc:contributor" versus the full form "http://purl.org/dc/elements/1.1/contributor" to reference the Dublin Core "contributor" element.
Prefixes are limited to the following grammar:
...
The process by which a repository may present resources through the API that are actually stored in a different system, such as a file system or database.
...
Properties are name/value pairs that belong to resources. The name of a property can be any term from a namespaced vocabulary. When RDF is generated in response to a request for a 178883319 resource that contains properties, the RDF will contain triples for each property where the subject of the 178883319 triple is the resource itself, the 178883319 predicate of the 178883319 triple is the property name, and the object of the triple is the value of the property. Property values can be of any valid rdf:type.
rdf:type
| Anchor | ||||
|---|---|---|---|---|
|
Containers are defined by one or more rdf:types that describe the nature of the 178883319 container. Similarly, every property will be an instance of a single rdf:type. The official definition can be found here.
...
Resources are the primary organizational structure in the repository. A resource is any web-addressable entity, such as a container, a 178883319 nonRdfSourceDescription, or a 178883319 binary. Every resource is uniquely identified, its identifier representing a repository path. Resources are comprised of zero or more properties and/or child resources.
...
A tombstone is a repository marker indicating that a container, a 178883319 nonRdfSourceDescription, or a 178883319 binary used to exist at a given URL. A tombstone is created when a resource is deleted or moved.
...
A triple is a fundamental building block of RDF. It consists of: a subject, 178883319 predicate, and an object. In this way, a triple can describe a relationship (via the 178883319 predicate) of the subject to the object. The official definition can be found here.
...
A string of characters used to uniquely identify a 178883319 resource. It is defined in RFC3986, section 3. An example of a URI would be "http://id.loc.gov/authorities/subjects/sh2002000192".
...
A universally unique identifier is a 36 hexadecimal number that is, for all practical purposes, unique (though there is an extraordinarily slight chance of a duplicate identifier being created in the future or already existing). It is used to identify a 178883319 resource.
Version
| Anchor | ||||
|---|---|---|---|---|
|
A snapshot of a 178883319 resource that is saved in version history for later access.