Home » railML newsgroups » railML.infrastructure » [railML 3.4 bèta 3] BaliseGroup attribute validityDirection
[railML 3.4 bèta 3] BaliseGroup attribute validityDirection [message #4040] Tue, 16 June 2026 18:04 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 143
Registered: February 2025
Location: Brussels
Senior Member
Hello,

I notice in railML v3.4 bèta 3 that the baliseGroup has received a new attribute validityDirection that seems to indicate the direction in which the baliseGroup is applicable.

The element type that is associated is the tApplicationDirection which refers to intrinsicCoordinates to give meaning to the direction. However:
- without a reference to a netElement, this attribute is useless and ambiguous
- the spotLocation already contains this attribute, so this solution is increasing data duplication and possible issues
- multiple spotLocations (on different networks or levels) can exists, thus the tApplicationDirection can be different depending on the referenced netelement

Please remove this new attribute, it makes no sense.

Thank you

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: [railML 3.4 bèta 3] PlatformEdge's new attribute "lateralDistance"
Next Topic: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation
Goto Forum:
  

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

Current Time: Sun Aug 09 18:59:49 CEST 2026