Date: Thu, 28 Mar 2024 14:22:12 -0400 (EDT) Message-ID: <1783703234.28580.1711650132406@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28579_143465918.1711650132406" ------=_Part_28579_143465918.1711650132406 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Fedora 4 is a Linked Data Platform server as defi= ned by the Linked Data Platform 1.0 specification. As such, many of= the terms in this glossary are drawn directly from this specification.
A named role, such as "writer", that is assigned to a user, group or som= e other identifying principal within part of the repository. Roles may be u= sed by the policy enforcement point (PEP) to authorize actions taken in the= repository.
A binary in a Fedora repository is a nonRdfSource resource. In = other contexts, binaries would sometimes be described as bit-streams or fil= es. Binaries are always accompanied by a nonRdfSourceDescription.<= /p>
A computed fingerprint for binary content, used to ensure a complete tra= nsfer or the fixity of stored information. Fedora supports the SHA-1 checks= um algorithm for safely uploading content.
The resources which are immediate children of a given container. Pr= operties are not counted as children.
A file format defined by JCR here that allows for the definition of new resource= em> types and namespaces. It is highly recommended that users do n= ot modify Fedora 4's CND file, as such modifications may limit the ability = for subsequent Fedora version upgrades of the repository installation.
A container is a resource that represents intellectua= l entities and can also be used to aggregate other resources in a = Fedora repository. Containers may container other containers or binarie= s and their nonRdfSourceDescriptions.
See: NonRdfSourceDescription
An approach previously available in Fedora 3 that allowed for binding a = service to a content model. Note: disseminators, as such, do not e= xist in Fedora 4.
See: Projection
Fixity is the integrity of stored information over time. Fedora performs= fixity checks on demand by comparing a stored checksum with one that is ne= wly computed.
Creating, modifying or deleting resources in the repositor= y generates events. The indexer monitors and processes these events; by ing= esting relevant RDF to an external triplestore, for example.
An XML document, the schema of which is defined by the JCR specification, which has a format that represents JCR resou= rces. It can be used to export/import a set of resources and p= roperties into a repository.
The W3C Linked Data Platform (LDP) specification =
describes a set of best practices and si=
mple approach for a read-write Linked Data architecture, based on HTTP acce=
ss to web resources that describe their state using the RDF
Refers to content that sits outside the Fedora-configured datastore,&nbs= p;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 4, resource properties may be= long to any namespace providing semantic assertions that support interopera= ble metadata. Namespaces are restricted to being an empty string or to a UR= I as defined in section 3 of RFC3986. = An example of a namespace would be "http://purl.org/dc/elements/= 1.1/".
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.
See: Container
This is a pluggable component in the Fedora framework that is responsibl= e for authorizing all actions take on resources.
A predicate expresses a relat= ionship between the subject and the object of a triple.
Typically a short string representation of an associated namespace=
em>. 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:
LocalNa= me ::=3D ValidString - SelfOrParent /* Any ValidString except SelfOrParent */ SelfOrParent ::=3D '.' | '..'=20 ValidString ::=3D ValidChar {ValidChar} ValidChar ::=3D XmlChar - InvalidChar /* Any XmlChar except InvalidChar */ InvalidChar ::=3D '/' | ':' | '[' | ']' | '|' | '*' XmlChar ::=3D /* Any character that matches the Char production at http://w= ww.w3.org/TR/xml/#NT-Char */
The process by which a repository may present resources through= the API that are actually stored in a different system, such as a file sys= tem or database.
Properties are name/value pairs that belong to resources. The n= ame of a property can be any term from a namespaced vocabulary. Wh= en RDF is generated in response t= o a request for a resource that contains properties, the RDF will contain triples for eac= h property where the subject of the triple is the resource itself,= the predicate of the triple is the property name, and th= e object of the triple is the value of the property. Property values can be= of any valid rdf:type.
Containers are defined by one or more rdf:types that descr= ibe the nature of the container. Similarly, every propert= y will be an instance of a single rdf:type. The official def= inition can be found here.
A repository is a single, self-contained persistent store of information= plus the software that is used to access and update that information. Fedo= ra is a repository.
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 ha= s a name and a unique identifier, and can also be identified by a path. The= y are comprised of zero or more properties / child resources.
A tombstone is a repository resource indicating that a cont= ainer, binary, or nonRdfSourceDescription used to ex= ist at a given URL. A tombstone is created when a resource is deleted or mo= ved.
A transaction represents a series of changes to the repository that must= execute successfully and completely or not at all. Transactions should be = used to ensure consistency. Each transaction succeeds or fails as a complet= e unit; it cannot remain in an intermediate state.
A triple is a fundamental building block of RDF. It consists of: a subje= ct, predicate, and an object. In this way, a triple can describe a= relationship (via the predicate) of the subject to the object. Th= e 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://purl.org/dc/elements/1.1/".
A "practically" unique identifier that is used to identify a resourc= e.
A snapshot of a resource that is saved in version history for l= ater access.