Home » railML newsgroups » railML.infrastructure » [railML2] extension suggestion for the element <state> for open time period
Re: [railML2] extension suggestion for the element <state> for open time period [message #2720 is a reply to message #2699] Thu, 20 May 2021 12:53 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
This depend on the UC for the attribute! Our initial request is for open timeframes for an infrastructures state where you cannot reference an <operatingPeriod> (they need to be closed). Here it would make sense to have both date and time together in one attribute as suggested.

But note when you use @operatingPeriodRef for closed timeframes within an <operatingPeriod> or for cyclical day occurrences with the usage of operatingPeriod<operatingDay> these elements do not contain time attributes and are supplemented with the three attributes introduced in railML2.4: <state>@startTime @endTime and @endDayOffset.

If your suggestion is to keep (not deprecating) these three attributes and add new the two attributes @startDateTime and @endDateTime this is fine for us. Note a very clear semantic constraint should be written when to use @startTime and when to use @startDateTime in the wiki.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: railML 2.3 infrastructure extension proposal line sections
Next Topic: [railML2] modeling of a car ramp
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue May 14 22:48:51 CEST 2024