Home » railML newsgroups » railML.infrastructure » ocpRef at <platformEdges> and <stopPost>
ocpRef at <platformEdges> and <stopPost> [message #424] Fri, 09 November 2012 13:06 Go to next message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian and all others,

with the new <platformEdges> and <stopPost> elements, I was only now aware
that they have no ocpRef attributes so far.

I herewith plead for these ocpRef attributes because we need them to link
the timetable information with the new infrastructure elements.

Background: Often the timetable programmes do only refer to an OCP (stop,
passing through) but not to a certain platform or stop post. The question
"which stop post to take" when stopping at a station is normally clarified
by the operational rules. Therefore, it is not common to clarify it again
with the timetable because it would be redundant to the operational rules.

So, a train in its <ocpTT> refers to an <ocp> and a <track> but not
necessarily to a <stopPost> or <platform>. To find the platforms or stop
posts for that stop anyway, there should be the ocpRefs.

--> providing references from a <platformEdge> to an <ocp>: <platformEdge>
gets an "ocpRef".

--> We then also have the references from the stop posts to its ocp's via
the platformEdges, but there may be stop posts without platforms
(freight-only tracks), so: providing references from a <stopPost> to an
<ocp>: <stopPost> gets an "ocpRef".

---
In general:

- This applies theoretically not only to <platformEdges> and <stopPost>
but possibly to other track elements as signals and more. So possibly all
should get an optional ocpRef attribute, may be by inheritance. Currently
we do not have practical demand for that but theoretical it may come
quickly (drivers timetables normally also name the signals belonging to a
station...)

- There was a suggestion to provide all references as cross-references in
future. Therefore, an <ocp> should also name (enumerate) all its
<platformEdges> by refereces, possibly all its track elements. Again, I
see not specific demand now, it is a more general question.

Currently I only opt for the two now attributes; the general questions may
be discussed or postponed.

Best regards,
Dirk.
Re: ocpRef at <platformEdges> and <stopPost> [message #425 is a reply to message #424] Fri, 09 November 2012 15:48 Go to previous messageGo to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Dirk and other railML users,

> with the new <platformEdges> and <stopPost> elements, I was only now
> aware that they have no ocpRef attributes so far.
>
> I herewith plead for these ocpRef attributes because we need them to
> link the timetable information with the new infrastructure elements.
>
> [...]
>
> --> providing references from a <platformEdge> to an <ocp>:
> <platformEdge> gets an "ocpRef".
>
> --> We then also have the references from the stop posts to its ocp's
> via the platformEdges, but there may be stop posts without platforms
> (freight-only tracks), so: providing references from a <stopPost> to an
> <ocp>: <stopPost> gets an "ocpRef".

thank you for your remark. Indeed, a direct reference from the
<platformEdge> to the OCP and from the <stopPost> to the OCP has not
been implemented, yet. With the latest modification of trac tickets [1]
and [2], I considered the missing references.

[1] https://trac.assembla.com/railML/ticket/122
[2] https://trac.assembla.com/railML/ticket/167

Best regards

--
Christian Rahmig
railML.infrastructure coordinator
Re: ocpRef at <platformEdges> and <stopPost> [message #426 is a reply to message #425] Fri, 09 November 2012 16:06 Go to previous messageGo to next message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Dear Christian, Dirk and others,

Please have a look at a thread about its uses in the neighbouring
timetable-forum:

http://www.railml.org/forum/ro/?group=2&id=309

Don't miss the 'serviceSection' element!

Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
> thank you for your remark. Indeed, a direct reference from the
> <platformEdge> to the OCP and from the <stopPost> to the OCP has not
> been implemented, yet. With the latest modification of trac tickets
> [1] and [2], I considered the missing references.
>
> [1] https://trac.assembla.com/railML/ticket/122
> [2] https://trac.assembla.com/railML/ticket/167

Thanks for the quick implementation. Would you please provide the
appropriate keyrefs therefore? I will describe this dev-part of the
documentation in the wiki next:

http://www.wiki.railml.org/index.php?title=Hauptseite#Develo pers_Guides

Kind regards...
Susanne

--
Susanne Wunsch
Schema Coordinator: railML.common
Re: ocpRef at <platformEdges> and <stopPost> [message #427 is a reply to message #426] Fri, 09 November 2012 21:02 Go to previous messageGo to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Susanne,

> Don't miss the 'serviceSection' element!

I hope, I didn't, since I implemented the reference in the type
tPlatformEdge, which is the basis for tServiceSection, too.

> Thanks for the quick implementation. Would you please provide the
> appropriate keyrefs therefore? I will describe this dev-part of the
> documentation in the wiki next:
>
> http://www.wiki.railml.org/index.php?title=Hauptseite#Develo pers_Guides

Done with the last commit [1].

[1] https://trac.assembla.com/railML/changeset/475

Regards

--
Christian Rahmig
railML.infrastructure coordinator
Re: ocpRef at <platformEdges> and <stopPost> [message #1704 is a reply to message #427] Mon, 12 February 2018 15:35 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear all,

by using <stopPost>@ocpRef it is possible to link an OCP with a stop
post in railML 2.3. Despite this, Trac ticket #171 [1] suggests to
provide referencing from the OCP to the <stopPost>, too.

Question to all of you: do you need an attribute for direct referencing
of <stopPost> by <ocp> like this:

<ocp><stopPostRef>@ref

Or are you satisfied with the existing solution? Any kind of feedback is
appreciated.

[1] https://trac.railml.org/ticket/171

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: ocpRef at <platformEdges> and <stopPost> [message #1708 is a reply to message #1704] Wed, 14 February 2018 10:04 Go to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Ok, dear Christian, no further demand from our side. Thank you and best regards, Dirk.
Previous Topic: Track: description vs. trackDescr
Next Topic: loading gauge
Goto Forum:
  


Current Time: Fri Mar 29 11:41:27 CET 2024