1.1R2 - sectionTT element [message #685] |
Mon, 29 December 2008 20:23 |
Teemu Sirkiä
Messages: 5 Registered: December 2008
|
Junior Member |
|
|
In version 1.1 R2 there are sectionTT elements like this:
<sectionTT sectionRefId="85ZVIA-85ZWIP" lineRefId="70005" trackInfo="302"
minRunTime="PT0M36S" distance="0.907"/>
In my opinion sectionRefId attribute should be changed so that there are
different attributes for the ID that starts and the ID that ends the section
like this:
<sectionTT sectionStartID="85ZVIA" sectionEndID="85ZWIP" lineRefId="70005"
trackInfo="302" minRunTime="PT0M36S" distance="0.907"/>
Here are some reasons:
- There is no documentation how those two Id's are combined in one attribute
- There is no reason to combine two things in one attribute
- What about if the ID contains "-" character?
-Teemu
|
|
|
Re: 1.1R2 - sectionTT element [message #686 is a reply to message #685] |
Mon, 05 January 2009 11:01 |
Joachim Rubröder railML
Messages: 0 Registered: November 2019
|
|
|
|
Dear Teemu,
the sectionTT element is meant for information concerning the section
between two ocpTTs of a train. The two attributes sectionRefId and
lineRefId are referencing section and line elements which are part of the
infrastructure. Unfortunately there is no such section element in the
infrastructure yet but I think there should be one. So I invented the
usage sectionRefId="85ZVIA-85ZWIP" with a combination of two ocp elements.
But it is still a RefId so it depends on the definition of a section.
With the current structure of the infrastructure I agree that a
combination sectionStartID/sectionEndID would fit better. But I hope that
there will be soon a section concept in the infrastructure.
What do you think as best connection between timetable and infrastructure
by references? How would you describe a whole network with high-level
connections from station to station in the terms of railML-infrastructure?
Kind regards,
Joachim
|
|
|
|
Re: 1.1R2 - sectionTT element [message #688 is a reply to message #687] |
Mon, 05 January 2009 16:57 |
Joachim Rubröder railML
Messages: 0 Registered: November 2019
|
|
|
|
Hi,
sectionRefID is an ID and you should never parse an ID for included
information!
For your two stations "A-1" and "A-2", you have to take your two ocpTTs
with ocpRefId "A-1" and "A-2" for localisation. Now you have to search
your infrastructure for any connections between A-1 and A-2.
This connection from A-1 to A-2 (if there is any) might be part of a line
"70005" and a section "XY" in a line/section model used by a certain
program. So an export could add helpful references like sectionRefId="XY"
lineRefId="70005". But there is no rule how to define a sectionID. I just
invented one possible usage of a sectionID="85ZVIA-85ZWIP" for the
example.
So maybe its better not to use this attribute unless it has its
counterpart inside an infrastructure schema. Or you are transferring
timetable data between two programs with the same infrastructure model and
a sectionID, well known by both.
Kind regards,
Joachim
|
|
|
|
Re: 1.1R2 - sectionTT element [message #690 is a reply to message #689] |
Wed, 07 January 2009 14:57 |
Joachim Rubröder railML
Messages: 0 Registered: November 2019
|
|
|
|
Oh, now I see the point.
The "sectionTT" in version 1.1.R2 ist still the same as the "section" in
1.1. The renaming with TT should just indicate, that it is not part of the
infrastructure. It is instead the usage of the infrastructure by a train
(this might be a bit sophisticated). In the timetable.xsd you can see,
that sectionTT is still a subelement of an "ocpTT" (= entry).
The problem is, that I made a wrong example by putting "sectionTT" on the
same level than "ocpTT". The file was valid because "sectionTT" was now
regarded an "any"-element and therefore still correct, so I missed this
error. I'm going to modify my example, will that solve your problem?
Kind regards,
Joachim
|
|
|
|
|
Re: 1.1R2 - sectionTT element [message #693 is a reply to message #692] |
Fri, 09 January 2009 13:51 |
Teemu Sirkiä
Messages: 5 Registered: December 2008
|
Junior Member |
|
|
"JoachimRubröder" <coord(at)timetablerailmlorg> kirjoitti viestissä
news:gk77mj$q2u$1(at)sifaivifhgde...
> Hi,
> I have changed the example in the timetable_V11-R2.zip, so please take a
> fresh download.
>
> Sorry for the misleading example and many thanks for detailed review!
> Joachim
Yes, now the structure looks good again.
Thanks!
-Teemu
|
|
|