RTM:isValid

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element RTM:isValid of railML® version 3.2
Documentation

period for which a certain information object is valid in respect to availability for usage for train operations.

Subschema

Rtm4railml

Parents*
Children

None

Attributes:

  • from: defines the point in time where the object in question is available for usage for train operations. (optional; xs:date),

  • to: defines the point in time where the object in question is no longer available for functional usage. (optional; xs:date)
*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.


 

Autoexport from the XML-Schema for element RTM:isValid of railML® version 3.1
Documentation

This element is not documented in the schema!

Subschema

Rtm4railml

Parents*
Children

None

Attributes:

  • from: This attribute is not documented in the schema! (optional; xs:date),

  • to: This attribute is not documented in the schema! (optional; xs:date)
*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

The element documentation has been changed.

The parents have changed.

The attributes have been changed.

Semantics

Private-cloud-icon.png 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


Best Practice / Examples

Additional Information

Notes

Open Issues