| Re: roles [message #1129 is a reply to message #1127] |
Mon, 12 November 2012 10:14   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Andreas Tanner <ata(at)ivude> writes:
> this issue has moderate urgency. Currently, we use a set of
> proprietary attributes and in fact, these are even customer-specific
> since the roles and their understanding vary between different railway
> companies.
Anyway I try to figure out an XML solution that may fit with your
requirements, following the current way to define railML structures
(with most possible explicit constraints to validate with an XML
validator).
> The contact data is not the main concern, rather the possibility to
> define the legal values that a role can take (the "existing" caterers
> etc.), without additional schemas. But once we have a container, we
> could as well provide full features, and the idea of using an external
> existing scheme for contact data looks great.
My proposal:
New container element in the "Common part" <companies> with specified
child elements that may be referred from within the <trainPart>.
<railml>
<metadata> ...
<companies>
<vehicleOperator id="vo1" name="" startDate="" endDate=""/>
<vehicleManufacturer id="vm1" name=""/>
<infrastructureManager id="im1" name=""/>
<railwayUndertaking id="ru1" name=""/>
<concessionaire id="cc1" name=""/>
<contractor id="cr1" name="" role="catering" subLevel="1"/>
<otherCompany id="" name=""/>
</companies>
...
<timetable...>
...
<trainPart...>
...
<companyBinding>
<railwayUndertaking ref="ru1"/>
<contractor ref="cr1"/>
</companyBinding>
</trainPart>
...
</timetable>
</railml>
Any comments appreciated.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
