| Re: roles [message #1143 is a reply to message #1129] |
Fri, 08 February 2013 13:52   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi,
let me summarize the current discussion. You are suggesting a subelement
below <trainPart>:
<timetable...>
...
<trainPart...>
...
<organizationalUnitBinding>
<railwayUndertaking ref="ru1"/>
<contractor ref="cr1"/>
<concessionaire ref="cc1"/>
<vehicleOperator ref="vo1"/>
<operator ref="op1"/>
<infrastructureManager ref="im1"/>
<other:somethingElse ref="se1"/>
</organizationalUnitBinding>
</trainPart>
...
</timetable>
</railml>
The other possibility suggested by Dirk would look like:
<organizationalUnitBinding>
<organizationalUnitBinding type="railwayUndertaking" ref="ru1"/>
<organizationalUnitBinding type="other:somethingElse" ref="se1"/>
</organizationalUnitBinding>
I would prefer the first way of describing, because the types of
organizationalUnitBindings are quite fixed and both methods are
expandable. Its also better to have separated lists for the
railwayUndertakers and operators etc. instead of one giant list of
organizations with an additional type to distiguish between catering
companies and raiway undertakers.
If there is a consense I could implement the timetable part within 2.2 (or
within 2.x).
Kind regards,
Joachim
-------------------------------------
Joachim Rubröder
Schema Coordinator: railML.timetable
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
