IS:border

From railML 3 Wiki
Jump to: navigation, search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:border of railML® version 3.2
Documentation A border point is used to separate the railway network due to different reasons. Typical examples are country borders, the change of owning infrastructure manager or the border of a station.
Subschema infrastructure
Parents* borders
Children any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), markedByInfrastructureElement (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
Attributes:
  • isOpenEnd: set TRUE if this represents the end of the known network; default value FALSE (optional; xs:boolean),

  • externalRef: reference to an external identifier allowing to connect in this border point (only useful in case of open ends) (optional; xs:string),

  • type: defines the type of the border, e.g. "infrastructureManager" to indicate a border between two railway areas owned by different railway infrastructure managers (obligatory; xs:string; patterns: other:\w{2,})
Possible values:
  • area: border between different areas, e.g. areas that are controlled by different controllers
  • country: border between different (national) countries
  • infrastructureManager: border between infrastructure networks of different infrastructure managers
  • state: border of a (federal) state
  • station: border of a station
  • tariff: border between different tariff zones;
    Shall also be used for borders between two (or more) transport associations,

  • 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}\})
*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:border of railML® version 3.1
Documentation A border point is used to separate the railway network due to different reasons. Typical examples are country borders, the change of owning infrastructure manager or the border of a station.
Subschema infrastructure
Parents* borders
Children any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), markedByInfrastructureElement (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
Attributes:
  • isOpenEnd: set TRUE if this represents the end of the known network; default value FALSE (optional; xs:boolean),

  • externalRef: reference to an external identifier allowing to connect in this border point (only useful in case of open ends) (optional; xs:string),

  • type: defines the type of the border, e.g. "infrastructureManager" to indicate a border between two railway areas owned by different railway infrastructure managers (obligatory; xs:string; patterns: other:\w{2,})
Possible values:
  • tariff: border between different tariff zones;

Shall also be used for borders between two (or more) transport associations

  • station: border of a station
  • state: border of a (federal) state
  • infrastructureManager: border between infrastructure networks of different infrastructure managers
  • country: border between different (national) countries
  • area: border between different areas, e.g. areas that are controlled by different controllers,

  • 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}\})
*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.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues