NESTS - Named Entities in Simple Tiered Spaces

home | Entity internal structure 1 | Design objectives | Organization of namespaces | Internal implementation of namespaces | Entity internal structure 2

Organization of namespaces

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.)


  1. 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).

  2. 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.

  3. Mappings of namespace to other entities can be shared (to the extent useful) between hosts.

  4. An OM namespace path can be used to uniquely identify the host on which any particular namespace (tree segment) exists.

  5. 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

  6. All namespaces have exactly the same structure and properties.

Tree path representation of namespaces

external

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.

internal

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

  1. public: An entity both the name and the contents of which are visible to any user granted access to this namespace by its stewards.

  2. semi-private: An entity the name of which is visible to any user granted access to this namespace by its stewards but the contents of which are visible only to the owner (steward) of the entity, to the stewards of the namespace enclosing it, and to users to whom the steward (or stewards) of the entity have granted permission to view or use it.

  3. private: An entity the name of which is visible to any user granted access to this namespace by its stewards but the contents of which are visible only to the owner (steward) of the entity, to the stewards of the namespace enclosing it, and to users to whom the steward (or stewards) of the entity have granted permission to view or use.

  4. hidden: A nameless entity the contents or properties of which are visible only to the to stewards of the namespace enclosing it or those of an ancestral namespace.

  5. All namespaces are essentially similar. None has a higher "status" or priority than any other from the perspective of NESTS (or the OM definitions on which it is built (although users may assign such an interpretation where it is useful to do so). At its most fundamental level, the namespaces simply provide a variety management mechanism.

  6. A currency is any variable type. The name persists from the original application of this nested namespace structure - open money.

    A currency is an example of a semi-private entity. It may be created by any user within any namespace if (and only if) the stewards of that namespace have granted the necessary permissions.

    The creator (definer) of that currency may share the steward role with other users (again subject to the permissions granted by the stewards of the enclosing namespace.

  7. A user may exist in any namespace (subject to the permissions granted by its stewards), including the registry|namespace in which its primary identity is enclosed.

    A user is essentially a private namespace, both enclosing and concealing that user's accounts 7.

  8. A registry may may be embodied in any namespace.

    A registry is essentially a hidden 4 space enclosed within a public namespace.

    A registry encloses primary identities 9.

    Because a registry is inseparable from the namespace in which it is embodied, it can be regarded as a property of that namespace and identified by the same name.

  9. A primary identity (also known as a login identity) comprises a set of identifying data 9 sufficient to meet the requirements specified by the stewards of the enclosing namespace.

    It also includes a set of flags controlled only by the stewards of the immediately enclosing namespace or, under exceptional conditions, overridden or disabled by the stewards of an ancestral namespace. A subset of these flags may be visible to the owner of the primary identity if permitted by the stewards of the immediately enclosing namespace.

  10. Accounts are operated upon in various ways depending upon the currency 6 type definition 10 with which it is associated, the operations defined and implemented for it, and the permissions granted by its owner to agents capable of making use of such operations.

    In the case of the family of open money currency types, a special property is that the accounts belonging to all users of such an open money form a distributed ledger the sum of which is always zero. This provides the basis of a zero-sum, interest-free mutual credit (or mutual commitment) closure.




Version 0.30 - 2023-08-20 21.45 - Copyright © 2023, 2022 John Waters


home