| Re: request for an attribute for the Infrastructure Manager of a line [message #323 is a reply to message #316] |
Fri, 29 June 2012 21:30   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Christian,
thank you for the proposal on Infrastructure Manager of a line.
> <line code="..." uicCountryCode="80" imCode="DB-Netz">...
Well, many 'codes', but of course it would fit, so no objection from my
side.
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...
> Refining the attribute "imNumber" into "imCode" as an enumeration list
> with typical infrastructure managers with the free (schema-independent)
> extension possibility (other:xxx):
Assuming the IM is a free character string in the writing program: What
shall the writing program do to map the free character string to the
pre-defined enumeration values? It is possibly demanded a little bit too
much to expect that a program can map all spellings of "DB Netz", "DB Netz
AG", "DB-Netz", "DB-Netz AG", "DB-Netz-AG", "DB Netze" a.s.o. to the
enumeration value.
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...
What should prevent us from writing anything behind "other:", treating the
imCode attribute as a simple string without any mapping? Since there is no
need to ask a central authority (the Scheme coordinator) to use a new
enumeration value, there is also no chance to avoid that two instances use
different enumeration values for the same (new) IM. Consequently, we could
define imCode as a string from the beginning...
---
> <xs:attribute name="[uicCountryCode]" type="rail:tTwoDigits" />
Sometimes it is common practice to allow more-than-two-digit numbers to
code IM which have no official UIC number. It is not a big problem from my
side if we force a UIC-only code here. As earlier discussed in this forum,
it is rather a question of how general RailML should be: Should it be
valid in UIC countries only or outside also? America, Asia, Africa,
Australia?
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. So, we
put forward the original problem but do not solve it: 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.
Best regards,
Dirk.
|
|
|
|
Members
Search
Help
Login
Home
