| "stop post" / "platform edge" reference from ocpTT (was: stop probability) [message #845 is a reply to message #737] |
Tue, 06 November 2012 12:29   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi Joachim and others,
Sorry for responding to my own posting. The time and implementation
changed. ;-)
Susanne Wunsch <coord(at)commonrailmlorg> writes:
> There are further attributes which could be defined in
> <stopDescription>:
>
> * (serviceSectionRef) if platforms, ramps or other facilities are
> defined as "serviceSection"s in IS [1]
>
> * (stopPosition) if serviceSectionRef is used and the train is shorter
> than the service section length
>
> [1] http://trac2.assembla.com/railML/ticket/122
Now the 'platformEdges' and 'stopPosts' are implemented in the
infrastructure sub-schema. Christian already opened a new Trac ticket
for not forgetting the reference from within a timetables <ocpTT> to the
appropriate <platformEdge> or <stopPost>. [1]
Is there the need for more than one reference to either a 'platformEdge'
or a 'stopPost'? I mean a 'trainPart' may only have one planned stop
position. No matter that it may change due to operational reasons.
* The <ocpTT> may already refer to the appropriate <track> where the
<platformEdges> and <stopPosts> may be defined.
* The <stopPost> itself may refer to a certain <platformEdge>.
* A reference from the <ocpTT> to either a certain <stopPost> or a
certain <platformEdge> is currently missing.
Both attributes ('stopPostRef' and 'platformEdgeRef') may be
introduced into the sub-element <stopDescription>.
If the 'stopPostRef' is used the 'platformEdgeRef' should be omitted,
it would be redundant to the infrastructure definition.
Both attributes are needed for different modeling levels. Some
software tool handles platforms without stop posts another tool
may only accept stop posts but no platforms.
* The current 'trackInfo' attribute in <ocpTT> would be marked
deprecated.
Any comments appreciated.
Kind regards...
Susanne
[1] http://trac.assembla.com/railML/ticket/171
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
