| Identification in the XML list files and its references (was: small issues on "register" and "tLineInfrastructureManagerCode") [message #1138] |
Thu, 06 December 2012 11:29  |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dear Dirk, Christian and others,
I would like to discuss the general content structure of the separate
XML list file in the 'misc' forum, because it concerns all sub-schemas.
The separate XML list files should be an easier to maintain replacement
for schema-internal enumeration lists.
I will change the already proposed example a bit taking care of the
parallel discussion about attribute- or element-centric XML
styles. Please don't discuss this issue here. The following XML
structure may be easy changed into an attribute-centric one, if that
comes as consensus from the neighbouring thread.
<registers xmlns="http://www.railml.org/lists">
<register id="d1e3">
<version code="ENEE">
<name>European Railway Location Database</name>
<validity/>
<remarks/>
</version>
</register>
<register id="d1e51">
<version code="RL100">
<name>Richtlinie 100</name>
<validity begin="xxxx"/>
<remarks/>
</version>
<version code="DS100">
<name>Drucksache 100</name>
<validity begin="1951" end="xxxx"/>
<remarks/>
</version>
<version code="DV100">
<name>Dienstvorschrift 100</name>
<validity end="1951"/>
<remarks/>
</version>
</register>
</registers>
* Each register would be identified by a file-wide unique 'id'
attribute.
* Each version of a register would be identified by a domain-specific
'code' attribute. This is not a unique string.
The purpose of this list is to constraint the strings for the same
register name, e.g.
recommend "RL100",
not to use "Ril100", "KoRil100", "Ril 100"...
But how to use it?
For the following code snippets the <ocp> context is assumed.
* Should a railML file be meaningful without this list file?
That would mean to refer to the /meaningful/ 'code' value, that is not
unique.
<designator register="RL100" entry="..."/>
* Should a railML file be meaningful only with knowledge of the list
file, only in cases, where its attributes are used?
That would mean to refer to the _unique_ but not /meaningful/ 'id'
value.
<designator registerRef="registers.xml#d1e51" entry="..."/>
* Should both possibilities be provided? If the list file is present, it
may be looked up for further details, if not, the value is
/meaningful/ anyway.
That would mean to refer to both values.
<designator register="RL100" registerRef="registers.xml#d1e51" entry="..."/>
Any comments, questions, concerns, +1, -1 ... appreciated.
Kind regards...
Susanne
Crosspost & Followup-To: railML.misc
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
