Home » railML newsgroups » railML.infrastructure » Infrastructure registers
Re: Infrastructure registers [message #1685 is a reply to message #1683] Wed, 27 December 2017 14:28 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,

> What do you think about this proposal?

To be honest: Not good. I miss a clear and easy understandable structure. As far as I understand, with your suggestion, one could use the same value for <designator @register=...> in registers for <ocp>s, <line>s and so on. So, someone could write <designator register='DB640'> at a <line> element despite there are no lines listed in DB640. This could not be checked by a validator algorithm. It would not be formally invalid but it would be semantically invalid.

Rather, I would prefer railML being a standard which brings us as most clarity as possible.

With best regards,
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 09:10:22 CEST 2024