IS:mileageChange/3.2

From railML 3 Wiki
Revision as of 21:51, 25 April 2022 by RailML Coord Documentation (talk | contribs) (Created page IS:mileageChange/3.2 using XSD2MediaWiki Converter 1.0.6)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Automatic Schemaexport for Element mileageChange

Autoexport from the XML-Schema for element IS:mileageChange of railML® version 3.2
Documentation

A MileageChange marks the point where the railway kilometer system does a jump resulting in a kilometer gap or overlap. A MileageChange needs to have two spot locations: one for the incoming and one for the outgoing kilometer value.

Subschema

infrastructure

Parents*
Children

areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)

Attributes:

  • type: This attribute is not documented in the schema! (obligatory; xs:string)
Possible values:
  • gap
  • overlap,

  • from: Referencing a spotLocation (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}\}),

  • to: Referencing a spotLocation (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}\}),

  • 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.