| Re: RailML 2 Infrastructure [message #243 is a reply to message #233] |
Fri, 11 February 2011 09:23   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello Simon and Alfonso,
Sorry for the very late follow up. I hoped that the infrastructure
coordinator would reply, but he apparently was really very busy with his
paid job. :-(
Alfonso Gonzalez <alfaeco(at)gmailcom> writes:
> On 15/12/2009 17:59, Simon Kröger wrote:
>> Especially the rail:infraAttrGroups definition doesn't make sense to me
>> - I would guess this should be a container for one or more
>> infraAttrGroup elements that would have IDs and contain InfraAttributes.
>> (If not, please enlighten me)
Sorry, that's broken. We'll fix it with the next upcoming release
(railML 2.1 in March 2011).
>> The other thing that bothers me is the definition of balisegroups. Each
>> balise may have a groupID and ndx but there is also baliseGroup element
>> which could reference up to 8 balises.
Ok, that's the same issue like Alfonso reported these days. We can
reorganize the attributes only for the next major release (railML 3.0),
but there is currently no schedule for this.
But nevertheless we can develop the better structure now and fix it in
an Trac ticket for not losing the idea.
I thought of something like the following:
<balises>
<!-- for single balises (not linked) -->
<balise id="b1" pos="100.0" dir="up" countryID="357"
staticTelegram="..."/>
<balise id="b2" pos="400.0" dir="up" countryID="357"
staticTelegram="..."/>
<!-- for balise groups (linked) -->
<baliseGroup groupID="01">
<balise id="b3" pos="700.0" dir="up" countryID="357" ndx="1"
staticTelegram="..."/>
<balise id="b4" pos="1000.0" dir="up" countryID="357" ndx="2"
staticTelegram="..."/>
<linkingNominal reaction="trainTrip" locationAccuracy="47"/>
<linkingReverse reaction="applyServiceBrake" locationAccuracy="36"/>
</baliseGroup>
</balises>
Please comment with your professional background and expert knowlegde.
(Are there unlinked balise groups? Maybe we have to enable linking* also
for single balises, it is not bound to a balise group, I think.)
>> Now that the line element is gone - or moved to trackGroups - I'm in
>> desperate need of a place to store information that is valid for more
>> than one track (Like e.g. the definition of signal-types and their
>> aspects). I can abuse metadata or maybe better a trackGroup but if there
>> is a better solution i would be happy to know.
I think, the 'trackGroup' is a good place to bind information to more
than one track. It integrates an "any" element which can be used for
your needs.
Hope it helped a bit and to further develop this branch of railML
infrastructure.
read you ...
Susanne
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
