Home » railML newsgroups » railML.infrastructure » Platforms and ramps for railML 2.2
Re: "Sign code" for stop posts [message #493 is a reply to message #492] Mon, 03 December 2012 20:14 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

> 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".

I would prefer to use the name for notifying that we mean a rule book
number. So what about "ruleBookCode" or "ruleCode"? (Could later become
"ruleRef" if we possibly will have <operationalRules> scheme in far
futuer...)

Best regards,
Dirk.
 
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: Fri Mar 29 08:38:49 CET 2024