An xR registry system may include a number of components that are common across use cases. First, a common registry (or registry of registries) which provides for the following: rights based on certain properties that can be associated with the xR experiences, including permissions and ability to permit, prohibit, or restrict experiences; rules for determining who can or cannot deliver an xR experience to consumers based on various properties such as ownership, location, proximity, devices, permissions, etc.; and rules for determining who can and cannot consume an xR experience based on various properties such as ownership, personal preferences, location, proximity, devices, permissions, etc.
The xR registry may to store information regarding what is allowed or prohibited based on such rights (who, what, where, when, etc.) and interface with third party systems that may also contain such data (as both input and output). It may also have the ability to create and manage such rights, including what objects can have xR experiences, and the xR experiences themselves. The registry may also store what xR experiences are available and have been created and available including associations with ‘locations’ or other mechanisms for association with an object or place.
The registry may also store locations (in space, time, z dimensions, etc.) to which an xR experience may be associated and displayed. This includes storing one or more locations where the displayed object can be viewed from (multiple dimensions which will not be a rectangle). The registry may also store other types of objects (inanimate objects, people, animals, etc.) and the ability to recognize the type of object, including if the objects are movable or changeable over time.