| Re: joined continue: "Platforms and ramps for railML 2.2" and "Haltetafel / stop post" [message #382 is a reply to message #296] |
Sat, 06 October 2012 11:58   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Dirk,
in trac ticket [1] I concluded the whole subject on stop posts for an
implementation in railML 2.2 considering most of the ideas mentioned in
the forum entries here and in the original [2].
However, few things are still open, e.g.:
>> The sign code is important, but I would use the parameter "code" for
>> it, which already exists for any ocsElement.
>
> Since 'code' is an inherited attribute, it does naturally not rely to
> any special property of a stop post. It should be saved for more general
> usage, like an external primary key or so. For instance, if you describe
> a point (Weiche) you should use 'code' for the point number
> (Weichennummer) which is the external primary key. You should not write
> the rule book number of the point's signal into 'code'.
How about using the parameter "name" for this? In fact, the element's
type abbreviation is not only interesting for stop posts, but it is also
attached to points (EW, IBW, DKW...) or signals in general (Ra10,
So12...). So, I think, a more global parameter is required? Any comments
appreciated...
[1] https://trac.assembla.com/railML/ticket/167
[2] http://www.railml.org/forum/ro/index.php?group=1&offset= 20&thread=34
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
