Home » railML newsgroups » railML.infrastructure » [railML3] Mandatory <Location> for <genericArea>?
Re: [railML3] Mandatory <Location> for <genericArea>? [message #3144 is a reply to message #3138] Wed, 18 October 2023 14:41 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Hello Torben,

thanks for pointing on this topic. I checked the related development issue [1] and the forum posts [2]. After all, I cannot find any reason or argumentation, why the child element <location> should be mandatory and I am quite sure that this is a bug of our implementation of the <genericArea> element in railML 3.2. I suggest to change this to optional (like for the other child elements) with railML 3.3.

If someone from the community has any objection, please let me know until end of Octobre 2023.

Thank you very much and best regards
Christian

[1] https://development.railml.org/railml/version3/-/issues/479
[2] https://www.railml.org/forum/index.php?t=msg&th=830& goto=2832&#msg_2832

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 2.5] Connections without track information
Next Topic: Missing attributes and maybe elements in railML3.2 for RTCI-a
Goto Forum:
  

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

Current Time: Mon Jul 22 16:13:19 CEST 2024