IS:state (with length): Difference between revisions
| [checked revision] | [checked revision] |
(Inhalte zu railML 2.4 verborgen) |
(adding new Attribute @status) |
||
| Line 7: | Line 7: | ||
For information on defining the time and duration of the 'state', see [[Dev:Defining temporal availability of infrastructure elements and speed profiles|Defining temporal availability of infrastructure elements and speed profiles]] | For information on defining the time and duration of the 'state', see [[Dev:Defining temporal availability of infrastructure elements and speed profiles|Defining temporal availability of infrastructure elements and speed profiles]] | ||
|inheritedAttributes=''None'' | |inheritedAttributes=''None'' | ||
|ownAttributes= | |ownAttributes= | ||
*{{Attr|disabled}}: This attribute is 'true' if the infrastructure piece is somehow disabled. | *{{Attr|disabled}}: This attribute is 'true' if the infrastructure piece is somehow disabled. | ||
*{{Attr|status}}: {{Intro|2.4}} defines the status of the infrastructure element from perspective of its availability | |||
*{{Attr|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.{{unlock|2.3| | *{{Attr|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.{{unlock|2.3| | ||
*{{Attr|startTime}}: {{Intro|2.4}} The start time of the 'state'. | *{{Attr|startTime}}: {{Intro|2.4}} The start time of the 'state'. | ||
| Line 14: | Line 16: | ||
*{{Attr|endDayOffset}}: {{Intro|2.4}} Duration of the 'state', counted in midnight overruns.}} | *{{Attr|endDayOffset}}: {{Intro|2.4}} Duration of the 'state', counted in midnight overruns.}} | ||
*{{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|status}}: {{railMLType|tInfrastructureStatus}} | |||
*{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}{{unlock|2.3| | *{{Attr|operatingPeriodRef}}: {{railMLType|tGenericRef}}{{unlock|2.3| | ||
*{{Attr|startTime}}: {{XsdType|time}} | *{{Attr|startTime}}: {{XsdType|time}} | ||
Revision as of 11:27, 2 October 2018
IS:state
Schema description / Schemabeschreibung
Position of IS:state in the XML-Tree / Position von IS:state im XML-Baum
Multiplicity / Anzahl
Semantics / Bedeutung
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>).
For information on defining the time and duration of the 'state', see Defining temporal availability of infrastructure elements and speed profiles
Attributes of IS:state / Attribute von 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
- 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.
Syntactic Constraints / Syntaktische Beschränkungen
- disabled: xs:boolean
- status: union of (restriction of xs:string, tOtherEnumerationValue)
- operatingPeriodRef: xs:IDREF
- startTime: xs:time
- endTime: xs:time
- endDayOffset: xs:nonNegativeInteger
- remarks: xs:string
Best practice & Examples / Empfohlene Anwendung & Beispiele
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
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.