Home » railML newsgroups » railML.infrastructure » Infrastructure registers
Infrastructure registers [message #1547] Mon, 10 April 2017 14:56 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 474
Registered: January 2016
Senior Member
Dear all,

with railML version 2.2 we introduced the OCP sub-element <designator>
with its attributes @register and @entry (see [1]). At the 31st railML
Conference in Berne on 22.03.2017, the introduction of timetable related
register references has been discussed. In order not to mix registers
with different purposes, it is necessary to distinguish between
infrastructure and timetable registers. Therefore, it has been suggested
to rename @register into @infrastructureRegister in order to indicate
what kind of register shall be referenced (see [2] for more details).

[1] https://trac.railml.org/ticket/112
[2] https://trac.railml.org/ticket/310

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
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Use the concept of layer for splitting the data
Next Topic: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir
Goto Forum:
  


Current Time: Thu Nov 14 06:45:14 CET 2024