IS:uptime: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
(Specifying use of midnight values) |
(Best practice for whole days) |
||
Line 38: | Line 38: | ||
{{semcon|status=proposed|proposed=2020-02-28|id=IS:009|1=An {{Tag|IS|ocp}} with attribute {{Tag|IS|propOperational|@=operationalType}}=''stoppingPoint'' shall not have {{@|mode}}=''manned'' (as a ''stoppingPoint'' has no operational usage and therefore no operational staff by the IM).}} | {{semcon|status=proposed|proposed=2020-02-28|id=IS:009|1=An {{Tag|IS|ocp}} with attribute {{Tag|IS|propOperational|@=operationalType}}=''stoppingPoint'' shall not have {{@|mode}}=''manned'' (as a ''stoppingPoint'' has no operational usage and therefore no operational staff by the IM).}} | ||
{{semcon|status=proposed|proposed=2020-02-28|id=IS:010|1=An enumeration of several time periods by {{@|from}} and {{@|until}} for one {{Tag|IS|ocp}} shall not overlap so that for every time there shall be a unique status of {{Tag|IS|uptime}}.}} | {{semcon|status=proposed|proposed=2020-02-28|id=IS:010|1=An enumeration of several time periods by {{@|from}} and {{@|until}} for one {{Tag|IS|ocp}} shall not overlap so that for every time there shall be a unique status of {{Tag|IS|uptime}}.}} | ||
|example=As {{Attr|from}} and {{Attr|until}} are mandatory, a {{Attr|mode}} for the whole day must be specified <code>from="00:00:00" until="24:00:00"</code>. | |||
}} | }} |
Revision as of 13:46, 8 March 2021
uptime
Scheme description / Schemenbeschreibung
Position of uptime in the XML-Tree / Position von uptime im XML-Baum
- Parent: <propOperational>
- Children: None
Multiplicity / Anzahl
Semantics / Bedeutung
The element <uptime> defines daytime constraints for the current ocp.
Please, be aware of the semantic constraint(s)!
Attributes of uptime / Attribute von 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.
Syntactic Constraints / Syntaktische Beschränkungen
- 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
Semantic Constraints / Semantische Beschränkungen
|
|
|
Best practice & Examples / Empfohlene Anwendung & Beispiele
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
Not yet described. / Noch nicht beschrieben.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.