Home » railML newsgroups » railML.infrastructure » small issues on "register" and "tLineInfrastructureManagerCode"
Re: small issues on "register" and "tLineInfrastructureManagerCode" [message #489 is a reply to message #485] Mon, 03 December 2012 16:33 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Susanne,

concerning the file structure: I would prefer using named attributes
rather than default attributes with element names for shortness (<version
code='ENEE'> rather than <code>ENEE</code>).

concerning the contents: Please do not provide redundant elements for the
same register ("RL100", "DS100", "DV100" are all the same). You find
examples for different registers in Wiki. If you feel necessary to provide
different names for the same register, disjunctive validities should be
enforced. This is not the case in your example.

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
Read Message
Previous Topic: <crossSection>.ocpTrackID
Next Topic: request for an attribute for the Infrastructure Manager of a line
Goto Forum:
  


Current Time: Sat May 18 20:23:54 CEST 2024