Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal operational properties of an OCP (railML 2.3 infrastructure extension proposal operational properties of an OCP)
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP [message #2763 is a reply to message #2762] Mon, 14 June 2021 23:20 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
Christian Rahmig <coord(at)infrastructurerailMLorg> wrote:
> Dear all,
>
> Torben Brand wrote on Thu, 25 February 2021 09:59
>> The Norwegian railway sector proposes to introduce the
>> extension into railML2.5 under <propOperational>. For a
>> more international and generic clean approach I suggest to
>> split the existing extension attribute @simultaneousEntry
>> into two attributes @hasSimultaneousEntry with the
>> enumeration values: "yes","no" and "partial". The national
>> rule specific type for stations with simultaneous entry
>> can be defined with @simultaneousEntryruleCode.
>>
>> What does the community think?
>
>
> as there has been no objecting feedback by the community, I
> suggest to follow Torben's suggestion. The Trac ticket #416
> [1] already summarizes the railML 2.5 solution proposal.
>
> One thing still need to be clarified: what are the values of
> the enumeration @simultaneousEntry?
>
> Any comment is highly appreciated...
>
> [1] https://trac.railml.org/ticket/416
>
> Best regards
> Christian
>

For this simple approach of mapping the simultanious entry in a station we
suggest the enumeration values to be:
"yes","no", "partial" and "other:"

--
TOBR
 
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: [railML 2.5] state
Next Topic: [railML2] Basic speed profile
Goto Forum:
  


Current Time: Sat Apr 27 13:21:51 CEST 2024