-
Notifications
You must be signed in to change notification settings - Fork 0
MAP Metaspaces
The open ended nature of the MAP means that different groups can have different conceptions of how to define and structure MAP information. Eventually (post-L1), a MAP Metaspace will be an AgentSpace that is devoted to managing MAP Descriptors.
In the L0 prototype, each MAP Metaspace will be represented as a HolonSpace. It is a distinct DHT that offers a set of Schemas each containing MAP Descriptors.
Initially, the prototype will just include a single Metaspace.
A stretch goal for the prototype is to allow the elements of a Metaspace (e.g., its HolonDescriptors, RelationshipDescriptors, PropertyDescriptors, etc.) to reference Schema elements (e.g., ValueTypes, HolonTypes) defined in a different Metaspace. In other words, a MAP schema element can contain references to other local or external schema elements.