Home » railML newsgroups » railML.infrastructure » Infrastructure registers
Re: Infrastructure registers [message #1747 is a reply to message #1731] Wed, 28 March 2018 11:03 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

thank you addressing me as a speaker for all the railML community (which I am, of course, not).

> railML.org cannot guarantee that the content of the register mentioned is suitable for the purpose of exchange.

This was not the point nor the intention behind my last message.

Rather, railML.org has a set of register values like "DB640", "RL100" etc. which are clearly intended for the use at <ocp>. Please note: The value for the attribute "register=", _not_ the contents of a DB 640 or a Ril 100!

I do not expect railML.org to be responsible for the contents of such registers.

I do only prefer railML.org to formally ensure that the enumeration values for the attribute "register=" can only be set to registers which are clearly intended to be used at exactly this occurrence of "register", namely at <ocp>s, not for that at <line>s.

Dirk.
 
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 May 02 12:04:48 CEST 2024