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 #2723 is a reply to message #2720] Fri, 21 May 2021 13:21 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Torben,

thank you for your feedback. I updated the Trac ticket #394 [1] with a railML 2.5 solution proposal including semantic rules for the different scenarios of usage. The rules are:

* use @startDateTime and/or @endDateTime to specify an open or closed timespan for the state's validity that is not linked with an <operatingPeriod>
* use @startTime and/or @endTime (and @endDayOffset) to specify an open or closed timespan for the state linked with an <operatingPeriod> where @startDate and/or @endDate are defined

Are these rules sufficient?

[1] https://trac.railml.org/ticket/394

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

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: Wed May 15 00:02:19 CEST 2024