Page History

...

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 resource 178883319. In other contexts, binaries would sometimes be described as bitstreams or files. Binaries are always accompanied by a nonRdfSourceDescription 178883319.

Checksum

Anchor
checksum checksum

A computed fingerprint for binary content, used to ensure a complete transfer or the fixity 178883319 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 container 178883319.  Properties are not children.

Container

Anchor
container container

A container is a resource178883319 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 datastream

Datastream is principally a Fedora 3 concept.  Within the Fedora 4 model, the closest equivalent to a datastream is a binary 178883319 and its NonRdfSourceDescription 178883319. Treat both together as a datastream; they only ever occur in a pair.

...

Federation (aka Projection)

Anchor
federation federation

See: Projection

Fixity

Anchor
fixity fixity

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, resource 178883319 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
nonRdfSourceDescription nonRdfSourceDescription

A nonRdfSourceDescription is a resource 178883319 that describes a binary 178883319 resource within the Fedora repository. A nonRdfSourceDescription is always accompanied by a binary 178883319, and vice versa.

Policy Enforcement Point (PEP)

Anchor
pep pep

This is a pluggable component in the Fedora framework that is responsible for authorizing all actions take on resources.

Predicate

Anchor
predicate predicate

A predicate expresses a relationship between the subject and the object of a triple 178883319.

Prefix

Anchor
prefix prefix

Typically a short string representation of an associated namespace 178883319. 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 resource 178883319 that contains properties, the RDF will contain triples for each property where the subject of the triple 178883319 is the resource itself, the predicate 178883319 of the triple 178883319 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
rdftype rdftype

Containers are defined by one or more rdf:types that describe the nature of the container 178883319. 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 nonRdfSourceDescription 178883319, or a binary 178883319. 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 nonRdfSourceDescription 178883319, or a binary 178883319 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, predicate 178883319, and an object. In this way, a triple can describe a relationship (via the predicate 178883319) of the subject to the object. The official definition can be found here.

...

A string of characters used to uniquely identify a resource 178883319. 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 resource 178883319.

Version

Anchor
version version

A snapshot of a resource 178883319 that is saved in version history for later access.