| [railML3] <border> of type infrastructureManager [message #3149] |
Thu, 26 October 2023 10:10  |
Larissa Zhuchyi
Messages: 31
Registered: November 2022
|
Member |
|
|
Dear all
Currently railML ontology is under development [1] aiming at the harmonization (transformation) of railML2 and railML3. This forum post is related to <border> of type infrastructureManager of railML3.
Intuitively <ownerChange> of railML2 should be mapped to <border> of railML3. The problem is that <ownerChange> of railML2 has the additional attribute @infrastructureManagerRef to reference presumably following owner of the railway tracks.
In railML3 <border> of type infrastructureManager misses this reference. Thus when transforming railML2 to railML3 information on @infrastructureManagerRef is lost.
Even when not speaking about railML2 to railML3 mapping, railML3 data on <border> of type infrastructureManager without references seems incomplete.
railML.org would be grateful if you could communicate your thoughts on the following points:
(1) should railML 3.3 be extended by @infrastructureManagerRef for <border> element?
(2) do you see any other ways (implicit) to refer to infrastructure manager from <border> of type infrastructureManager in railML3?
[1] https://www.railml.org/en/public-relations/news/reader/railm l-ontology-subgroup-started.html
Sincerely,
Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
|
|
|
|
Members
Search
Help
Login
Home
