...
Federation (aka Projection)
See: Projection
Fixity
Fixity is a measurement or characterization of stored information at a given time. An identity between , a reference to the stored information being 'fixed' or otherwise unchanged. Comparing two values of fixity can be interpreted as some measurement of the integrity of the stored information over time. Fedora performs fixity checks on demand by comparing a stored checksum with one that is newly computed.
Indexer
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.
Indexer
Creating, modifying or deleting resources in the repository generates events. The An (optional) indexer monitors and processes these events; by ingesting relevant RDF , such as loading RDF from Fedora to an external triplestore, for example.
The W3C Linked Data Platform (LDP) specification describes a set of best practices and a simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using the RDF data as the data model. Fedora 4 5 implements the LDP specification for create, read, update and delete (CRUD), allowing HTTP, REST, and linked data clients to make requests to Fedora 4interact with Fedora 5.
Managed External Content
...
| Anchor |
|---|
| managedexternalcontent |
|---|
| managedexternalcontent |
|---|
|
Managed External Content is Refers to content that sits resides outside of the Fedora -configured datastore5 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.
Namespace
...
A namespace is a container for a set of identifiers (also known as symbols, names). In Fedora 45, resource properties may belong to any namespace providing semantic assertions that support interoperable metadata. 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
...
| Anchor |
|---|
| nonRdfSourceDescription |
|---|
| nonRdfSourceDescription |
|---|
|
A nonRdfSourceDescription is a resource that describes a binary resource within the Fedora repository. A nonRdfSourceDescription is always accompanied by a binary, and vice versa.
Object
See: Container
Policy Enforcement Point (PEP)
This is a pluggable component in the Fedora framework that is responsible for authorizing all actions take on resources.
Predicate
A predicate expresses a relationship between the subject and the object of a triple.
Prefix
Typically a short string representation of an associated namespace. For example the prefix "dc" could be is frequently 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 When using defined namespace prefixes, it is possible, for example, to use "dc:contributor" or in versus the full form form "http://purl.org/dc/elements/1.1/contributor" to reference the Dublin Core "contributor" element.
Prefixes are limited to the following grammar:
| Code Block |
|---|
LocalName ::= ValidString - SelfOrParent
/* Any ValidString except SelfOrParent */
SelfOrParent ::= '.' | '..'
ValidString ::= ValidChar {ValidChar}
ValidChar ::= XmlChar - InvalidChar
/* Any XmlChar except InvalidChar */
InvalidChar ::= '/' | ':' | '[' | ']' | '|' | '*'
XmlChar ::= /* Any character that matches the Char production at http://www.w3.org/TR/xml/#NT-Char */ |
Projection (aka: Federation)
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 that contains properties, the RDF will contain triples for each property where the subject of the triple is the resource itself, the predicate of the 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
Containers are defined by one or more rdf:types that describe the nature of the container. Similarly, every property 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, or a binary. Every resource has a name and a unique identifier, and can also be identified by a path. They is uniquely identified, its identifier representing a repository path. Resources are comprised of zero or more properties and/or child resources.
Tombstone
A tombstone is a repository resource marker indicating that a a container, binary a nonRdfSourceDescription, or nonRdfSourceDescription a binary used to exist at a given URL. A tombstone is created when a resource is deleted or moved.
Transactions
A transaction represents a series of changes to the repository that must execute successfully and completely or not at all. Transactions are client initiated and should be used to ensure consistency. Each transaction succeeds or fails as a complete unit; it cannot remain in an intermediate state.
Triple
A triple is a fundamental building block of RDF. It consists of: a subject, predicate, and an object. In this way, a triple can describe a relationship (via the predicate) of the subject to the object. The official definition can be found here.
A string of characters used to uniquely identify a resource. It is defined in RFC3986, section 3. An example of a URI would be "http://purlid.loc.orggov/dcauthorities/elements/1.1/subjects/sh2002000192".
Universally Unique Identifier (UUID)
A "practically" 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.
Version
A snapshot of a resource that is saved in version history for later access.