Ability to define paths in the domain model and then refer to them in other model elements. Similar notion to interfaces and socket bindings.
Paths can be declared at the domain level but not fully specified:
At the server level they would need to be fully specified. This could be done at the host or server level:
<path name="tmp.dir" path="/tmp"/>
Paths can reference other paths:
<path name="tmp.examples" path="examples" relative-to"tmp.dir"/>
The system will some default paths that are not changeable by the user but can be referenced in other paths' "relative-to" attribute or in other model elements, e.g.:
These paths are not changeable by the user because the system needs to know what they are before configuration file parsing can be done.
The system will also include some other "standard" paths that can be referenced in other paths' "relative-to" attribute or in other model elements and whose meaning can be changed by the user, e.g.: