Home » railML newsgroups » railml.common » roles
| Re: roles [message #1144 is a reply to message #1135] |
Mon, 11 February 2013 15:03   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hello Andreas, Joachim and others,
Andreas Tanner <ata(at)ivude> writes:
> The requirement of a date was brought in by Joerg von Lingen. I would
> not drop it but anchor it with the binding. Otherwise, to me the
> proposal looks fine.
I just implemented this proposal. [1]
The dates for the vehicle operator binding should better stay at the
"vehicle", not at the "vehicle operator".
> We should agree on a list of "predefined" roles
> (the subelements of <organizationalUnits>) that are sufficiently
> general, including their German pendants and a description for the
> wiki.
>
> Here is a suggestion:
>
> contractor (Auftraggeber) : The authority or enterprise that ordered
> the transportation service, i.e., an integrated transit system
Contractor is a very general term for both sides: costumer and supplier.
-> renamed to "customer", keeping the above explanation
> railwayUndertaking (Verkehrsunternehmen) : The undertaking that is
> commercially responsible for the service
+1
> vehicleOperator, in IVU language this would be subcontractor
> (Fremdunternehmer) : The railway undertaking that operates the
> vehicle, if different from the one that is responsible for the
> commercial service
+1
> - concessionaire (Konzessionsinhaber) ?? Not sure, we use it for bus
> transport.
+1
> - operator (Betreiber) - the unit that is responsible for the
> operational planning of this service
Operator is a very general term for each kind of operation and hard to
distinguish from the "railwayUndertaking". -> renamed to
"operationalUndertaking", keeping the above mentioned explanation
> infrastructureManager (Infrastrukturbetreiber) ...
+1
> vehicleManufacturer (Fahrzeughersteller) ...
+1
Added "contractor" as generic enhancement with additional "role" and
"subLevel" attributes for "catering, cleaning... bindings".
References to this elements will be implemented in a specialized way in the
sub-schemas. [2]
Any comments appreciated.
Kind regards...
Susanne
[1] http://trac.assembla.com/railML/changeset/542
[2] http://trac.assembla.com/railML/ticket/178#comment:4
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Current Time: Thu May 09 01:26:42 CEST 2024
|
Members
Search
Help
Login
Home
