| Re: [railML2] extension suggestion for the element <state> for open time period [message #2699 is a reply to message #2676] |
Fri, 09 April 2021 18:05   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
time aspects in infrastructure states are an important topic indeed. Therefore, I very much appreciate any comments and ideas from the community on our way to identify an appropriate solution.
My proposal: instead of defining single attributes for day and time, let's focus on only two new attributes for a state:
* @startDateTime (xs:dateTime) to specify begin date AND time for the state
* @endDateTime (xs:dateTime) to specify end date AND time for the state
xs:dateTime is specified in the pattern: "YYYY-MM-DDThh:mm:ss" (see [1]).
Both attributes shall be optional meeting your requirement of having "open time spans".
I am curios to hear from the community about their ideas...
[1] https://www.w3schools.com/XML/schema_dtypes_date.asp
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
