IL:hasLevelCrossingType/3.1: Difference between revisions
Jump to navigation
Jump to search
[unchecked revision] | [unchecked revision] |
(Created page with "<noinclude>Automatic Schemaexport for Element '''hasLevelCrossingType'''</noinclude> {{Schemaexport |element=hasLevelCrossingType |subschema=interlocking |subschema_slug=IL |d...") |
No edit summary |
||
Line 12: | Line 12: | ||
{{attribut|name=hasBarrier|pflicht=0|typ=xs:boolean|documentation=The level crossing may be equipped with barriers for road traffic.}}, | {{attribut|name=hasBarrier|pflicht=0|typ=xs:boolean|documentation=The level crossing may be equipped with barriers for road traffic.}}, | ||
{{attribut|name=hasTrafficWarning|pflicht=0|typ=xs:boolean|documentation=The level crossing may be equipped with audible/optical means to allow warning of road traffic.}}, | {{attribut|name=hasTrafficWarning|pflicht=0|typ=xs:boolean|documentation=The level crossing may be equipped with audible/optical means to allow warning of road traffic.}}, | ||
{{attribut|name=id|pflicht=0|typ=xs:ID|documentation=unique identifier|patterns={{pattern|(urn:uuid:)?[0-9a-fA-F] | {{attribut|name=id|pflicht=0|typ=xs:ID|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}\}}}}} | ||
}} | }} |
Revision as of 18:19, 23 December 2019
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 (), 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. |