Home » railML newsgroups » railml.common » [railml3.1] Change "v" to "speed" in attribute names (Applies to both infrastructure and interlocking domains)
Re: [railml3.1] Change "v" to "speed" in attribute names [message #2067 is a reply to message #2062] Sun, 30 December 2018 05:32 Go to previous messageGo to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 148
Registered: May 2011
Senior Member
Thanks for your specific comments. I will consider this during current
refactoring of schema.

Best regards,
Joerg v. Lingen

Rollingstock Coordinator

On 29.12.2018 00:57, Thomas Nygreen wrote:
> Dear all,
>
> It was suggested already in 2010 to rename speedChange/@vMax
> to @maxSpeed, but it was kept for backwards compatibility
> between 2.x versions. I see no reason not to improve the
> name in 3.1.
>
> This applies to (with suggested changes):
> IS: Speed/@vMax -> @maxSpeed IS: SpeedSection/@vMax ->
> @maxSpeed IL: AspectRelation/@Vpassing -> @passingSpeed IL:
> AspectRelation/@Vexpecting-> @expectingSpeed
>
> Mostly, other tSpeedKmPerHour attributes already have names
> that end with Speed. Exceptions that begin with speed are:
> IS: SwitchCrossingBranch/@speedBranching -> @branchingSpeed
> IS: SwitchCrossingBranch/@speedJoining -> @joiningSpeed IS:
> PantographSpacing/@speed4PantographSpacing ->
> @pantographSpacingSpeed IL:
> LevelCrossingIL/@speedRestriction-> @unprotectedSpeed IL:
> Overlap/@speedInOverlap-> @overlapSpeed

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railml3.1] cleanup of unused types
Next Topic: railML 3.x: Data Modelling Patterns
Goto Forum:
  

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

Current Time: Wed May 15 12:47:47 CEST 2024