Introduction
Documentation
Syntax
|
Documentation
|
specify an infrastructure element that is linked with this balise group: signal, levelTransition, radioBlockCenterBorder, switch, bufferStop
|
Subschema
|
infrastructure
|
Parents*
|
baliseGroup
|
Children
|
None
|
Attributes:
- ref: reference an object using its UUID or GenericID (xs:ID) (obligatory;
xs:IDREF ),
- type: type of connection to the infrastructure element (physical vs logical) (obligatory;
xs:string )
- Possible values:
- logical: e.g. a fixed data balise group is logical connected to an SMB signal which is a panel called ETCS stop marker board.
- physical: e.g. a switchable balise group is physically connected via cable with an electronic lineside unit (LEU)
|
*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
|
specify an infrastructure element that is linked with this balise group: signal, levelTransition, radioBlockCenterBorder, switch, bufferStop
|
Subschema
|
infrastructure
|
Parents*
|
baliseGroup
|
Children
|
None
|
Attributes:
- ref: reference to an infrastructure element (obligatory;
xs:string ; 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}}),
- type: type of connection to the infrastructure element (physical vs logical) (obligatory;
xs:string )
- Possible values:
- logical: e.g. a fixed data balise group is logical connected to an SMB signal which is a panel called ETCS stop marker board.
- physical: e.g. a switchable balise group is physically connected via cable with an electronic lineside unit (LEU)
|
*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.
|
This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues