Home » railML newsgroups » railML.infrastructure » [railML 3.4 alpha 5] Inconsistent camelcase for superelevation
[railML 3.4 alpha 5] Inconsistent camelcase for superelevation [message #4041] Tue, 16 June 2026 18:13 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels
Senior Member
Hello,

I notice that the [railML 3.4 alpha 5] has introduced inconsistent camelcasing for "superelevation". The concept is one word, so the 'E' after super shouldn't need to be capitalized. However, it was so in earlier version of railML. Staring from the alpha, this was changed to lowercase. But not everywhere.

Please choose one or the other but then implement the change everywhere.

Here is one example where it went wrong:

	<xs:complexType name="GeometryPoint">
		<xs:annotation>
			<xs:documentation>point representing location of a radius or/and a gradient of a track</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="rail3:GeometryEntity">
....
				<xs:attribute name="superElevation" use="optional" type="rail3:tLengthMM"/>
				<xs:attribute name="superElevationReference" use="optional" default="innerRail" type="rail3:tSuperelevationReference"/>
...


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

Report message to a moderator

[Message index]
 
Read Message
Read Message
Previous Topic: [railML3] Usage of //network/networkResource
Next Topic: [railML 3.4 bèta 3] PlatformEdge's new attribute "lateralDistance"
Goto Forum:
  

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

Current Time: Fri Sep 11 13:20:13 CEST 2026