IS:detector/3.2: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Updated page IS:detector/3.2 using XSD2MediaWiki Converter 1.0.6)
(Updated page IS:detector/3.2 using XSD2MediaWiki Converter 1.1.1)
Line 6: Line 6:
|version=3.2
|version=3.2
|parent={{parent|subschema=IS|name=detectors}}
|parent={{parent|subschema=IS|name=detectors}}
|children={{child|subschema=RTM|name=areaLocation|multiplicity=0..*}}, {{child|subschema=CO|name=designator|multiplicity=0..*}}, {{child|subschema=CO|name=external|multiplicity=0..*}}, {{child|subschema=IS|name=gmlLocations|multiplicity=0..*}}, {{child|subschema=RTM|name=isValid|multiplicity=0..*}}, {{child|subschema=RTM|name=linearLocation|multiplicity=0..*}}, {{child|subschema=CO|name=linkedWith|multiplicity=0..*}}, {{child|subschema=CO|name=name|multiplicity=0..*}}, {{child|subschema=IS|name=networkLocation|multiplicity=0..*}}, {{child|subschema=RTM|name=spotLocation|multiplicity=0..*}}, {{child|subschema=IS|name=typeDesignator|multiplicity=0..*}}
|children={{child|subschema=RTM|name=areaLocation|multiplicity=0..*}}, {{child|subschema=generic|name=designator|multiplicity=0..*}}, {{child|subschema=generic|name=external|multiplicity=0..*}}, {{child|subschema=IS|name=gmlLocations|multiplicity=0..*}}, {{child|subschema=RTM|name=isValid|multiplicity=0..*}}, {{child|subschema=RTM|name=linearLocation|multiplicity=0..*}}, {{child|subschema=generic|name=linkedWith|multiplicity=0..*}}, {{child|subschema=generic|name=name|multiplicity=0..*}}, {{child|subschema=IS|name=networkLocation|multiplicity=0..*}}, {{child|subschema=RTM|name=spotLocation|multiplicity=0..*}}, {{child|subschema=IS|name=typeDesignator|multiplicity=0..*}}
|attributes={{attribut|name=detects|pflicht=0|typ=xs:string|documentation=type of hazard that is detected by the detector|werte={{wert|name=avalanche}}{{wert|name=camels}}{{wert|name=reindeer}}{{wert|name=rocks}}{{wert|name=sand}}|patterns={{pattern|other:\w{2,}}}}},
|attributes={{attribut|name=detects|pflicht=0|typ=xs:string|documentation=type of hazard that is detected by the detector|werte={{wert|name=avalanche}}{{wert|name=camels}}{{wert|name=reindeer}}{{wert|name=rocks}}{{wert|name=sand}}|patterns={{pattern|other:\w{2,}}}}},
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|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}\}}}}}
{{attribut|name=id|pflicht=1|typ=xs:string|documentation=the identifier of the object; this can be either of type xs:ID or UUID|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 12:39, 8 February 2024

Automatic Schemaexport for Element detector

Autoexport from the XML-Schema for element IS:detector of railML® version 3.2
Documentation This element is not documented in the schema!
Subschema infrastructure
Parents* detectors
Children areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), linkedWith (0..*), name (0..*), networkLocation (0..*), spotLocation (0..*), typeDesignator (0..*)
Attributes:
  • detects: type of hazard that is detected by the detector (optional; xs:string; patterns: other:\w{2,})
Possible values:
  • avalanche
  • camels
  • reindeer
  • rocks
  • sand,

  • id: the identifier of the object; this can be either of type xs:ID or UUID (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.