| Re: suggestion for improved use of infraAttrGroups [message #533 is a reply to message #531] |
Sun, 02 June 2013 22:03   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Dear Bob,
thank you for your message and also for introducing yourself to the
reading community. As the railML infrastructure coordinator I welcome
you to the railML forum.
Concerning your idea:
Am 29.05.2013 11:29, schrieb Bob Janssen:
> Dear all,
>
> the tag infraAttrGroups is a container for pre-defined infrastructure
> attributes. One would use it to mark e.g. all tracks that have a common
> property, e.g. traction 25kV or similar gauge.
>
> In a way, this is similar to unix groups. A user belongs to group "lp,
> printer, scanner group".
> I think this is the idea behind infraAttrGroups. At present, <track> has
> an attribute infraAttrGroupRef. In other words, it is not possible to
> create a relation between one <track> and more than one <infraAttrGroup>.
> If a track points to more than one infraAttrGroups, we could emulate the
> unix-style group usage. This implies that <track> needs a 0..n children
> <infraAttrGroupRef>
>
> How about it ?!
I was waiting few days to see if other users will comment on it. I
personally like your idea very much. And I think, that others would
agree if they really used the infraAttrGroups. By changing the reference
to such an infraAttrGroup from the <track>'s attribute
"infraAttrGroupRef" to a child element <infraAttrGroupRef> the
infraAttrGroup may become more usable in practice.
Therefore, I would like to ask the other users: What do you think about
Bob's idea? Let's implement it for railML 2.3? Any comments appreciated...
>
> ps. this is my first and probably not my last contribution !
I am looking forward to your next idea :)
Regards
--
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
