Home » railML newsgroups » railML.infrastructure » Platforms and ramps for railML 2.2
Re: "Sign code" for stop posts [message #492 is a reply to message #450] Mon, 03 December 2012 20:05 Go to previous messageGo to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear Susanne and Dirk,

Am 13.11.2012 10:03, schrieb Susanne Wunsch:
> Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
>
>> The attributes of a stop post should be from my side:
> [...]
>> --> 'sign code' or 'rule number' or so (this shall allow to define the
>> Ne5' or 'So8' of DS/DV301 or something like that)
>
> If filed a Trac ticket for this issue in order to clarify it with railML
> 2.2:
>
> http://trac.assembla.com/railML/ticket/198

the so-called "sign code" is a parameter, which belongs to more elements
than just the stop post. Considering the DS/DV301 the name "stop post"
is identical with the codes 'Ne5' or 'So8'.

I suggest to extend the concept of "sign code" to all <signal> and
<stopPost> elements within the <ocsElements> container. Instead of "sign
code" I would name it "ocsCode".

Any comments appreciated...

Regards

--
Christian Rahmig
railML.infrastructure coordinator
 
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 alpha version 3.0.5 available / railML 2.4 announced
Next Topic: Modeling of switches
Goto Forum:
  


Current Time: Sat Apr 20 15:10:36 CEST 2024