Home » railML newsgroups » railml.common » adding <designator> to <speedProfile>
adding <designator> to <speedProfile> [message #3766] Sun, 26 October 2025 22:07 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 205
Registered: March 2016
Senior Member
Hi,

For an unambigious designation of the speed profiles I suggest to add the standarized <designator> sub element to <speedProfile> [1] element in Common in railML3.4.

This for the RTCI UC in an international (cross-border) perspective.

As a huge side effect this would make the unresolved forum post [2] on the sub-element <etcsSpeedProfile> redundant as you then can optionally designate the speed profile to the register "SUBSET-026" in general or the "NC_TRAIN: INTERNATIONAL CATEGORY TO WHICH BELONGS THE TRAIN" specific. Pending one of them beeing registered after the introduction of <designator> under <speedCategory>.

There have also been multiple voices in the community to add <designator> to most elements.

[1] https://wiki3.railml.org/wiki/CO:speedProfile
[2] https://www.railml.org/forum/index.php?t=msg&goto=3710&a mp;&srch=etcsSpeedprofile#msg_3710
[3] https://wiki3.railml.org/wiki/CO:etcsSpeedProfile

Report message to a moderator

Re: adding <designator> to <speedProfile> [message #3768 is a reply to message #3766] Mon, 27 October 2025 08:29 Go to previous messageGo to next message
Dominik Looser is currently offline  Dominik Looser
Messages: 37
Registered: March 2020
Member
Hi,

We would also appreciate this.
When we receive files from different countries, knowing which speed profile is which is always a bit of guessing. Having a clear, standardized designator, would help a lot here.

Best regards,

Dominik Looser
trafIT solutions gmbh

Report message to a moderator

Re: adding <designator> to <speedProfile> [message #3769 is a reply to message #3768] Mon, 27 October 2025 08:42 Go to previous messageGo to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 88
Registered: February 2025
Location: Brussels
Member
I agree with this request and strongly ask to add <Designator> and! <ElementState> to all elements (also topology!)

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

Re: adding <designator> to <speedProfile> [message #3772 is a reply to message #3769] Mon, 27 October 2025 18:40 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 110
Registered: March 2008
Senior Member
Dear all,

Initially, I don't see a problem adding a designator to <speedProfile>. But it would maybe be more fitting with a <typeDesignator>?

Does anyone have an example of an existing register of speed profiles? Either with individual code entries in a register that can be added to the Registers code list or a register that assigns a UUID to each speed profile, which can be referenced from a <designator> with register="UUID".

"SUBSET-026" is not a register, but a series of ETCS specifications with several versions, each with several releases, in which NC_TRAIN has been redefined several times. Trying to use that as a designator only carries over the problems from Torben's [2]. It would also apply only to ETCS speed profiles. The other variables available in SUBSET-026 to specify which trains a speed profile applies to are already available in <speedProfile> and can also be used for non-ETCS speed profiles.

Having a "clear, standardised designator" for speed profiles across different countries would require the speed profiles themselves to be standardised across different countries. What the ETCS specifications are doing is standardising how the applicable train types are described, and the same approach has been used in railML3. There are already properties available in <speedProfile> to avoid having to guess.

Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic: [railML2/3] Proposal for new semantic constraint for the version of railML
Next Topic: [railML3] Adding globally unique identifiers
Goto Forum:
  

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

Current Time: Sun Feb 15 03:50:26 CET 2026