Home » railML newsgroups » railml.common » Vote for revision of ISO RailDax
Vote for revision of ISO RailDax [message #3154] Tue, 31 October 2023 15:54 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 180
Registered: March 2016
Senior Member
ISO TS4398 was published September 2022. Thank to a large extent to the railML community and railML.org as a liaison B organisation to ISO technical committee 204 intelligent transportation systems.
As a technical specification (TS) it is intended for review after 3 years. So, there will be a ballot on the manner in ISO technical committee 204 intelligent transportation systems. National standardisation bodies (NSB) that are member of TC204 in September 2025 will be eligible to vote. The vote is: abstain, discontinue, or revise. The most common vote is to abstain. This means the technical specification continues unchanged as an ISO TS. Alternative the NSB can vote to discontinue the standard (requiring an argument) or vote to revise it towards a full international standard (IS). A simple majority decides the vote. If there is no initiative (from railML or other ISO participants) the very likely outcome is that the TS continues unchanged. The next vote is then 3 years later in September 2028. If an ISO participant suggests revising the TS, they need to commit resources to do the revision and achieve the necessary simple majority vote. Also, a draft of the proposed revision should be made. Because of this work an active decision to revise needs to be made at least 1,5 years prior to the vote. For the upcoming vote this would be March 2024. The railML conference closest before this date is the upcoming conference in Rome on 7th November.
Thus, I suggest the railML community make an active decision to recommend a revision of ts4398 RailDax for either:
A. Sept 2025
B. Sept 2028 (without any commitment)/No revision planned currently.

There seems to be consensus if we want a revision, it should be based on the latest version of railML3.

See also slides from the presentation on the 43th railML conference found at railML.org ( https://www.railml.org/en/event-reader/43rd-railml-conferenc e-berlin.html?file=files/download/events/conferences/43_Berl in/2023-05-30_JDIR_ISORailDaxTimelineRailMLusageNorway.pdf&a mp;cid=11371)

Please cast your vote as a reply to this forum post. Note if you vote to revise you should contribute to the revision work.

Re: Vote for revision of ISO RailDax [message #3155 is a reply to message #3154] Wed, 01 November 2023 08:27 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 180
Registered: March 2016
Senior Member
Jernbanedirektoratet vote option B.
This as it fits with our resource plan where we will focus on railML 3.2 mapping/3.3 development to fulfil all required UC for Jernbanedirektoratet and gain further maturity in 2024. We do not have enough resources to also contribute to an ISO RailDax revision at the same time.
We also think a revision of ISO RailDax would fit well with the development of railML version 3.4, making railML3.4 the basis for ISO IS4398:2028 (our proposal).
Re: Vote for revision of ISO RailDax [message #3161 is a reply to message #3155] Wed, 08 November 2023 09:48 Go to previous messageGo to next message
Miloš Futera is currently offline  Miloš Futera
Messages: 1
Registered: November 2023
Junior Member
Dear colleagues,

Správa železnic votes for option A ( i.e. Sept 2025)

Správa železnic (SZCZ) is infrastructure manager in the Czech Republic and has implemented railML 3.x format for publication of network statement data and other purposes. SZCZ is member of RailNetEurope (RNE) - association of European infrastructure managers. RNE will use ISO RailDax for date exchange about infrastructure with its member. Existing RailDax is based on railML 2.x.

SZCZ has no expierence with railML 2.x. Therefore SZCZ would appreciate if new version of RailDax railML based on version 3.x would be available as soon as possible. That is why therefore SZCZ supports option A.

Miloš Futera
Re: Vote for revision of ISO RailDax [message #3538 is a reply to message #3161] Wed, 02 April 2025 20:07 Go to previous messageGo to next message
Torben Brand is currently offline  Torben Brand
Messages: 180
Registered: March 2016
Senior Member
ISO/TS 4398:2022 "Guided transport service planning data exchange" (short ISO RailDax) was published in September 2022 by ISO committee 204 Intelligent transportation systems (ITS), developed thorough its working group 8 public transportation (PT). See www.raildax.org for further details.

ISO/TS 4398:2022 is up for systematic review in September 2025. The Norwegian railways sector plan to suggest revising the document and upgrade it to a full international standard (IS). This position paper explains the background and arguments for such a revision, and its purpose is to gather feedback from interested parties for or against a proposed revision and its details. We plan the following steps:
• April: enquiry for the revision (this forum post)
• End of May: outreach and presentation at ISO TC204 plenary
• June: send in ISO Form 4 for new work item at ISO, with defined model language and use case
• September: Ballot closes
• September/October: project group startup

The existing standard ISO/TS 4398 purpose is to provide a data exchange format for guided transportation for the use case service planning . For further details on the scope see "executive explanation" on internet www.raildax.org.
An important requirement was to build on proven and mature technology that fulfills the scope, where available. The existing industry standard railML was chosen to fulfill this, in the version 2.5. The only negative feedback towards this was that we should base the standard on the conceptual de-facto standard for topology by UIC called "RailTopoModel/Rail system Model" (RTM). RailML version 3 is based on RTM, but the version 3.1 at the time was not deemed mature enough for our scope. With the current version 3.3 this has changed.
Thus, we recommend the revision to keep the initial purpose and use cases, but to base on the current version of railML 3.3. We are open for considering further potential use cases, which might be deemed relevant. If you would like to extend the list of use cases, please provide the relevant resources (in experts) in the UC relevant field towards the project.

We will be working in close collaboration with experts from raiML.org (you), as a liaison C organization towards ISO TC204 WG8, which will develop the new railML version 3.4 in parallel with this proposed revision of an upgrade to a full international standard of ISO IS:4398.

We believe a revised and upgraded ISO 4398 will benefit the European community, as a European standard. Thus, use of Vienna agreement (meaning that the ISO standard will also become a european CEN standard) is an option, and we ask for feedback on support for such an approach.

Details on the suggested relevant use case
The high level use case is "service planning". This consist of sub use cases:
- Schematic track plans for infrastructure planning (SCTP)
- Runtime calculations (RTCI)
- Network asset descriptions (NEST)
- Passenger assets of rolling stock for operational planning (RPAS)
- Long Term Strategic Timetabling (LTST)
- Operative timetable simulation (RSIM)
Details of these use cases (and others) can be seen at the railML wiki.


Mapping towards other standards
The current TS 4398 contains in annex A a very high-level mapping towards the standards:
- Network Timetable Exchange, NeTEx (CEN/TS 16614 series),
- Telematics Applications for Passenger Service TSI (TAF/TAP; European Union Agency for Railways)
- Register of Infrastructure, RINF (European Union Agency for Railways)

We propose to update the mapping and to make it more detailed for practical use.

I ask the railML communit to please give feedback either here in the forum or in email to torbenbrand(at)jernbanedirektoratetno with copy to bbr(at)standardno by 19.may 2025
Re: Vote for revision of ISO RailDax [message #3552 is a reply to message #3538] Wed, 09 April 2025 06:33 Go to previous message
Vasco Paul Kolmorgen
Messages: 64
Registered: November 2004
Member
Dear Mr. Brand, dear colleagues,

On behalf of the railML.org governance, we would like to thank you for
your initiative and clear outline regarding the proposed revision and
upgrade of ISO/TS 4398:2022 “Guided Transport Service Planning Data
Exchange”.

The publication of ISO/TS 4398 in 2022 was a significant milestone, made
possible through the strong collaboration between ISO TC204/WG8 and the
railML.org community. We are proud to have supported its development as
a liaison B organisation to ISO TC204/WG8
(https://www.iso.org/committee/54706.html) and we remain fully committed
to contributing to its future evolution.

Following extensive consultation within our community and in alignment
with recent developments in the railML 3.x schemas and the ongoing
development of railML 3.4, we believe that the timing is right for
revision and we are prepared to commit the necessary resources to
support the standardization process accordingly.

Therefore, railML.org votes in favour of a revision of option A and
formally supports a revision of ISO/TS 4398 starting in September 2025
with the objective of upgrading it to a full International Standard
(IS), based on the latest railML 3.x framework.
We would also agree on the use of the Vienna Agreement to harmonise ISO
4398 with European CEN standard. This would support wider adoption
across European infrastructure managers and operators, while also
avoiding duplication in national implementation efforts.

We support the plan to expand and improve the mappings towards the
standards - NeTEx, TAF/TAP, RINF and retain the current use cases, add
additional ones from the current research project IDX4rail
(https://www.idx4rail.de/de/anwendungsfaelle; German text only) in the
light rail / tramway sector, where relevant. By this we confirm our
willingness to provide technical expertise and resources throughout the
process.

We thank you once again for your efforts in leading this important
initiative and encourage all stakeholders and the railML community to
join us in the standardised exchange of data for railway service
planning. We look forward to working with you on this initiative.

Kind regards,

--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany
Previous Topic: [Ontology v0.6] minor comments on Classes & their definition
Next Topic: [railML3] Change pattern for tOtherEnumerationValue
Goto Forum:
  


Current Time: Sat May 03 19:41:10 CEST 2025