RTM:spotLocation/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Updated page RTM:spotLocation/3.2 using XSD2MediaWiki Converter 1.1.1)
(Updated page RTM:spotLocation/3.2 using XSD2MediaWiki Converter 1.1.1)
 
Line 49: Line 49:
{{attribut|name=intrinsicCoord|pflicht=0|typ=xs:double|documentation=location on the <netElement> in normalized form (value in range 0..1)}},
{{attribut|name=intrinsicCoord|pflicht=0|typ=xs:double|documentation=location on the <netElement> in normalized form (value in range 0..1)}},
{{attribut|name=netElementRef|pflicht=1|typ=xs:string|documentation=reference to a railway topology <netElement> element|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;&#x007C;\&#x007B;[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;\&#x7D;}}}},
{{attribut|name=netElementRef|pflicht=1|typ=xs:string|documentation=reference to a railway topology <netElement> element|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;&#x007C;\&#x007B;[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;\&#x7D;}}}},
{{attribut|name=pos|pflicht=0|typ=xs:decimal|documentation=generic type for length values measured in metres}},
{{attribut|name=pos|pflicht=0|typ=xs:decimal|documentation=a distance from the edge of a net element}},
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;&#x007C;\&#x007B;[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;\&#x7D;}}}}
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;&#x007C;\&#x007B;[0-9a-fA-F]&#x007B;8&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;4&#x7D;-[0-9a-fA-F]&#x007B;12&#x7D;\&#x7D;}}}}
}}
}}

Latest revision as of 15:45, 17 May 2024

Automatic Schemaexport for Element spotLocation

Autoexport from the XML-Schema for element RTM:spotLocation of railML® version 3.2
Documentation

defines the concept of punctual location on a net element of a logical topology of a network.

Subschema

Rtm4railml

Parents*
Children
Attributes:

  • applicationDirection: direction in which the element is applied, related to the orientation of the <netElement> (optional; xs:string)
Possible values:
  • both
  • normal
  • reverse,

  • intrinsicCoord: location on the <netElement> in normalized form (value in range 0..1) (optional; xs:double),

  • netElementRef: reference to a railway topology <netElement> element (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}\}),

  • pos: a distance from the edge of a net element (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.