Introduction
| 🗒️
|
This article uses the unit label meter.
As the reference for this Wiki is British English, the correct label is metre.
Wherever the label meter occurs, it is meant equivalently to metre.
|
|
|
Documentation
Syntax
Autoexport from the XML-Schema for element IS:width of railML ® version 3.3 |
| Description
|
width of the platform
|
| Subschema
|
infrastructure
|
| Parents*
|
platform
|
| Children**
|
None
|
Attributes:
- type: type of length (operational, physical, administrative...) (obligatory:
tLengthTypeExt : xs:string: patterns: other:\w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- operational: operational or administrative length value
- physical: physical length value,
- validForDirection: indicate the direction for which the length information applies (optional:
tExtendedDirection : xs:string)
- Possible values:
- both: from intrinsicCoordinate=0 to intrinsicCoordinate=1 AND from intrinsicCoordinate=1 to intrinsicCoordinate=0 of associated <netElement>
- reverse: from intrinsicCoordinate=1 to intrinsicCoordinate=0 of associated <netElement>
- normal: from intrinsicCoordinate=0 to intrinsicCoordinate=1 of associated <netElement>,
- value: the distance value given in meters (obligatory:
tLengthM : xs:decimal)
|
*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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema
|
Autoexport from the XML-Schema for element IS:width of railML ® version 3.2 |
| Description
|
width of the platform
|
| Subschema
|
infrastructure
|
| Parents*
|
platform
|
| Children**
|
None
|
Attributes:
- type: type of length (operational, physical, administrative...) (obligatory:
tLengthTypeExt : xs:string: patterns: other:\w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- operational: operational or administrative length value
- physical: physical length value,
- validForDirection: indicate the direction for which the length information applies (optional:
tExtendedDirection : xs:string)
- Possible values:
- both: from intrinsicCoordinate=0 to intrinsicCoordinate=1 AND from intrinsicCoordinate=1 to intrinsicCoordinate=0 of associated <netElement>
- reverse: from intrinsicCoordinate=1 to intrinsicCoordinate=0 of associated <netElement>
- normal: from intrinsicCoordinate=0 to intrinsicCoordinate=1 of associated <netElement>,
- value: the distance value given in meters (obligatory:
tLengthM : xs:decimal)
|
*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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema
|
Autoexport from the XML-Schema for element IS:width of railML ® version 3.1 |
| Description
|
width of the platform
|
| Subschema
|
infrastructure
|
| Parents*
|
platform
|
| Children**
|
None
|
Attributes:
- value: the distance value given in meters (obligatory:
tLengthM : xs:decimal),
- type: type of length (operational, physical, administrative...) (obligatory:
tLengthTypeExt : xs:string: patterns: other:\w{2,}; consider Use of tOtherEnumerationValue too.)
- Possible values:
- physical: physical length value
- operational: operational or administrative length value,
- validForDirection: indicate the direction for which the length information applies (optional:
tExtendedDirection : xs:string)
- Possible values:
|
*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.
**Notice:
To learn, how to interpret multiplicity information like (0..*) go to The W3C Recommendation on XML Schema
|
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 attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues