Difference between revisions of "Template:StartEndCon"

From wiki.railML.org
Jump to: navigation, search
[checked revision][checked revision]
 
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.|status=approved|proposed=2018-11-12|approved=2019-03-21|id=TT:1}}</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.|status=approved|proposed=2018-11-12|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 14:38, 9 July 2019

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.
 
Proposed on November 12th 2018
Approved on March 21st 2019
Please, recognize our guidelines on semantic constraints