questions & suggestions v0.94_18: trackTopology [message #66] |
Wed, 07 April 2004 17:26 |
Matthias Hengartner
Messages: 57 Registered: August 2003
|
Member |
|
|
Hello,
I have some questions and suggestions about the newest version of the
infrastructure schema. Some of them could be points to discuss about.
Here some points about <trackTopology>:
- As we already shortly discussed about: I suggest to drop the element
<singleCrossOver>. I see no relevant advantages of keeping this element in
the scheme.
- In a <track>, we have the attributes "posTrackBegin", "posTrackEnd",
"absPosTrackBegin", "absPosTrackEnd" for the relative and absolute position
of the begin/end of the track. The same information can be found in the
<trackBegin>/<trackEnd>-elements. What are the benefits of this redundancy?
Another attribute of a <track> is "length", which coincides with
"posTrackEnd", if "posTrackBegin" is set to 0.000.
So my suggestion is to drop those 4 attributes, but to keep "length". Other
opinions?
- What's the meaning of the (required) attribute "dir" in <simpleConnection>
and <bufferStop>? The sense escapes me.
- Why do we distinguish between "connectionIDType" and "connectionIDRefType"
?
- <bufferStop> has an attribute "connectionID", although it has nothing to
do with a connection. Why is bufferStopType derived from connectionType and
not elemBaseType?
- What about renaming "connectionID" into "elemID"?
- I propose to add an attribute "topologyIDRef" to connectionRefType
(<branchConnection>).
Thanks for answers and opinions!
Best regards
Matthias Hengartner
|
|
|