| Balise / baliseGroups : structure & attributes [message #329] |
Wed, 04 July 2012 19:23  |
pierre.simon
Messages: 8
Registered: July 2012
|
Junior Member |
|
|
Conceptually a balise belongs to one and only one balise group. So why not
create the parent node <baliseGroup> having a list of 1..8 balises ?
On top of that, attributes like countryID which today is attached to
<balise> could be move the parent node <baliseGroup> (+ some additional
attributes like
- idBaliseGroup
- its type (in Belgium we have Infill Balise Group / Signal Balise Group /
Technical Fixed Balise Group / Technical Switchable Balise Group)
- its reference to the signal (xs:IDRef)
Plus a balise group will have some function(s) and textMessage(s)
For instance we can have:
<baliseGroup id="id1" name="d" pos="4" dir="up" absPos="4"
application="ETCS" nidBg="1" nidC="251" type="IBG" signalRef="id12873">
<balise baliseType="Fixed" nPig="1"/>
<balise baliseType="Switchable" nPig="0"/>
</baliseGroup>
Is it possible to review the model of the <baliseGroup> element in the
next railML version ?
[de: Eine Balise gehoert immer zu einer Balisengrppe. Somit koennte man
Attribute der Balisen in die Balisengruppe verschieben, um sie nicht in
der Balise zu wiederholen. Es koennen bis zu 8 Balisen pro Balisengruppe
erscheinen.]
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
