Home » railML newsgroups » railML.infrastructure » small issues on "register" and "tLineInfrastructureManagerCode"
Re: small issues on "register" and "tLineInfrastructureManagerCode" [message #470 is a reply to message #468] Mon, 26 November 2012 13:02 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 and Christian,

> As agreed at the meeting in Zurich we will implement a free string
> attribute in the XML Schema, but provide an additional XML file with
> pre-defined values for this attribute.

Despite of having suggested an enumeration here, I would accept Susannes
solution. Here, anything is better than a pure string. It is ok, as long
as the spelling of well-known registers is defined anywhere in RailML. In
this sense, an enumeration and a string with pre-defined values makes no
difference for me.

Please don't forget the other extreme already mentioned: The
/infrastructureManagerCode/. As long as nobody wants to enumerate (and
maintain!) all the known IMs (ThE, EVB, HzL,...): Please define it as a
string (possibly with some pre-defined values) before it is too late for
2.2.

Thanks,
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: Fri May 17 14:20:47 CEST 2024