Home » railML newsgroups » railml.timetable » RFE for connection, DE:Anschluss
Re: RFE for connection, DE:Anschluss [message #792 is a reply to message #791] Wed, 30 May 2012 14:16 Go to previous messageGo to previous message
Joachim Rubröder railML is currently offline  Joachim Rubröder railML
Messages: 0
Registered: November 2019
Dear Andreas,

> 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

We like to reuse the existing "connection" element to be considered as
"transfer connections" but without renaming or lots of restructuring.
Therefore we planned to just introduce some new attributes for version 2.2
with a clearly defined purpose.

> 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.

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".

> * For the "description" element I suggest the name "messageText" or
> "infoText" as this is more specific.

I like the name "messageText". This is appropriate for printouts and also
for the AVL system, indicating an instruction for the driver.

> * 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.

> 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.

Kind regards,
Joachim




--
----== posted via PHP Headliner ==----

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: stop probability
Next Topic: wiki: missing attribute description for additionalTrainNumber at <train>
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Mon May 06 11:10:17 CEST 2024