IS:uptime: Difference between revisions
Jump to navigation
Jump to search
| [checked revision] | [checked revision] |
(Einige ''None'') |
(constraints added) |
||
| Line 24: | Line 24: | ||
|constraints = | |constraints = | ||
* {{Attr|from}} {{XsdType|time}}, mandatory | * {{Attr|from}}: {{XsdType|time}}, mandatory | ||
* {{Attr|until}} {{XsdType|time}}, mandatory | * {{Attr|until}}: {{XsdType|time}}, mandatory | ||
* {{Attr|mode}} mandatory | * {{Attr|mode}}: {{railMLType|tOcpManMode}}; mandatory | ||
|backHome = IS:elements | |backHome = IS:elements | ||
}} | }} | ||
Revision as of 20:36, 17 January 2017
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.
Attributes of uptime / Attribute von uptime
- from
- until
- mode Possible values are:
- manned
- unmanned
- off
- 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
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.