| Re: request for an attribute for the Infrastructure Manager of a line [message #326 is a reply to message #323] |
Mon, 02 July 2012 08:43   |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Dirk,
> It may be mis-understandable that sometimes a 'code' shall contain
> rather a number and sometimes rather an abbreviation or name. So again
> much depends on good documentation and examples...
Yes, you are right. Therefore, Susanne gave already few examples in her
comment to trac ticket #153 [1].
>> Refining the attribute "imNumber" into "imCode" as an enumeration list
>> with typical infrastructure managers with the free
>> (schema-independent) extension possibility (other:xxx):
>
> [...]
> The problem is that from my opinion, the name or abbreviation of an IM
> is not a typical case for an enumeration. One should assume that they
> can change their names as they do it with their shirts...
> [...]
> Consequently, we could define imCode as a string from the beginning...
I agree with your opinion. On the other side: Wouldn't it be great to
having a list with possible entries instead of thinking about the
spelling of "DB-Netz" or "DB Netz"? All applications may refer to the
enumerations and there is no need for further discussions between the
different applications' users. Of course, if the IM decides to change
his shirt, we should track this change and update the list.
>> <xs:attribute name="[uicCountryCode]" type="rail:tTwoDigits" />
>
> [...]
> With uicCountryCode=tTwoDigits, RailML seams to be usable in continents
> starting with 'E' only but not in continents starting with 'A'. At
> least, the world has more countries than we could code into two digits.
Yes, there are countries that don't have a UIC country code, because
they are not members of the UIC. However, it is possible to map the
whole world to a two-digit code defined as ISO 3166-1 alpha-2 in ISO
3166-1 [2]. If we generalize the attribute 'uicCountryCode' into e.g.
'countryCode' and allow for the alpha-2 codes, railML may become usable
in "A-continents" as well.
> [...] With two
> US-American infrastructure companies both numbering their lines from #1,
> the uicCountryCode attribute does not help us to distinguish uniquely
> between the lines.
For distinguishing betweeen the lines, you need to look at the whole
"key", which consists of the parameters 'uicCountryCode', 'code' and
'imCode'. In your example, the infrastructure companies would have
different values for 'imCode' and thus, their lines could be identified.
[1] https://trac.assembla.com/railML/ticket/152
[2] http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
Regards
---
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
Members
Search
Help
Login
Home
