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 #2105 is a reply to message #2062] Fri, 18 January 2019 11:27 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Thomas,
dear all,

Am 29.12.2018 um 00:57 schrieb Thomas Nygreen:
> [...]
> 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

I did the following renamings:
* <speedSection>
- @vMax --> @maxSpeed
* <switch><*branch>
- @speedBranching --> @branchingSpeed
- @speedJoining --> @joiningSpeed

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

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 05:18:53 CEST 2024