| Re: roles [message #1133 is a reply to message #1131] |
Mon, 12 November 2012 16:15   |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Hi Dirk,
I'm sorry, I don't understand the focus of this posting.
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> Am 12.11.2012, 10:14 Uhr, schrieb Susanne Wunsch <coord(at)commonrailmlorg>:
>> <vehicleOperator .../>
>> <vehicleManufacturer .../>
>> <infrastructureManager .../>
>
> Am 18.10.2012, 11:44 Uhr, schrieb Dirk Bräuer <dirkbraeuer(at)irfpde>:
>> I would prefer not to have pre-defined elements for them at
>> <trainPart>.
I really prefer the pre-defined element list with the background of
systematic XML validation options.
>> Rather, I could imagine a general enumerable list of "<contractor>"
>> or "<partner>" with an attribute for "kind of contractual
>> relationship" =
I already asked for the difference between 'contractor' and 'partner'
but got no satisfactory answer.
>> Aufgabenträger/Auftraggeber/Subauftragnehmer/Caterer...
If you need the appropriate element names which you already offered in
German, I give it a try:
Aufgabenträger: Transport organisation authority (AOT)
Auftraggeber: Customer
Subauftragnehmer: Subcontractor
Caterer: Caterer :-)
I would, of course, extend the element's list with these names if they
really match the needed semantics.
Please ask further for any open points.
Kind regards...
Susanne
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
Members
Search
Help
Login
Home
