IS:trainProtectionElementGroup: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(template:external)
Line 8: Line 8:
*{{Attr|id}}: XML-file-wide unique identity is required for later referencing that element
*{{Attr|id}}: XML-file-wide unique identity is required for later referencing that element
*{{Attr|name}}: for typical, specific abbreviations, used in different systems with the same understanding
*{{Attr|name}}: for typical, specific abbreviations, used in different systems with the same understanding
*{{Attr|description}}: should be interpreted in its elements' context, substantiates the name
*{{Attr|description}}: should be interpreted in its elements' context, substantiates the name{{human}}
*{{Attr|xml:lang}}: natural language identification according to {{external|http://www.w3.org/TR/xml/#sec-lang-tag}}
*{{Attr|xml:lang}}: natural language identification according to {{external|http://www.w3.org/TR/xml/#sec-lang-tag}}
|constraints=
|constraints=

Revision as of 16:03, 5 October 2018


IS:trainProtectionElementGroup
 


Scheme description / Schemenbeschreibung

Position of IS:trainProtectionElementGroup in the XML-Tree / Position von IS:trainProtectionElementGroup im XML-Baum

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

Missinginformation.png In this article there is information missing with respect to the semantics. Please help improving the railML® wiki by filling the gaps. Possibly, you will find further details on the discussion pageFerri Leberl (talk) 14:57, 12 January 2017 (CET)

Attributes of IS:trainProtectionElementGroup / Attribute von IS:trainProtectionElementGroup

  • id: XML-file-wide unique identity is required for later referencing that element
  • name: for typical, specific abbreviations, used in different systems with the same understanding
  • description: should be interpreted in its elements' context, substantiates the name
💡 Please take into account our references to human-intepretable data fields.

Bitte berücksichtigen Sie unsere Hinweise zu menschen-intepretierbaren Datenfeldern.

Syntactic Constraints / Syntaktische Beschränkungen

Best practice & Examples / Empfohlene Anwendung & Beispiele

Not yet described. / Noch nicht beschrieben.

Notes / Anmerkungen

Not yet described. / Noch nicht beschrieben.

Open issues / Offene Punkte/Pendenzen

Not yet described. / Noch nicht beschrieben.