Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
| Re: RFE for connection, DE:Anschluss [message #791 is a reply to message #790] |
Wed, 30 May 2012 10:21   |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Dear all,
up to now, we (I mean: IVU) have not implemented the connection element.
But maybe we will at some point, and then the following would be, from
my point of view, good to consider:
* the terminus technicus we are talking about is "transfer connections"
* they come for different purposes:
** printout products
** online information systems
** instructions to drivers (AVL (de:RBL) systems)
* they have a priority and / or a maximal delay time
I don't know the purpose of the "reason" element but to me it looks
dubious. Maybe a "type" would be more appropriate and could have the
values "external" (for passenger information and printout) and
"internal" (for AVL systems). In fact, a further differentiation could
be needed for different types of printout products and information
systems, so maybe a free subtype element would be wise.
* For the "description" element I suggest the name "messageText" or
"infoText" as this is more specific.
* optional attributes "maximalDelayTime" and "priority" would allow to
specify how reliable these connections are. AVL systems use these
parameters.
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.
Best regards
--Andreas.
Am 29.05.2012 22:44, schrieb Susanne Wunsch:
> Hello,
>
> coord(at)timetablerailmlorg (Joachim Rubröder) writes:
>
>> according to ticket #126, the following attributes are missing:
>> * connInfo (text)
>> * reason (commercial/operational)
>> * anyAttribute
>>
>> If there is no further input, I would implement it this way.
>
> I would like to avoid the duplication of the element's name.
>
> 'description' (some textual message) instead of 'connInfo'?
>
> I would like to implement an open enumeration list for the 'reason'
> attribute: commercial / operational / other:xxx
>
> just my 2 cents...
>
> Kind regards...
> Susanne
>
|
|
|
|
 |
|
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 00:41:09 CEST 2024
|
Members
Search
Help
Login
Home
