NB: This is a temporary working document under continual revision as coding progresses. The documents and the initial implementation are co-evolving continually, so expect to find some duplications and occasional inconsistencies (all of which will be removed over time). (See page footer for most recent revision.)
OM namespaces are organized in namespace trees. A path through such a tree is referred to as a namespace path and is, by convention, represented by a string listing namespace name from left (furthest branches) to right (the root of the tree).
Although an OM namespace can resemble a URL, it bears no relationship to any other identifier. Its naming conventions are less constrained, and UTF8 allows a far larger character set to be used.
Mappings of namespace to other entities can be shared (to the extent useful) between hosts.
An OM namespace path can be used to uniquely identify the host on which any particular namespace (tree segment) exists.
A namespace tree can be grafted on to any part of an existing namespace tree (other than itself), so
e.g.
can be added to
as
All namespaces have exactly the same structure and properties.
From lowest (most local) level to highest (most close to global) level accessible/visible within scope.
For example, a simple geopolitical namespace tree path might
be represented as
gardencity.chepstow.mon.cy.uk
while one possible bioregional namespace tree path
intersecting the example above geographically might focus upon water
catchment, flows, etc.
beachley.mouth.lower.wye-valley.uk
Namespaces can be created and nested to suit any purpose.
Within the NESTS implementation, the two namespace path
examples above would be represented (respectively) below the trees' roots (in
ROOT - e.g. /var/nests/roots/) by filesystem paths such as
/dd5d03832c754be8/9ccec313762b2074/98f2f281a3bd013b/1d31cc469d128365/f9ac47bf5464167a/
and
/dd5d03832c754be8/3054169c03341e0d/e6c970fe368550df/77e102468e08a446/39d5bb735d7c696f/
where each name, regardless of the alphabet used to represent it in
human-readable form, is mapped on to a short collision-resistant hash (in
this case of 8 hex character = 64 bits).
Each namespace contains other named entities.
Each named entity is a represented internally by a directory
containing a number of different types of information (depending on the
entity type).
Typically, ROOT might be one of the following (for example):
/var/nests/
/srv/nests/
/mnt/srv/nests/
A NESTS hub might host several distinct root namespaces, each with its own collective of stewards but sharing a common collective of hub stewards (system administrators).
Every NESTS hub will include a root
namespace "test" under which valid examples will be created
to assist in automated testing. Internally this will be represented as both of
the following:
2d7f1808da1fa63c (xxhash64 hash of string "test")
test -> 2d7f1808da1fa63c (symlink to the above)
Every NESTS hub will also include a root
namespace "sandbox" in which users can experiment freely and
harrmlessly with the commands available. The entire "sandbox" tree
will be cleared automatically at regular intervals (on the hour by default,
but this may be overridden by the NESTS hub system administrators.
Internally this will be represented as both of the following:
f0efa7d611aeaed7 (xxhash64 hash of string "sandbox")
sandbox -> f0efa7d611aeaed7 (symlink to the above)
NB, the 64-bit xxhash64 hash may be replaced in due course with the 32-bit xxhash32 equivalent, or perhaps even the 128-bit version. Such a change will require only one substitution in the nshash function and a single pass of a script to traverse the trees renaming each directory in turn.
| Table 1: Named entity types within NESTS namespaces | ||
| entity type | visibility | description |
| namespace | public 1 | A namespace enclosed (or nested) within this namespace. 5 |
| currency | semi-private 2 | A definition of a variable type 6. |
| primary identity 9 | private 3 | The identity 9 of a person, organization, machine or any other type type of agent identified uniquely in a registry 8. |
| secondary identity 9 | private 3 |
This is an alias of a primary identity contained within any namespace with the authorization of its steward(s). A distinct collection of accounts will be associated with this secondary identity (but will remain the responsibility of the associated primary identity). |
| account 10 | private 3 | An account is a variable owned by a user. It is visible only to its owner (user/steward), to any other user to which the the owner has granted visibility, to the stewards of the namespace enclosing it, and (under exceptional circumstances) to the stewards of ancestral namespaces. |
|
Notes for Table 1
|
||
Version 0.30 - 2023-08-20 21.45 - Copyright © 2023, 2022 John Waters