| Re: Schema version V0.95-02 released [message #95 is a reply to message #93] |
Wed, 15 September 2004 20:47   |
Matthias Hengartner
Messages: 57
Registered: August 2003
|
Member |
|
|
Hello,
I'm very glad about the new schema with all the changes and new elements and
hope there is only a small step to version 1.0!
My (and Dani Hürlimanns) comments & questions:
- the attribute "type" (of <track>) should not be required (because some
exporting programms may not know what type a track is)
- could we have something like <generalElement> also in the <infraAttrGroup>
? ("<generalInfraAttribue>" or similar)
- I'm also glad about the possibility to place a switch (and also a
crossing) on a <trackBegin> / <trackEnd>. But I'd prefer to have only a
reference to a switch/crossing which is located in the
<connections>-container.
- It's also a good thing that we have the absolute position separated in 2
parts. But I'm a little bit confused about the format of these to
attributes. Both are decimals with 12 digits, 5 of them after decimal point.
What unit is "absPosOffset" meant to be? In the former versions of the
schema, the 2 patterns for "absPos" were
1. km: {dddd}d.d{dddd}
2. km + m: {dddd}d.d + {ddd}dd{.dd}
If these are close to reality (I guess they are), my suggestion is: 10/5
digits for "absPos" (km) and 7/2 for "absPosOffset" (m)
- <mileageChange>: I'm confused about the use of absPos, absPosOffset,
absPosIn and absPosInOffset, especially after having studied the two
mileageChanges in the demoNet-file. Perhaps it would be clearer if we had
"absPosOut" instead of "absPosIn".
- We have a new element type <trainProtectionElement> in the
<ocsElements>-container, but we have also the ("old")
<trainProtectionChange> in <trackElements>. Intention or mistake?
If it's intention, what is the difference between <trainProtectionElement>
and <trainProtectionChange>?
If it's a mistake, why is the attribute "monitoring" not included anymore?
- The new <crossing>-element has an attribute "dir". What is the use of
this, since we have already the "branchDir"-attribute in the connection?
- I've noticed, that longitude, latitude and altitude are now implemented as
attributes instead of child-elements of <geoCoords>. I'm fine with that.
- and finally, 2 little misprints:
<axleCounter>/posInTrack --> outsideRIght
annotation of "absPosAttrGroup" ("handlicng")
See you next week in Berlin!
Regards,
Matthias Hengartner
|
|
|
|
Members
Search
Help
Login
Home
