Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
| Re: RFE for connection, DE:Anschluss [message #841 is a reply to message #814] |
Tue, 06 November 2012 10:47   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi Joachim, Andreas, Dirk and others,
coord(at)timetablerailmlorg (Joachim Rubröder) writes:
> here is my conclusion for the enhancement of connection within version 2.2:
>
> * messageText (string), optional
> * connType (commercial, operational, other:xxx), optional
> * ocpRef (Ref), optional
>
> http://trac.assembla.com/railML/ticket/165
> I shall implement it this way. Please check if this is sufficient for now.
There is a typo, I think you wanted to cite the following URL:
http://trac.assembla.com/railML/ticket/126
Why not to implement the 'trainPartRef' instead of 'trainRef'? It is
much more specific as Andreas already mentioned.
> Andreas Tanner wrote:
>>> Trainparts would be somewhat more precise than trains, and they have a
>>> validity. Maybe a connection holds only on certain dates.
>>> Actually, adding optional identifiers to ocpTTs would be non-breaking,
>>> so why not implement it this way for the next minor release?
Currently no ocpTT may be referred because of the missing "id" attribute
in the <ocpTT> element.
Wouldn't it be sufficient to refer to a certain 'trainPart' and an
'ocp'? A 'trainPart' may traverse a certain 'ocp' only once. If it
changes its direction this should be defined as a distinct 'trainPart'.
We currently speak about "heavy rails" not about tram systems where
turning loops are common. But anyway the 'trainPart' changes running
their.
> The issue of referencing an ocpTT is important and has a lot of
> implications. Tthat should be futher discussed and be introduced within a
> version 3.0. I therefore opend a new ticket:
> http://trac.assembla.com/railML/ticket/165
The reference to a certain platform stays to be resolved with the above
mentioned ticket. But this is a more general topic: how to refer to a
certain platform inside the timetable?
Currently the string-typed attribute "trackInfo" in the <ocpTT> element
is used for this, but since railML 2.2 the infrastructure enables
defining platformEdges for tracks that may be referred from the
timetable.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
 |
|
RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
|
|
Re: RFE for connection, DE:Anschluss
|
Goto Forum:
Current Time: Mon May 06 10:55:17 CEST 2024
|
Members
Search
Help
Login
Home
