IL:hasLevelCrossingType/3.1: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [checked revision] |
No edit summary |
(Updated page IL:hasLevelCrossingType/3.1 using XSD2MediaWiki Converter 1.0.2) |
||
Line 7: | Line 7: | ||
|version=3.1 | |version=3.1 | ||
|parent={{parent|subschema=IL|name=usesTypes}} | |parent={{parent|subschema=IL|name=usesTypes}} | ||
|children={{Any}}, {{child|subschema=CO|name=designator|multiplicity=0..1}} | |children={{Any|multiplicity=0..*}}, {{child|subschema=CO|name=designator|multiplicity=0..1}} | ||
|attributes={{attribut|name=controlType|pflicht=1|typ=xs:string|documentation=The classification of the control type w.r.t. the interlocking operation.|werte={{wert|name=autonomous}}{{wert|name=fullControlled}}{{wert|name=halfControlled}}}}, | |attributes={{attribut|name=controlType|pflicht=1|typ=xs:string|documentation=The classification of the control type w.r.t. the interlocking operation.|werte={{wert|name=autonomous}}{{wert|name=fullControlled}}{{wert|name=halfControlled}}}}, | ||
{{attribut|name=allowsLocalOperation|pflicht=0|typ=xs:boolean|documentation=The level crossing may have a control unit which allows local operation from the field.}}, | {{attribut|name=allowsLocalOperation|pflicht=0|typ=xs:boolean|documentation=The level crossing may have a control unit which allows local operation from the field.}}, |
Latest revision as of 14:22, 24 January 2020
Automatic Schemaexport for Element hasLevelCrossingType
Autoexport from the XML-Schema for element IL:hasLevelCrossingType of railML® version 3.1 | |
Documentation | Classification of basic level crossing types. |
Subschema | interlocking |
Parents* | usesTypes |
Children | any (0..*), designator (0..1) |
Attributes:
| |
*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. |