IL:key/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Updated page IL:key/3.2 using XSD2MediaWiki Converter 1.0.6)
(Updated page IL:key/3.2 using XSD2MediaWiki Converter 1.1.1)
 
(One intermediate revision by the same user not shown)
Line 7: Line 7:
|version=3.2
|version=3.2
|parent={{parent|subschema=IL|name=keys}}
|parent={{parent|subschema=IL|name=keys}}
|children={{child|subschema=CO|name=designator|multiplicity=0..*}}, {{child|subschema=IL|name=isPhysical|multiplicity=0..1}}
|children={{child|subschema=Generic|name=designator|multiplicity=0..*}}, {{child|subschema=IL|name=isPhysical|multiplicity=0..1}}
|attributes={{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}\}}}}}
|attributes={{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 15:47, 17 May 2024

Automatic Schemaexport for Element key

Autoexport from the XML-Schema for element IL:key of railML® version 3.2
Documentation

An ancillary element used for operation of a specific locking device.

Subschema

interlocking

Parents*
Children

designator (0..*), isPhysical (0..1)

Attributes:

  • 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.