Introduction
Documentation
Syntax
|
|
| Documentation
|
the tuple of references to the level crossing and its state
|
| Subschema
|
interlocking
|
| Parents*
|
givenState,
requiredLevelCrossingState,
requiresLevelCrossingInState
|
| Children
|
refersToLevelCrossing (1..1)
|
Attributes:
- inState: The state (open/closed) the level crossing has. (obligatory;
xs:string)
- Possible values:
- closed: position of the level crossing when the safe passage by railway traffic is allowed.
- open: position of the level crossing when the crossing of track(s) is safe for road traffic.
- unknown: position of the level crossing is not known,
- 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 level crossing and its state
|
| Subschema
|
interlocking
|
| Parents*
|
givenState,
requiredLevelCrossingState,
requiresLevelCrossingInState
|
| Children
|
any (0..*), designator (0..1), refersToLevelCrossing (1..1)
|
Attributes:
- inState: The state the level crossing has. (obligatory;
xs:string)
- Possible values:
- unknown
- closing
- opening
- closed
- open,
- 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 children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues