| Re: Multiple ocpTT within a station [message #2397 is a reply to message #2393] |
Fri, 13 March 2020 15:58  |
Vasco Paul Kolmorgen
Messages: 55
Registered: November 2004
|
Member |
|
|
Dear Stefan,
thank you for the interesting question. First of all I would like to
learn for what kind of use case this need for a railway data exchange is
given in the Netherlands. Could you describe a little bit more detailed?
From my opinion your sample should not be used for semantic reasons.
As good practice in the files I had seen in the past and also described
in the railML 2 wiki
(https://wiki2.railml.org/index.php?title=TT:ocpTT#Semantics) each ocpTT
shall only appear once within a trainPart. Unfortunately this issue is
described there on German only ("Als Regel darf jeder ocpTT nur einmal
innerhalb eines trainParts auftauchen.") However, I will gladly take
your question and suggestion to one of the next telephone conferences of
TT developers and ask for contributions to the discussion and opinions.
I would also like to suggest a possibly clearer presentation in the
section "Semantic Constraints" as well as a statement for the current
development of railML 3.x.
Let me highlight some other problems in your example:
- Your example uses "speaking ID's" like ocpRef="ARR-StopArea-Vvl"
which should be avoided, as 'StopArea' could be parsed and used by a
reading programme. See
https://wiki2.railml.org/index.php?title=Dev:identities for more
information.
- Independent of the concrete times at the individual <ocpTT> I
consider the double use to be very problematic, because different
further characteristics can exist. In your example this is given by
ocpType="stop" and ocpType="pass".
Best regards,
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Am 11.03.2020 um 15:15 schrieb Stefan de Konink:
> I have a question regarding the use of ocpTT's within a
> station.
>
> Considering the following sample:
>
> <ocpTT ocpRef="ARR-StopArea-Vvl" ocpType="stop"
> sequence="10" trackInfo="252">
> <times arrival="19:09:00" arrivalDay="0"
> departure="19:09:00" departureDay="0" scope="scheduled"/>
> <sectionTT>
> <trackRef ref="ARR-ServiceLink--667658658"/>
> </sectionTT>
> </ocpTT>
> <ocpTT ocpRef="ARR-StopArea-Gn" ocpType="pass"
> sequence="11" trackInfo="7A">
> <times arrival="19:09:00" arrivalDay="0"
> departure="19:09:00" departureDay="0" scope="scheduled"/>
> <sectionTT>
> <trackRef ref="ARR-ServiceLink--1709210067"/>
> </sectionTT>
> </ocpTT>
> <ocpTT ocpRef="ARR-StopArea-Gn" ocpType="stop"
> sequence="12" trackInfo="7B">
> <times arrival="19:09:00" arrivalDay="0"
> departure="19:09:00" departureDay="0" scope="scheduled"/>
> </ocpTT>
> </ocpsTT>
>
>
> Is the ocpTT of 7A allowed as pass? Or is it never allowed
> to use the same ocp in a ocpsTT?
|
|
|
|
Members
Search
Help
Login
Home
