Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:netElement of railML ® version 3.2 |
| Documentation
|
The NetElement type is derived from the RailTopoModel class PositioningNetElement.
|
| Subschema
|
infrastructure
|
| Parents*
|
netElements
|
| Children
|
associatedPositioningSystem (1..*), designator (0..*), elementCollectionOrdered (0..*), elementCollectionUnordered (0..*), isValid (0..*), name (0..*), relation (0..*)
|
Attributes:
- length: length of the NetElement in metres (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (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}}); compare: Dev:Identities
|
*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 IS:netElement of railML ® version 3.1 |
| Documentation
|
The NetElement type is derived from the RailTopoModel class PositioningNetElement.
|
| Subschema
|
infrastructure
|
| Parents*
|
netElements
|
| Children
|
associatedPositioningSystem (1..*), elementCollectionOrdered (0..*), elementCollectionUnordered (0..*), isValid (0..*), name (0..*), relation (0..*)
|
Attributes:
- length: length of the NetElement in metres (optional;
xs:decimal),
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:ID; 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}}); compare: Dev:Identities
|
*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
The children have changed.
The attributes have been changed.
Semantics
Best Practice / Examples
Additional Information
Notes
Open Issues