Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
| Re: RFE for connection, DE:Anschluss [message #796 is a reply to message #792] |
Wed, 30 May 2012 14:56   |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
> The purose of "reason" was to distinguish between these two main types.
> * internal / commercial for printouts or online information systems
> * external / operational for AVL systems
> * other:xxx for further differentiation
> I think "commercial/operational/other:xxx" is more specific than
> "internal/external".
>
Ok, but to my ears, a connection would be of some /type/ rather than it
would have a "reason".
>> * optional attributes "maximalDelayTime" and "priority" would allow to
>> specify how reliable these connections are. AVL systems use these
>> parameters.
>
> We have already the two attributes "minConnTime" and "maxConnTime" that
> could be used instead of "maximalDelayTime". The "priority" is only for
> the AVL usage and is hard to define. I'd like to leave this for a future
> version.
>
Hmm, I read the description of these attributes in the wiki, but did not
come to the end that this was their intention. If maxConnTime is the
maximal delay, what then is minConnTime?
>> And one more point: is the "trainRef" element intended for a reference
>> to a /train/? Shouldn't it refer to some ocptt? First, a connection may
>> be between two /different/ ocps (Berlin Hbf oben / unten), and second,
>> an ocp may be traversed more than once.
>
> If we think of printouts, this wuould be part of the "messageText" like
> "connection to IC 7411 on platform 7b". We could not reference an ocpTT
> because there is no "id" to be referenced. I think a Reference to a
> "train" is correct.
>
>
I agree for printouts, but this would not work for online connection
finders and AVL systems where a driver wants to see the connection the
relevant location.
You are right, the ocpTTs are not referencable, could you please open a
ticket for future versions?
Trainparts would be somewhat more precise than trains, and they have a
validity. Maybe a connection holds only on certain dates.
Best, Andreas.
|
|
|
|
 |
|
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 09:25:14 CEST 2024
|
Members
Search
Help
Login
Home
