The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Introduction
Documentation
Syntax
|
|
| Documentation
|
the tuple of references to the locked device and its state
|
| Subschema
|
interlocking
|
| Parents*
|
givenState,
requiredKeyLockState
|
| Children
|
refersToKeyLock (1..1)
|
Attributes:
- inState: The state (locked/released) the key release instrument has. (obligatory;
xs:string)
- Possible values:
- locked: The related element is in a locked stated, i.e. secured in its position for safe railway operation
- released: The related element is not in a locked state.,
- isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional;
xs:boolean)
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
|
|
| Documentation
|
the tuple of references to the key lock and its state
|
| Subschema
|
interlocking
|
| Parents*
|
givenState,
requiredKeyLockState
|
| Children
|
any (0..*), designator (0..1), refersToKeyLock (1..1)
|
Attributes:
- inState: The state the key release instrument has. (obligatory;
xs:string)
- Possible values:
- isNegated: The exclusion of a particular state, i.e. everything else that this one. (optional;
xs:boolean),
- id: unique identifier (optional;
xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice:
Elements may have different parent elements. As a consequence they may be used in different contexts.
Please, consider this as well as a user of this wiki as when developing this documentation further.
Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
Changes 3.1→3.2
The element documentation has been changed.
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues