Template:StartEndCon: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Semantic constraint approved in TT developers telco on 2019-03-21)
(added link to https://wiki2.railml.org/wiki/Dev:Defining_temporal_availability_of_infrastructure_elements_and_speed_profiles)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<includeonly> {{semcon|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods.|2019-03-21}}</includeonly><noinclude>
<includeonly>{{semcon|Any '''starting time stamp''' (as it may result e.g. from a combination of ''startDate'' and ''startTime'') shall be lower or equal any '''ending time stamp''' (e.g. ''endDate'') if both are given. Must not overlap with other validity periods. See also https://wiki2.railml.org/wiki/Dev:Defining_temporal_availability_of_infrastructure_elements_and_speed_profiles|status={{{status|approved}}}|proposed={{{proposed|2018-11-12}}}|approved={{{approved|2019-03-21}}}|id=TT:001}}</includeonly><noinclude>
==Usage==
==Usage==
This template depicts a [[dev:Semantic Constraints|semantic constraint]] refering to [[IS:designator#Examples_concerning_startDate_and_endDate|these consistecy requirements for time spans]].
This template depicts a [[dev:Semantic Constraints|semantic constraint]] refering to [[IS:designator#Examples_concerning_startDate_and_endDate|these consistecy requirements for time spans]].

Latest revision as of 19:45, 12 April 2024

Usage

This template depicts a semantic constraint refering to these consistecy requirements for time spans.

Arguments

None

Dependencies

Uses template:note

Examples

{{StartEndCon}}

delivers

Private-cloud-icon.png Semantic Constraint "TT:001":
 
Any starting time stamp (as it may result e.g. from a combination of startDate and startTime) shall be lower or equal any ending time stamp (e.g. endDate) if both are given. Must not overlap with other validity periods. See also https://wiki2.railml.org/wiki/Dev:Defining_temporal_availability_of_infrastructure_elements_and_speed_profiles
 
Proposed on November 12th 2018
Approved on March 21st 2019
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints