IS:switchIS/3.1

Automatic Schemaexport for Element switchIS

Autoexport from the XML-Schema for element IS:switchIS of railML® version 3.1 UML-visualization of IS
Documentation	This element is not documented in the schema!
Subschema	infrastructure
Parents*	switchesIS
Children	any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), leftBranch (0..1), linearLocation (0..*), name (0..*), networkLocation (0..*), rightBranch (0..1), spotLocation (0..*), straightBranch (0..2), turningBranch (0..2)
Attributes: belongsToParent: reference to the one an only parent switch of this switch (to be used at switch crossings) (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}\}), type: type of the switch (optional; xs:string) Possible values: doubleSwitchCrossing insideCurvedSwitch ordinarySwitch outsideCurvedSwitch singleSwitchCrossing, continueCourse: defines the switch main track route (as seen from begin of switch, application direction) (optional; xs:string) Possible values: right left, branchCourse: defines the switch branching track route (as seen from begin of switch, application direction) (optional; xs:string) Possible values: right left, basedOnTemplate: reference to a generic switch (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}\}), 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.