IL:relatedLevelCrossingAndState/3.2: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(Updated page IL:relatedLevelCrossingAndState/3.2 using XSD2MediaWiki Converter 1.0.6) |
(Updated page IL:relatedLevelCrossingAndState/3.2 using XSD2MediaWiki Converter 1.1.1) |
||
Line 10: | Line 10: | ||
{{parent|subschema=IL|name=requiresLevelCrossingInState}} | {{parent|subschema=IL|name=requiresLevelCrossingInState}} | ||
|children={{child|subschema=IL|name=refersToLevelCrossing|multiplicity=1..1}} | |children={{child|subschema=IL|name=refersToLevelCrossing|multiplicity=1..1}} | ||
|attributes={{attribut|name=inState|pflicht=1|typ=xs:string|documentation=The state (open/closed) the level crossing has.|werte={{wert|name=closed}}{{wert|name=open}}{{wert|name=unknown}}}}, | |attributes={{attribut|name=inState|pflicht=1|typ=xs:string|documentation=The state (open/closed) the level crossing has.|werte={{wert|name=closed|documentation=position of the level crossing when the safe passage by railway traffic is allowed.}}{{wert|name=open|documentation=position of the level crossing when the crossing of track(s) is safe for road traffic.}}{{wert|name=unknown|documentation=position of the level crossing is not known}}}}, | ||
{{attribut|name=isNegated|pflicht=0|typ=xs:boolean|documentation=The exclusion of a particular state, i.e. everything else that this one.}} | {{attribut|name=isNegated|pflicht=0|typ=xs:boolean|documentation=The exclusion of a particular state, i.e. everything else that this one.}} | ||
}} | }} |
Latest revision as of 12:42, 8 February 2024
Automatic Schemaexport for Element relatedLevelCrossingAndState
Autoexport from the XML-Schema for element IL:relatedLevelCrossingAndState of railML® version 3.2 | |
Documentation | the tuple of references to the level crossing and its state |
Subschema | interlocking |
Parents* | givenState, |
Children | refersToLevelCrossing (1..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. |