IS:uptime

uptime
 

Scheme description / Schemenbeschreibung / Description du schéma

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

• Parent: <propOperational>
• Children: None

Multiplicity / Anzahl / Multiplicité

[0..∞]

Semantics / Bedeutung / Sémantique

The element <uptime> defines daytime constraints for the current ocp.
 
Please, be aware of the semantic constraint(s)!

Attributes of uptime / Attribute von uptime / Attributs de uptime

• from is the start time for the given mode. When referring to midnight at the beginning of the day, please use "00:00:00".
• until is the end time for the given mode. When referring to midnight at the end of the day, please use "24:00:00".
• mode Possible values are:

• manned: The <ocp> is operational/usable and staffed with IM's personnel ready for operation on site (in the area of the <ocp>).
• unmanned: The <ocp> is operational/usable and not staffed with on site personnel by the IM. Even if the <ocp> is not controlled or is remote controlled by any staff of the IM and there is no staff of the IM available in the area of the <ocp>.
• off: The <ocp> is temporarily not operational/usable. No information about local staff is given by this value.

Please note that a long-term non-defined or permanent disabling of an <ocp> will be expressed via <ocp><propOther><state>@status={disabled|closed}.

• 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. Please, apply Dev:usingAny accordingly.

• operatingPeriodRef: (introduced with version 2.5) reference to the operating period defined in the timetable part
• endDayOffset: (introduced with version 2.5) define an offset greater than 0 if the end of the time span is not on the same day like the begin of the time span

Syntactic Constraints / Syntaktische Beschränkungen / Contraintes syntactiques

• from: xs:time, mandatory
• until: xs:time, mandatory
• mode: union of (restriction of xs:string, tOtherEnumerationValue); tOtherEnumerationValue is an arbitrary string starting with 'other:' followed by at minimum two characters, white space not allowed for extending railML enumeration lists; mandatory
• operatingPeriodRef: tGenericRef (xs:IDREF); optional
• endDayOffset: xs:nonNegativeInteger; optional

Semantic Constraints / Semantische Beschränkungen / Contraintes semantiques

Proposed Semantic Constraint "IS:008": An <ocp> with <propOperational>@operationalType=blockSignal shall not have @mode=manned (as a manned blockSignal shall be modelled in railML® 2.x as a blockPost). Proposed on February 28th 2020 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

Proposed Semantic Constraint "IS:009": An <ocp> with attribute <propOperational>@operationalType=stoppingPoint shall not have @mode=manned (as a stoppingPoint has no operational usage and therefore no operational staff by the IM). Proposed on February 28th 2020 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

Proposed Semantic Constraint "IS:010": An enumeration of several time periods by @from and @until for one <ocp> shall not overlap so that for every time there shall be a unique status of <uptime>. Proposed on February 28th 2020 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints

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

As from and until are mandatory, a mode for the whole day must be specified from="00:00:00" until="24:00:00".

Notes / Anmerkungen / Notes

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

Open issues / Offene Punkte/Pendenzen / Questions ouvertes

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