| Re: roles [message #1103 is a reply to message #1102] |
Thu, 15 March 2012 14:46   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Andreas Tanner <ata(at)ivude> writes:
Hi Andreas,
> In RailML, we have different attributes and elements for roles:
> - "owner" in InfraAttrGroups and "ownerChanges", both used for tracks
> - "manufacturer" and "operator" (element) for vehicles,
> - "operator" (attribute) for trainParts
Yes, it's done in different ways across the subschemas.
> I think it would be wise to introduce a dedicated type for "roles" and
> provide slots for id references at the appropriate locations. Maybe a
> string enumeration type would work for the names of the different
> roles. Even better, we could provide container elements as used in the
> vehicle classification everywhere.
I try to figure out, what you want to get. The following XML snippets
try to show your wishes. Please correct me, if I'm wrong with my
implementation.
<infrastructure>
...
<infraAttributes>
<owner id="im_12345" name="Die Bahninfrastruktur"
role="infrastructureManager"
uicNumber="foo"/>
..
<track>
...
<ownerChange id="im_54321" name="Schweizerische Bahn"
role="infrastructureManager"
uicNumber="bar"/>
...
</infrastructure>
<rollingstock>
...
<vehicle>
<classification>
<manufacturer id="m_123" name="Bombardjee"
role="manufacturer"
serial_number="123.456.78"/>
<operator id="o_123" name="EmErCeE-DispoLok"
role="rollingstockOperator"
class="baz"
startDate="2012-01-01" endDate="2012-12-31"/>
...
</rollingstock>
<timetable>
...
<trainPart>
<operator id="op_123" name="Der Bahnbetreiber"
role="railwayUntertaking"/>
...
</timetable>
My first step is some clarification, afterwards I would comment it.
Thanks for your idea and kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
