IS:state

From wiki.railML.org
Jump to: navigation, search

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

  • Children: None

Multiplicity / Anzahl / Multiplicité

[1..1]

Semantics / Bedeutung / Sémantique

This is to define disabled/enabled infrastructure pieces with a given time frame.

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

  • disabled: This attribute is 'true' if the infrastructure piece is somehow disabled.
  • status: (introduced with version 2.4) defines the status of the infrastructure element from perspective of its availability
    Possible values are:
  • conceptual: The construction or commissioning of the element is planned for the medium or long term. However, there are still no concrete (planning) activities for the construction of the element beyond the preliminary planning and cost estimation.
  • planned: The construction or commissioning of the element is planned concretely and at short notice or concrete planning activities for the construction take place, e.g. design, approval or implementation planning, cost calculation, award of contracts. It is not normally possible to use the element.
  • operational: The element is operational and can be used regularly.
  • disabled: The element is currently not usable, switched off or deactivated and therefore cannot be used regularly. However, it can be put back into operation at short notice without further construction, acceptance or approval activities.
  • closed: The element is no longer available, removed, dismantled, or no longer exists. Planning, construction or commissioning activities are absolutely necessary for recommissioning.
  • other:anything Any value that does not fit any value from the previous enumeration list, fulfilling the constraint: at minimum two characters, whitespace is not allowed.
  • operatingPeriodRef: The start date (or start dates if its a periodic state) should be defined in the 'timetable' part of the railML file, using the 'operatingPeriod' element.
  • startTime: (introduced with version 2.4) The start time of the 'state'.
  • endTime: (introduced with version 2.4) The end time of the 'state'.
  • endDayOffset: (introduced with version 2.4) Duration of the 'state', counted in midnight overruns.
  • remarks: This is to further explain the 'state' definition.
Birne.png Please be aware that this attribute is only intended to forward simple remarks/explanations from one end-user to another end-user. It is not to be used to contain computer-processable data, nor shall it be parsed by programmes in any way. In case of semantical overlaps or discrepancies to machine processable file contents, any machine processable contents have priority over possible human interpretable contents. However, the attribute may be used to transmit complementary details to machine processable parameters.

Bitte, berücksichtigen Sie, dass dieses Attribut nur für einfache Kommentare/Erklärungen von Endbenutzer zu Endbenutzer bestimmt ist. Es ist nicht für maschineninterpretierbare Daten gedacht und wird nicht geparst werden. Im Falle semantischer Überschneidungen oder Widersprüche zu maschinenlesbaren Inhalten wird diesen der Vorzug gegenüber durch Menschen lesbaren gegeben. Allerdings können durch Menschen lesbare Felder für Ergänzungen zu maschinenlesbaren verwendet werden.

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

Semantic Constraints / Semantische Beschränkungen / Contraintes semantiques

Private-cloud-icon.png Proposed semantic constraint:
Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods.
Proposed on 2018-11-12
Please, recognize dev:Semantic Constraints

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.