Difference between revisions of "IS:state (with length)"

From wiki.railML.org
Jump to: navigation, search
[checked revision][checked revision]
(Set forth Semantics)
Line 13: Line 13:
 
*{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}
 
*{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}
 
*{{Attr|remarks}}: {{railMLType|tElementDescription}}
 
*{{Attr|remarks}}: {{railMLType|tElementDescription}}
 +
|example=The {{IS:Tag|states}} element is optional. In case that no specific {{IS:Tag|state}} is defined for the parent infrastructure element this infrastructure element remains "valid" without any further constraints.<br>{{deu|Das {{IS:Tag|states}} Element ist optional. Für den Fall, dass kein expliziter {{IS:Tag|state}} für das übergeordnete Infrastruktur-Element angegeben ist existieren keine Einschränkungen hinsichtlich der Gültigkeit/Verfügbarkeit dieses Infrastruktur-Elements.}}
 
}}
 
}}

Revision as of 16:36, 4 December 2017

IS:state
 


Scheme description / Schemenbeschreibung / Description du schéma

Position of IS:state in the XML-Tree / Position von IS:state im XML-Baum / position de IS:state dans l’aborescence XML

Multiplicity / Anzahl / Multiplicité

[1..1]

Semantics / Bedeutung / Sémantique

This is to define disabled/enabled infrastructure pieces with a given time frame for a certain length. The length can be specified via the children <from> and <to> (can be left away if the complete object is disabled; must not be used if the object is nonspacial, e.g. <levelCrossing>). The time frame can, optionally, be expressed via operatingPeriodRef.

Attributes of IS:state / Attribute von IS:state / Attributs de IS:state

  • disabled: This attribute is 'true' if the infrastructure piece is somehow disabled.
  • operatingPeriodRef: The temporal frame of the 'state' should be defined in the 'timetable' part of the railML file, using the 'operatingPeriod' element.
  • remarks: This is to further explain the 'state' definition.

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

Best practice & Examples / Empfohlene Anwendung & Beispiele / Bonnes pratiques & exemples

The <states> element is optional. In case that no specific <state> is defined for the parent infrastructure element this infrastructure element remains "valid" without any further constraints.
Das <states> Element ist optional. Für den Fall, dass kein expliziter <state> für das übergeordnete Infrastruktur-Element angegeben ist existieren keine Einschränkungen hinsichtlich der Gültigkeit/Verfügbarkeit dieses Infrastruktur-Elements.

Notes / Anmerkungen / Notes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.

Open issues / Offene Punkte/Pedenzen / Questions ouvertes

Not yet described. / Noch nicht beschrieben. / Pas encore décrit.