IS:typeDesignator: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page IS:typeDesignator using XSD2MediaWiki Converter 1.0.6)
 
(added link to forum)
 
Line 13: Line 13:
=={{Additional Information}}==
=={{Additional Information}}==
==={{Notes}}===
==={{Notes}}===
see https://www.railml.org/forum/index.php?t=msg&goto=2969& for context
==={{Open issues}}===
==={{Open issues}}===

Latest revision as of 11:35, 3 September 2024

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element IS:typeDesignator of railML® version 3.2
Documentation external identifier of the type of the entity
Subschema infrastructure
Parents* balise,

baliseGroup, border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tunnelGateIS, underCrossing, weightLimit

Children None
Attributes:
  • description: Human-readable, more detailed description as addition to the entry. It should give additional explanations or hints to the contents of this element. Not intended for machine interpretation, please see our notice on human interpretable data fields. (optional; xs:string),

  • entry: the designator of the type in the specified rule book (optional; xs:string),

  • rulebook: name of a rule book where the designator entry can be found (obligatory; xs:string)
*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.


 

This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

see https://www.railml.org/forum/index.php?t=msg&goto=2969& for context

Open Issues