The nodes which are immediate children of a given Node. This only includes child nodes in the hierarchy, it does not include nodes which are referenced by Properties.
Compact Node Definition (CND):
A file format defined by JCR here. It 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.
Datastream (aka Fedora Datastream):
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.
Includes the current node's parent node, and any child nodes it may have. Child datastream nodes also show their content node (jcr:content).
An XML document which has a format that represents JCR resources. It can be used to import a set of nodes and properties into a workspace. Or it can be used to export a full representation of a Node. See https://docs.jboss.org/author/display/MODE/Initial+Content for more detail.
A namespace is a container for a set of identifiers. In Fedora 4, namespaces are restricted to being an empty string or to a URI as defined in section 3 of http://tools.ietf.org/html/rfc3986#section-3. An example of a namespace would be "http://purl.org/dc/elements/1.1/".
Nodes are the primary organizational structure in the repository. Every node has a name and a unique identifier, and can also be identified by a path. They are comprised of zero or more properties / child nodes.
A Node's properties and children can be limited by its Primary and Mixin Node Types. ModeShape / JCR provides a number of Node Types and Mixins. Node Types are defined in CND files within in the Fedora / ModeShape, users can define their own CND files and upload them to create new Node Types.
Object (aka Fedora Object):
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.
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:
Properties (aka JCR Properties):
Properties are typed values that belong to Nodes. Properties can be restricted to a single value or can be a collection of values with the same name (A property's multiplicity is limited by the Node definition in which it is defined). They can be any one of the following types STRING, BINARY, LONG, DOUBLE, DATE, BOOLEAN, NAME, PATH, REFERENCE, WEAKREFERENCE, URI, and DECIMAL.
Is an RDF property that is used to define that the Node described belongs to a class of functionality / behavior. For example http://www.w3.org/ns/ldp#Container is an rdf:type that denotes the node can contain other nodes. The official definition 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. Fedora is a repository.
A Transaction represents a series of changes to the repository that must execute successfully and completely or not at all. They are used to ensure consistency. Each transaction must succeed or fail as a complete unit; it cannot remain in an intermediate state.
Uniform resource identifier (URI):
Is a string of characters used to identify a name of a web resource. It is defined in section 3 of http://tools.ietf.org/html/rfc3986#section-3. An example of a URI would be "http://purl.org/dc/elements/1.1/".
Universally unique identifier (UUID):
A "practically" unique identifier that is used to identify a node. For more detailed description see wikipedia.
The repository is divided into separate named workspaces, and it is within these workspaces that all content is stored as a tree-structure of nodes. At a minimum, there is always a default workspace named "default". The top of that tree structure is the root node (named "/"), and all nodes in the tree are accessible via navigation (path) or via query result.