Home » railML newsgroups » railML.infrastructure » [railML 2] Semantic Constraint at trackBegin and trackEnd
Re: [railML 2] Semantic Constraint at trackBegin and trackEnd [message #3547 is a reply to message #3545] Tue, 08 April 2025 10:46 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 80
Registered: March 2015
Member
Dear all,

sorry for my late answer. In certain cases we export tracks whose trackBegin element has an "pos"-value other than "0". I am not sure whether there is a specific usecase for this, finally we export the data in the same way the user entered it in our program. However all "pos" values of track elements should always be increasing, i.e. the position of trackEnd is always higher then the one of trackBegin.

But I'm a bit confused: When I look at the SemCons IS:002 and IS:003 under https://wiki2.railml.org/wiki/Dev:SemanticConstraints I don't see any hint, that the track must begin with "pos=0". Both SemCons seem to be still under discussion. So, is it the idea, to reject these two SemCon proposals and replace them with the restriction that the trackBegin-Position must always be zero?

Best regards
Christian

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3 wiki] opEquipment
Next Topic: [railML3] Proposal of a semantic constraint for <baliseGroup>
Goto Forum:
  

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

Current Time: Sat Nov 15 19:45:07 CET 2025