Introduction
Documentation
Syntax
|
Documentation
|
reference a LocatedNetEntity to the whole Network (or LevelNetwork) without explicitly naming all the contained NetElements. This approach will be useful to define "global values", e.g. the railway electrification parameters or the track gauge for the whole railway network.
|
Subschema
|
infrastructure
|
Parents*
|
balise,
baliseGroup,
border,
bufferStop,
crossing,
derailerIS,
detector,
electrificationSection,
etcsArea,
etcsLevelTransition,
genericArea,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
linesideElectronicUnitIS,
loadingGauge,
loop,
mileageChange,
operationalPoint,
overCrossing,
platform,
platformEdge,
radioBlockCentreBorder,
restrictionArea,
roadSideBarriers,
roadSideLights,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
tunnelGateIS,
underCrossing,
weightLimit
|
Children
|
None
|
Attributes:
- networkRef: reference to a railway topology <network> element (optional;
xs:IDREF )
|
*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
|
reference a LocatedNetEntity to the whole Network (or LevelNetwork) without explicitly naming all the contained NetElements. This approach will be useful to define "global values", e.g. the railway electrification parameters or the track gauge for the whole railway network.
|
Subschema
|
infrastructure
|
Parents*
|
balise,
baliseGroup,
border,
bufferStop,
crossing,
derailerIS,
detector,
electrificationSection,
etcsArea,
etcsLevelTransition,
genericArea,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
loadingGauge,
mileageChange,
operationalPoint,
overCrossing,
platform,
platformEdge,
radioBlockCentreBorder,
restrictionArea,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
tunnelGateIS,
underCrossing,
weightLimit
|
Children
|
None
|
Attributes:
- networkRef: reference to a railway topology <network> element (optional;
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}})
|
*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
|
This element is not documented in the schema!
|
Subschema
|
infrastructure
|
Parents*
|
balise,
border,
bufferStop,
crossing,
derailerIS,
electrificationSection,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
loadingGauge,
operationalPoint,
overCrossing,
platform,
restrictionArea,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
underCrossing,
weightLimit
|
Children
|
None
|
Attributes:
- networkRef: reference to a railway topology <network> element (optional;
xs:IDREF ; 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}})
|
*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
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
The element documentation has been changed.
The parents have been changed.
The attributes have been changed.
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