Terminology
An overview of the novem terminology
Novem is currently in closed alpha. This documentation is incomplete and subject to change.
Novem is a fairly complicated platform and to make sure we're all talking about the same thing we've created a set of technical terms with explicit meaning.
This page provides a list and definition of the important technical terms and their definition.
The fully qualified novem path is how we refer to objects and entities within the novem platform. The FQNP gives a 100% unique string representation of all resources on the novem platform.
FQNPs are designed to be typeable, URL friendly, hierarchical and intuitive.
Novem resources are owned by either users or organisations, as such there are
two root nodes in FQNP, either /u/ or /o/.
By convention all partial FQNPs should alternate between a general and a
specific part with the general part listing the available options
(conditioned on access).
As such /u/ should list all users and /u/username/ should list all resources
available for username.
Below we use the example of a plot variable as a fairly complex FQNP, but other visualisations, jobs and repos exhibit similar patterns.
For example, to reference a variable published on a novem plot you could reference it as follows: