IL:routeSequence/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page IL:routeSequence/3.2 using XSD2MediaWiki Converter 1.0.6)
 
(Updated page IL:routeSequence/3.2 using XSD2MediaWiki Converter 1.1.1)
 
Line 7: Line 7:
|version=3.2
|version=3.2
|parent={{parent|subschema=IL|name=routeSequences}}
|parent={{parent|subschema=IL|name=routeSequences}}
|children={{child|subschema=IL|name=belongsToOperationalPoint|multiplicity=0..*}}, {{child|subschema=IL|name=comboEntry|multiplicity=1..1}}, {{child|subschema=IL|name=comboExit|multiplicity=1..1}}, {{child|subschema=IL|name=containsRoute|multiplicity=1..*}}, {{child|subschema=CO|name=designator|multiplicity=0..*}}, {{child|subschema=IL|name=hasCommand|multiplicity=0..*}}, {{child|subschema=IL|name=hasIndication|multiplicity=0..*}}, {{child|subschema=CO|name=objectName|multiplicity=0..*}}
|children={{child|subschema=IL|name=belongsToOperationalPoint|multiplicity=0..*}}, {{child|subschema=IL|name=comboEntry|multiplicity=1..1}}, {{child|subschema=IL|name=comboExit|multiplicity=1..1}}, {{child|subschema=IL|name=containsRoute|multiplicity=1..*}}, {{child|subschema=generic|name=designator|multiplicity=0..*}}, {{child|subschema=IL|name=hasCommand|multiplicity=0..*}}, {{child|subschema=IL|name=hasIndication|multiplicity=0..*}}, {{child|subschema=generic|name=objectName|multiplicity=0..*}}
|attributes={{attribut|name=priorityRank|pflicht=0|typ=xs:nonNegativeInteger|documentation=Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0.}},
|attributes={{attribut|name=priorityRank|pflicht=0|typ=xs:nonNegativeInteger|documentation=Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0.}},
{{attribut|name=elementNumber|pflicht=0|typ=xs:nonNegativeInteger|documentation=element number of the object for internal referencing in the engineering data}},
{{attribut|name=elementNumber|pflicht=0|typ=xs:nonNegativeInteger|documentation=element number of the object for internal referencing in the engineering data}},
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=unique identifier|patterns={{pattern|(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}\}}}}}
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=unique identifier|patterns={{pattern|(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}\}}}}}
}}
}}

Latest revision as of 12:42, 8 February 2024

Automatic Schemaexport for Element routeSequence

Autoexport from the XML-Schema for element IL:routeSequence of railML® version 3.2
Documentation RouteSequence is a combination of single routes defining the path from A to B independent of involved signalBoxes (interlockings).
Subschema interlocking
Parents* routeSequences
Children belongsToOperationalPoint (0..*), comboEntry (1..1), comboExit (1..1), containsRoute (1..*), designator (0..*), hasCommand (0..*), hasIndication (0..*), objectName (0..*)
Attributes:
  • priorityRank: Gives the priority of the path in case there are several possible paths between entry and exit. The highest priority is 0. (optional; xs:nonNegativeInteger),

  • elementNumber: element number of the object for internal referencing in the engineering data (optional; xs:nonNegativeInteger),

  • id: unique identifier (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.