Home » railML newsgroups » railML.infrastructure » suggestion for switchIS@type="crossingPart" (new enumerations value in railML3.4)
Re: suggestion for switchIS@type="crossingPart" [message #4121 is a reply to message #4048] Wed, 26 August 2026 08:39 Go to previous messageGo to previous message
Dominik Looser is currently offline  Dominik Looser
Messages: 66
Registered: March 2020
Member
Dear all,

In railML 3.4 beta 4, the subelement Crossing/crossingAngle is defined as mandatory (minOccurs="1"). While beneficiary for layouting purposes, I think this is too strict. Some tools might no be able to know the angle and as long as you have infrastructureVisualization information, the information is also not necessary.
I would suggest to change it to minOccurs="0".

Thank you and best regards,
Dominik Looser, trafIT solutions gmbh

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Restricting aggregation of RailTopoModel
Next Topic: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation
Goto Forum:
  

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

Current Time: Fri Oct 16 16:31:10 GMT+2 2026