Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Binary

A binary in a Fedora repository is a nonRdfSource resource. In other contexts, binaries would sometimes be described as bit-streams or files. Binaries are always accompanied by a nonRdfSourceDescription.

Checksum

A computed fingerprint for binary content, used to ensure a complete transfer or the fixity of stored information. Fedora supports the SHA-1 checksum algorithm for safely uploading content.

...

A file format defined by JCR here. It allows  that allows for the definition of new Node Types. See the ModeShape documentation for further information on how to use CND to create your own Node Types.

Container

...

Datastream (aka Fedora Datastream)

resource types and namespaces. It is highly recommended that users do not modify Fedora 4's CND file, as such modifications may limit the ability for subsequent Fedora version upgrades of the repository installation.

Container (formerly known as: object)

A container is a resource that is the primary organizational entity in a Fedora repository. Containers may container other containers or binaries and their nonRdfSourceDescriptionsA 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.

...

A namespace is a container for a set of identifiers (also known as symbols, names). In Fedora 4, 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 known as: datastream)

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 (aka Fedora Object)

...