Table of Contents type flat separator pipe
Access Role
A named role, such as "writer", that is assigned to a user, group or some other identifying principal within part of the repository. Roles may be used by the policy enforcement point (PEP) to authorize actions taken in the repository.
Checksum
An algorithmically produced fingerprint for binary content, used to ensure a complete transfer or the fixity of stored information. Fedora supports the SHA1 checksum algorithm for safely uploading content.
...
A node type with the Primary type of [nt:file] and a Mixin type of [fedora:datastream]. It is used to represent file content within the Fedora repository. It always has a child node named "jcr:content", where the file's binary content is stored. It can also contain other derived [fedora:datastream] objects.
Federation (aka Projection)
The process by which a repository may present objects through the API that are actually stored in a different system, such as a file system or database.
Fixity
Fixity is the integrity of stored information over time. Fedora performs fixity checks on demand by comparing a stored checksum with one that is newly computed.
...
A node type with the Primary type of [nt:folder] and a Mixin type of [fedora:object]. It is the primary organizational node in a Fedora repository.
Policy Enforcement Point (aka PEP)
This is a pluggable component in the Fedora framework that is responsible for authorizing all actions take on objects.
Prefix
Typically a short string representation of an associated namespace. For example the prefix "dc" could be used to represent the namespace. "http://purl.org/dc/elements/1.1/". If we wanted to access an element (e.g. "contributor") within that namespace we could do it with the prefix "dc:contributor" or in the full form "http://purl.org/dc/elements/1.1/contributor".
Prefixes are limited to the following grammar:
...