| Re: [railML3] Refactoring of states (e.g. infrastructure states) [message #3375 is a reply to message #3373] |
Thu, 24 October 2024 18:39   |
Thomas Nygreen
Messages: 89
Registered: March 2008
|
Member |
|
|
Dear Dominik,
The conclusion of the coordinators is that netElement, gradientCurve and horizontalCurve are abstract entities that do not take on different states. We will therefore not include elementState on these in railML 3.3. A netElement is not a track, it is an abstract part of the topology, on which one can place tracks and other infrastructure entities. The netElement (or gradientCurve or horizontalCurve) itself is not "operational", "closed" or "dismantled", but any track or other entity positioned along the netElement can have a state, allowing you to model the use case you describe with railML 3.3.
netElement, gradientCurve and horizontalCurve support basic RTM validity, so one is able to specify a start and/or end of availability/applicability.
Please let us know if there is anything we have overlooked in your use case.
We will add start and end of validity for organizationalUnit.
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
