Re: request for an attribute for the Infrastructure Manager of a line [message #507 is a reply to message #481] |
Fri, 04 January 2013 16:33 |
Christian Rahmig
Messages: 151 Registered: January 2011
|
Senior Member |
|
|
Hi Susanne,
as well as for all the other railML users, I would like to wish you a
happy New Year 2013!
Am 03.12.2012 11:45, schrieb Susanne Wunsch:
> Hi Christian, Dirk and others,
>
>>> as discussed at the railML-conference in Zurich and already noticed by
>>> Dirk in another thread, we agreed on having a free string field for the
>>> 'infrastructureManager' with an additional XML-file providing a
>>> pre-defined list of possible values.
>>> [1] https://trac.assembla.com/railML/ticket/152
>
> I would propose the following structure for the XML file:
>
> <infrastructureManagerCodes xmlns="http://www.railml.org/lists">
> <infrastructureManagerCode id="d1e3">
> <version>
> <code>ThE</code>
> <name>Thüringer Eisenbahn GmbH</name>
> <validity begin="2001-08-01"/>
> <remarks/>
> </version>
> </infrastructureManagerCode>
> <infrastructureManagerCode id="d1e84">
> <version>
> <code>EIB</code>
> <name>Erfurter Industriebahn GmbH</name>
> <validity begin="1990-05-01" end="2007-03-02"/>
> <remarks/>
> </version>
> <version>
> <code>EB</code>
> <name>Erfurter Bahn GmbH</name>
> <validity begin="2007-03-03"/>
> <remarks/>
> </version>
> </infrastructureManagerCode>
> </infrastructureManagerCodes>
Since the attribute "id" is not really needed for the purpose of
referencing an IM list entry from a <line> within a railML file, I
prefer to leave it out. The question is if the user is really interested
in the history of the entry i.e. which name did the IM had before.
Because that seems to be the only reason why we introduced that "id"
attribute first.
To make the structure a little bit slimmer, I suggest the following layout:
<infrastructureManagerCodes xmlns="http://www.railml.org/lists">
<infrastructureManager code="ThE">
<name>Thüringer Eisenbahn GmbH</name>
<validity begin="2001-08-01" />
<remarks />
</infrastructureManager>
...
</infrastructureManagerCodes>
Any comments appreciated...
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|