Home » railML newsgroups » railML.infrastructure » [railML3] Construction of virtual signals (New semantic constraint suggested)
[railML3] Construction of virtual signals [message #3317] Mon, 09 September 2024 11:26
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 49
Registered: November 2022
Member
Dear all

2024-01-22 railML.org suggested the new semantic constraint IS:005 [1] for the representation of the railway signals. Please let us know if you do not agree with it withing the following month.

The background is as follows:

In railML3 <signalIS> has child <signalConstruction> with attribute @type with one of enumeration values "virtual: signal has no physical presence on the track. Command is passed in some other way, e.g. radio".

<signalConstruction> has also other attributes: @height and @positionAtTrack. These surely seem to be intended for physically present entities.

Suggested semantic constraint is as follows: signalConstruction/@height and signalConstruction/@positionAtTrack should not be used with signalConstruction/@type = "virtual".

[1] https://wiki3.railml.org/wiki/Dev:Semantic_Constraints

Sincerely,

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

[Updated on: Mon, 09 September 2024 11:30]

Report message to a moderator

[Message index]
 
Read Message
Previous Topic: [railML3] Interpreting @applicationDirection of <linearLocation>
Next Topic: [railML3] Need for modelling Lineside Electronic Unit
Goto Forum:
  

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

Current Time: Mon Oct 07 14:12:02 CEST 2024