| Re: Datatype for distance in sectionTT [message #768 is a reply to message #765] |
Mon, 26 March 2012 22:22   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello Dirk, Christoph and others interested,
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> this is a known problem since a long time. I do not know the origins
> anymore but we already had discussions about it some years ago.
+1
> So, I would prefer to write meters ("distance='460'" in the example
> above) and this is my recommendation. This would mean not to change
> the XSD but to change the examples and FBS output.
That would be easier for us maintaining the schemas. But is it helpful
for the export and import interfaces?
I thought that the distance between two 'ocp's should be in kilometers
as well. If we look into the new rostering sub-schema we introduced the
attribute 'runLength' in the element 'blockPart'. It should be given in
kilometers.
We should harmonize both values, either the sectionTT or the blockPart
attribute.
BTW all infrastructure length values are expected in meters. That may be
a cause for this "old" attribute.
....just my 2 cents
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
