| Re: XML list files in an element-centric structure (was: small issues on "register" and "tLineInfrastructureManagerCode") [message #1139 is a reply to message #1137] |
Fri, 07 December 2012 15:17  |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Susanne,
thank you for providing the possibility to take part at this important
decision.
To make it short: I opt for keeping the current philosophy of usage of
attributes and elements. I opt for still using attributes for simple,
base-type information.
In general: The reason for my opinion is the file size: With elements a
file is bigger than with attributes because of the repeating of the
element names. Due to a simple file-size proportionality, the processing
of element-like files tends to be longer than that of attribute-like
files. We already have very large RailML files with processing times
sometimes of some minutes (!) and I do not want to get a problem with file
size or processing times in future.
But I am aware that there are many arguments for both solutions and I also
do not want to start this discussion again here. So this should be a
simple vote in a democratic manner without much arguing.
In specific: If RailML 3.0 or 10.0 or whatever would change all the
existing attributes to elements (even if except the three you named), we
possibly wouldn't be able to use that RailML schemes because I think it is
too much effort to change all the existing programming for iRFP and for
all our partners. So here in particular I opt a little bit "stronger" for
keeping the structures and philosophy we already have.
With best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
