Home » railML newsgroups » railML.infrastructure » [railML 3.4 bèta 2] misuse of designator
[railML 3.4 bèta 2] misuse of designator [message #4042] Tue, 16 June 2026 18:25 Go to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
I see this introduced in railML 3.4 bèta 2:
	<xs:complexType name="TrackSuperstructure">
		<xs:complexContent>
			<xs:extension base="rail3:ConstructedComponent">
				<xs:sequence>
					<xs:element name="designator" type="rail3:Designator" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows specifying the exact type of material used as track ballast.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
...

I'm confused by the annotation documentation saying that the designator specifies "... the exact type of material...".

And here:
	<xs:complexType name="TrackBase">
		<xs:complexContent>
			<xs:extension base="rail3:ConstructedComponent">
				<xs:sequence>
					<xs:element name="designator" type="rail3:Designator" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows specifing the exact type of base used. E.g. ma be used to provide key identification data on the used sleepers.</xs:documentation>
						</xs:annotation>
					</xs:element>
A designator is not used to specify the type. Therefor exists the type designator?

Please also harmonise the documentation. I suggest to always start the annotation with "Identifier for external register that ..."

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

Report message to a moderator

Re: [railML 3.4 bèta 2] misuse of designator [message #4043 is a reply to message #4042] Tue, 16 June 2026 20:55 Go to previous messageGo to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
I just see a similar issue in the rolling stock scheme:

	<xs:complexType name="LineClassification">
		<xs:annotation>
			<xs:documentation>load limit with respect to line classification (permissible axle load and meter load)</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="designator" type="rail3:Designator" minOccurs="1" maxOccurs="1">
				<xs:annotation>
					<xs:documentation>name of the line class according to RIV or other register</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>

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

Report message to a moderator

Re: [railML 3.4 bèta 2] misuse of designator [message #4108 is a reply to message #4043] Tue, 18 August 2026 18:58 Go to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 130
Registered: March 2008
Senior Member
Dear Mathias,

Thank you for pointing out these inconsistencies! I already discussed a somewhat similar issue with the new Designator-typed elements <profile> and <steelGrade> in Rail, CheckRail and Frog with other coordinators. I've created a work item to follow it up [1], as well as one to improve the documentation of all occurrences of <designator> [2]. Please let me know if you see more cases of "false" designators in the table in [2].

[1] https://development.railml.org/railml/version3/-/work_items/ 778
[2] https://development.railml.org/railml/version3/-/work_items/ 777

Best regards,
Thomas

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: [railML v3.3 wiki] Ambiguous reference direction of track@mainDirection
Next Topic: [railML3.3] Signal combinations
Goto Forum:
  

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

Current Time: Tue Sep 15 10:54:44 CEST 2026