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 previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 143
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
 
Read Message
Read Message
Previous Topic: [railML3] Usage of //network/networkResource
Next Topic: [railML3.3] Signal combinations
Goto Forum:
  


Current Time: Sun Aug 09 19:28:00 CEST 2026