Home » railML newsgroups » railML.infrastructure » Platforms and ramps for railML 2.2
Re: "Sign code" for stop posts [message #511 is a reply to message #493] Fri, 18 January 2013 11:32 Go to previous messageGo to previous message
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Dear Dirk and Christian,

Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
>> 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".
>
> Agreed. But more general, this applies not only to <ocsElements> but
> also to (at least some) <trackElements> so please do not call it
> "ocsCode".

Which other elements do also apply to get the new attribute?

I just implemented the optional attribute 'ruleCode' of type xs:string
for the elements 'stopPost' and 'signal'. [1] [2]

Please check out, if this implementation fulfills your needs.

Kind regards...
Susanne

[1] http://trac.assembla.com/railML/changeset/529
[2] https://trac.assembla.com/railML/ticket/198
 
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 08:45:42 CEST 2024