Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element RTM:isValid of railML ® version 3.3 |
| Documentation
|
period for which a certain information object is valid in respect to availability for usage for train operations.
|
| Subschema
|
Rtm4railml
|
| Parents*
|
associatedPositioningSystem,
balise,
baliseGroup,
border,
bufferStop,
crossing,
derailerIS,
detector,
electrificationSection,
etcsArea,
etcsLevelTransition,
genericArea,
geometricPositioningSystem,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
linearPositioningSystem,
linesideElectronicUnitIS,
loadingGauge,
loop,
mileageChange,
netConnector,
netConnectorRelation,
netElement,
netRelation,
operationalPoint,
overCrossing,
platform,
platformEdge,
radioBlockCentreBorder,
restrictionArea,
roadSideBarriers,
roadSideLights,
screenPositioningSystem,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
tunnelGateIS,
underCrossing,
weightLimit
|
| Children
|
None
|
Attributes:
- from: defines the point in time where the object in question is available for usage for train operations. (optional;
xs:date),
- to: defines the point in time where the object in question is no longer available for functional usage. (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.
|
Autoexport from the XML-Schema for element RTM:isValid of railML ® version 3.2 |
| Documentation
|
period for which a certain information object is valid in respect to availability for usage for train operations.
|
| Subschema
|
Rtm4railml
|
| Parents*
|
associatedPositioningSystem,
balise,
baliseGroup,
border,
bufferStop,
crossing,
derailerIS,
detector,
electrificationSection,
etcsArea,
etcsLevelTransition,
genericArea,
geometricPositioningSystem,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
linearPositioningSystem,
loadingGauge,
mileageChange,
netElement,
netRelation,
networkResource,
operationalPoint,
overCrossing,
platform,
platformEdge,
radioBlockCentreBorder,
restrictionArea,
screenPositioningSystem,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
tunnelGateIS,
underCrossing,
weightLimit
|
| Children
|
None
|
Attributes:
- from: defines the point in time where the object in question is available for usage for train operations. (optional;
xs:date),
- to: defines the point in time where the object in question is no longer available for functional usage. (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.
|
Autoexport from the XML-Schema for element RTM:isValid of railML ® version 3.1 |
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
Rtm4railml
|
| Parents*
|
associatedPositioningSystem,
balise,
border,
bufferStop,
crossing,
derailerIS,
electrificationSection,
geometricPositioningSystem,
geometryPoint,
gradientCurve,
horizontalCurve,
keyLockIS,
levelCrossingIS,
line,
linearPositioningSystem,
loadingGauge,
netElement,
netRelation,
networkResource,
operationalPoint,
overCrossing,
platform,
restrictionArea,
screenPositioningSystem,
serviceSection,
signalIS,
speedSection,
stoppingPlace,
switchIS,
track,
trackBed,
trackGauge,
trainDetectionElement,
trainProtectionElement,
trainRadio,
underCrossing,
weightLimit
|
| Children
|
None
|
Attributes:
- from: This attribute is not documented in the schema! (optional;
xs:date),
- to: This attribute is not documented in the schema! (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.
|
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.
Semantics
|
Semantic Constraint "IS:001":
Starting time stamp (e.g. "from") shall be lower or equal any ending time stamp (e.g. "to") if both are given. Must not overlap with other validity periods within the same enclosing element.
Proposed on January 15th 2024
Approved on April 15th 2024
FIXME Forum missing
Please, recognize our guidelines on semantic constraints
|
|
Best Practice / Examples
Additional Information
Notes
Open Issues
