Introduction
Documentation
Syntax
|
|
| Description
|
This element is not documented in the schema!
|
| Subschema
|
generic
|
| Parents*
|
validity
|
| Children
|
None
|
Attributes:
- from: specifies the start date and time for the enclosing validity definition. (optional;
xs:dateTime),
- to: specifies the end date and time for the enclosing validity definition. (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.
|
This element does not appear in railML® 3.2 within the Generic subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.This element does not appear in railML® 3.1 within the Generic subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
Introduced with version 3.3.
Semantics
|
Proposed 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 within the same enclosing element.
Proposed on 15 January 2024
FIXME Forum missing
Please, recognize our guidelines on semantic constraints
|
|
Best Practice / Examples
Please refer to <elementState> and Dev:Defining temporal availability of infrastructure elements and speed profiles for examples.
Additional Information
Notes
Open Issues
