| Re: small issues on "register" and "tLineInfrastructureManagerCode" [message #485 is a reply to message #475] |
Mon, 03 December 2012 14:06   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Christian Rahmig <coord(at)infrastructurerailmlorg> writes:
>> As agreed at the meeting in Zurich we will implement a free string
>> attribute in the XML Schema, but provide an additional XML file with
>> pre-defined values for this attribute.
I would suppose the following structure for the pre-defined registers in
the extra XML file:
<registers xmlns="http://www.railml.org/lists">
<register id="d1e3">
<version>
<code>ENEE</code>
<name>European Railway Location Database</name>
<validity/>
<remarks/>
</version>
</register>
<register id="d1e51">
<version>
<code>RL100</code>
<name>Richtlinie 100</name>
<validity begin=""/>
<remarks/>
</version>
<version>
<code>DS100</code>
<name>Drucksache 100</name>
<validity begin="1951" end=""/>
<remarks/>
</version>
<version>
<code>DV100</code>
<name>Dienstvorschrift 100</name>
<validity end="1951"/>
<remarks/>
</version>
</register>
</registers>
This would be used in the 'ocp':
<ocp>
...
<designator register="RL100" entry="...">
</ocp>
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
