| Re: [railML2] Modelling of crossings/overtakings [message #2403 is a reply to message #2401] |
Thu, 19 March 2020 12:17  |
Vasco Paul Kolmorgen
Messages: 55
Registered: November 2004
|
Member |
|
|
Dear Janne,
thank you for the interesting question regarding the modelling of
crossings and overtakings. First of all I would like to learn for what
kind of use case this need for a railway data exchange is given in
Norway. Could you describe a little bit more detailed?
From my opinion your proposal could lead for some new semantic
constraints, e.g. what happens, if you define a
<stopActivity>@type="occupationCrossing" for a crossing but there is no
crossing train the this file which fits to the train to be crossed.
Such semantic constraints must be described very carefully and adapted
to the (in railML 2 mostly unknown) use cases in order to avoid further
queries.
The central question would therefore be from the perspective of the
long-term usability of the railML schemes: In which application case
shall an crossing and overtaking also be transferred and read in within
the framework of a data exchange between two software systems and could
this not also be clearly determined by evaluating the data that already
exists?
Best regards,
--
Vasco Paul Kolmorgen - Governance Coordinator
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Am 18.03.2020 um 13:22 schrieb Janne Möller:
> Dear railML community,
>
> To model a crossing or overtaking procedure between trains,
> I would like to ask what the best practice for these are.
> I would use the element <connection> to Refer to the train the crossing
> takes place with, and
> Specify the sequence of arrival of the trains with
> @connOperation (where the value "isWaitingFor" describes the
> train that arrives first and "isExpectedBy" the train that
> arrives last)
>
> To specify what type of connection (crossing or overtaking)
> is taking place I would use the element <stopActivity>:
> @type="occupationCrossing" for a crossing, and
> @type="occupationBlock" for overtaking. Following the
> definition of these types, they describe "stop caused by
> ...", so these values (and <stopActivity> generally) are
> only to be used for a stopping train.
>
> My question is how to specify the type of connection for the
> not-stopping train? Could stopActivity@type be used for
> passing trains too? As an example, the element
> <stopDescription> is also used if the attribute
> ocpTT@ocpType is set to "pass".
>
> What are your thoughts on this?
> Thanks in advance for your input!
>
> Best regards,
> Janne Möller
|
|
|
|
Members
Search
Help
Login
Home
