IS:overCrossing/3.1

From railML 3 Wiki
Revision as of 13:21, 24 January 2020 by RailML Coord Documentation (talk | contribs) (Updated page IS:overCrossing/3.1 using XSD2MediaWiki Converter 1.0.2)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Automatic Schemaexport for Element overCrossing



Autoexport from the XML-Schema for element IS:overCrossing of railML® version 3.1
Documentation An over crossing describes a crossing, where something crosses over the railway line. From constructional point of view an over crossing can be a bridge or a tunnel.
Subschema infrastructure
Parents* overCrossings
Children allowedLoadingGauge (0..*), any (0..*), areaLocation (0..*), crossesElement (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), length (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*)
Attributes:
  • constructionType: construction type of over crossing: bridge or tunnel (obligatory; xs:string; patterns: other:\w{2,})
Possible values:
  • tunnel
  • bridge,

  • belongsToParent: reference to a parent over crossing (optional; xs:IDREF; 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}\}),

  • verbalConstraint: verbal formulation for any kind of further constraint that applies for using the overCrossing or underCrossing (optional; xs:string),

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