Constants for Roles
Meshy Space base object b:unit has many relations.
The client MAY understand these relations. The relations have a Role,
and end in a Unit of a certain Type.
See also the concept Roles.
The is attribute of the b:has elements
in a b:unit describes the relation. When that value
is in the b: namespace, you will find it described below.
Roles do not need to refer to Units with only one specific Type: the
application client must be able to handle (ignore) unexpected Types.
ms:Role/Documentation
Refers to a Unit of type ms:Type/Documention
ms:Role/Manager
When the root Namespace b:has a Manager, then
access to that namespace can only take place via that Manager.
At the moment, the msc:Type/Shop is the only manager
for a top-namespace, and msc:Type/Collection for
sub-spaces.
ms:Role/Rule
Units referred to as this role, are of type ms:Type/Rule
or msc:Type/Rule and define expressions
(b:let)
mark@overmeer.net
Web-pages generated on 2023-12-19
| 
