Home » railML newsgroups » railML.infrastructure » [railML 3.3 beta2] Generic Area Sequence Number
[railML 3.3 beta2] Generic Area Sequence Number [message #3372] Wed, 23 October 2024 15:04 Go to next message
Dominik Looser is currently online  Dominik Looser
Messages: 23
Registered: March 2020
Junior Member
Dear all,

The element <genericArea>/<isLimitedBy> contains a mandatory attribute "sequenceNumber". This attribute does not exist for any other "zone" or "area".
We think this change stems from issue 520, which mentions "adding sequenceNumber to collection items". The examples provided in the 44th railML.org conference are sequences where a natural order is logical, such as the stops of a train (in a timetable). However, we think that for the borders of an area, there is no logical order and the attribute "sequenceNumber" should not be implemented here (or at least not as mandatory).


Thank you and best regards,
Dominik
Re: [railML 3.3 beta2] Generic Area Sequence Number [message #3383 is a reply to message #3372] Tue, 29 October 2024 13:41 Go to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 157
Registered: April 2007
Senior Member
Hi Dominik,

thanks for bringing this to our attention. The was actually a side effect of modelling something else that in the meantime was discarded already. the sequence number should not have been there in the first place. I removed it from the genericArea and it will not be part of the 3.3 release.

Best regards, Milan


Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Previous Topic: [railML3] Refactoring of states (e.g. infrastructure states)
Next Topic: [railML3] Need for modelling Radio Infill Units
Goto Forum:
  


Current Time: Mon Jan 20 13:03:28 CET 2025