This element does not appear in railML® 3.2 within the CO subschema. It is available only in railML® . Do not hesitate to contact railML.org for further questions.
CO:validityTime:period: Difference between revisions
Jump to navigation
Jump to search
[checked revision] | [checked revision] |
m (added semantic constraint) |
(changed status of semantic constraint to approved) |
||
Line 11: | Line 11: | ||
{{semcon|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. | {{semcon|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. | ||
|status= | |status=approved|proposed=2024-01-15|approved=2024-04-15 | ||
|id=IS:001}} | |id=IS:001}} | ||
{{importComment}} | {{importComment}} |
Latest revision as of 13:44, 18 April 2024
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element CO:validityTime:period of railML® version 3.1 | |
Documentation | This element is not documented in the schema! |
Subschema | common |
Parents* | validityTime |
Children | None |
Attributes:
| |
*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
Removed with version 3.2.
Semantics
|