| Re: [railML3] meaning and purpose of speedSection.isTemporary is unclear [message #3015 is a reply to message #3009] |
Tue, 14 June 2022 00:08  |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Jorgen,
thank you very much for bringing up this question about the time dimension of speed restrictions. The idea, to model a TSR using the element <speedSection>@isTemporary="true" sounds good and I am happy about any practical example that could be added in our wiki.
But what about the potential overlapping with "isValid"?
The child element <isValid> comes from the RailTopoModel and therefore it is available for all functional infrastructure elements (because they derive from RTM class NetEntity). The element <isValid> contains two attributes - @from and @to - which refer to dates (xs:date).
Apart from this, there exists the view <infrastructureStates> inside domain <infrastructure>. An <infrastructureState> defines the state using attribute @value (e.g. "operational"). This state can be linked with a time dimension using the child element <validityTime>.
The task for us in one of our next working group meetings should be to clarify which approach to use for which purpose. Until then, any comment is highly appreciated...
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
