Introduction
Documentation
Syntax
|
Documentation
|
external identifier of the type of the entity
|
Subschema
|
generic
|
Parents*
|
balise,
baliseGroup,
border,
bufferStop,
crossing,
derailerIS,
detector,
electrificationSection,
etcsArea,
etcsLevelTransition,
keyLockIS,
levelCrossingIS,
line,
linesideElectronicUnitIS,
loadingGauge,
loop,
mileageChange,
operationalPoint,
overCrossing,
platform,
platformEdge,
radioBlockCentreBorder,
restrictionArea,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
tunnelGateIS,
underCrossing,
weightLimit
|
Children
|
None
|
Attributes:
- rulebook: name of a rule book where the designator entry can be found (obligatory;
xs:string ),
- description: description of the designator, which can be used to provide basic information about an external system that uses the designator for external referencing (optional;
xs:string ),
- endDate: end date of the validity of the entry specified with this designator (optional;
xs:date ),
- entry: the designator of the element in the specified register (obligatory;
xs:string ),
- startDate: begin date of the validity of the specified entry specified with this designator (optional;
xs:date )
|
*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.2 within the Generic subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
This element does not appear in railML® 3.1 within the Generic subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
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.
Introduced with version 3.3.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues