IS:state (with length): Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
No edit summary
m (Syntax)
Line 10: Line 10:
*{{Attr|remarks}}: This is to further explain the 'state' definition.
*{{Attr|remarks}}: This is to further explain the 'state' definition.
|constraints=
|constraints=
*{{Attr|disabled}}: {{XsdType:boolean}}
*{{Attr|disabled}}: {{XsdType|boolean}}
*{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}
*{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}
*{{Attr|remarks}}: {{railMLType|tElementDescription}}
*{{Attr|remarks}}: {{railMLType|tElementDescription}}
}}
}}

Revision as of 20:56, 28 February 2017


IS:state
 


Scheme description / Schemenbeschreibung

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

Multiplicity / Anzahl

[1..1]

Semantics / Bedeutung

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

Attributes of IS:state / Attribute von 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

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.