Home » railML newsgroups » railML.infrastructure » [railML3] Semantic constraints for linking the topology with the positioning systems (Making sure the schema is used the way it is meant)
[railML3] Semantic constraints for linking the topology with the positioning systems [message #3448] Mon, 27 January 2025 15:57 Go to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 57
Registered: November 2022
Member
In railML 3.2 and railML 3.3 schema allows to link the topology to the positioning systems: linearPositioningSystem and geometricPositioningSystem.

This is done via the tag associatedPositioningSystem which specifies a reference to one of these positioning systems (@positioningSystemRef) In a substructure of associatedPositioningSystem linearCoordinates or geometricCoordinates can be specified. These of course only make sense if the positioning system specified on the level of the associatedPositioningSystem matches the specified type of coordinate.

In order to emphasize this we are considering semantic constraints to be introduced.

Please let know railML.org in case you do not agree with them until end of February 2025 otherwise if the working groups agree then it will be accepted and affect future certifications.

Thanks in advance!

railML 3.2

if associatedPositioningSystem/@positioningSystemRef refers to geometricPositioningSystem (reference is mandatory according to the positioning approach) then children netElement/associatedPositioningSystem/intrinsicCoordinate/l inearCoordinate are not allowed

if associatedPositioningSystem/@positioningSystemRef refers to linearPositioningSystem (reference is mandatory according to the positioning approach) then children netElement/associatedPositioningSystem/intrinsicCoordinate/g eometricCoordinate are not allowed

railML 3.3

if associatedPositioningSystem/@positioningSystemRef refers to geometricPositioningSystem then children netElement/associatedPositioningSystem/intrinsicCoordinate/l inearCoordinate are not allowed

if associatedPositioningSystem/@positioningSystemRef refers to linearPositioningSystem then children netElement/associatedPositioningSystem/intrinsicCoordinate/g eometricCoordinate are not allowed

Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Fri, 28 February 2025 09:21]

Report message to a moderator

Re: [railML3] Semantic constraints for linking the topology with the positioning systems [message #3566 is a reply to message #3448] Wed, 16 April 2025 13:37 Go to previous message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 57
Registered: November 2022
Member
Dear all

During the presentation of the forum post at the railML SCTP working group meeting from 2025-03-28 it became clear that the wording of the above suggested semantic constraints is hard to understand.

Basically, the suggested semantic constraints mean that the netElement shall be positioned using coordinates of the same kind as the positioning system referenced from associatedPositioningSystem of this netElement.

Additionally, railML.org provides the valid and invalid examples (against suggested constraint) for linearCoordinate [1].

The examples refer to the positioning approach, which can be found by the link [2].

Interpretation for geometricCorrdinate is analogous.

[1] https://cloud.railml.org/s/tLsnECZB9ajEqNJ
[2] https://www.railml.org/forum/index.php?t=msg&th=920& goto=3125&#msg_3125

Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Thu, 17 April 2025 16:34]

Report message to a moderator

Previous Topic: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Apr 20 18:24:57 CEST 2025