CO:validityTime:period

Documentation

Syntax

This element does not appear in railML^® 3.3 within the CO subschema. It is available only in railML^® 3.1.
There exists an element <generic:validityTime:period> that might have replaced or preceded it. Do not hesitate to contact railML.org for further questions.

This element does not appear in railML^® 3.2 within the CO subschema. It is available only in railML^® 3.1.
There exists an element <generic:validityTime:period> that might have replaced or preceded it. Do not hesitate to contact railML.org for further questions.

Autoexport from the XML-Schema for element CO:validityTime:period of railML® version 3.1      UML-visualization of CO
Documentation	This element is not documented in the schema!
Subschema	common
Parents*	validityTime
Children	None
Attributes: from: This attribute is not documented in the schema! (optional; xs:dateTime), to: This attribute is not documented in the schema! (optional; xs:dateTime)
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.

Changes 3.1→3.2

There exists an overview of all changes between railML^® 3.1 and railML^® 3.2 on page Dev:Changes/3.2.

Removed with version 3.2.

Semantics

Semantic Constraint "IS:001":   Starting time stamp (e.g. "from") shall be lower or equal any ending time stamp (e.g. "to") if both are given. Must not overlap with other validity periods.   Proposed on January 15th 2024 Approved on April 15th 2024 FIXME: add Link to discussion! Please, recognize our guidelines on semantic constraints