Home » railML newsgroups » railml.common » roles
| Re: roles [message #1119 is a reply to message #1118] |
Tue, 16 October 2012 08:58   |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
We currently use the following roles on the trainPart level:
- contractor (Auftraggeber)
- subcontractor (Fremdunternehmer)
- concessionaire (Konzessionsinhaber)
- operator (Betreiber)
All of these come with attributes like address, phone number, licence
number, etc.
That's why, and because the possible roles vary for different users, I
would prefer to model these as separate and referable entities. This
wouldn't be a breaking change, so why not do it for the next minor release?
Best, --Andreas.
Am 15.10.2012 17:46, schrieb Susanne Wunsch:
> Hi Andreas and others,
>
> How about this topic? I want to resume the discussion.
>
> I currently don't see a generic "role-list" for railML 2.2 as there are
> already different positions in the railML-tree for this purpose (not in
> a separate list).
>
> Susanne Wunsch<coord(at)commonrailmlorg> writes:
>> Andreas, you would like to have some "role catalogue" outside the
>> sub-schema for collecting all roles, wouldn't you? How about using XSL
>> or XQuery for such a task with the knowledge of each possible occurence
>> in the sub-schemas?
>>
>> Aahh ... I saw, you bound two roles to the 'trainPart' element. That's
>> really a good point. Let's look, if there are more than one possible
>> role across the schemas. If there are problems (like the attribute in
>> <trainPart>) let's file a ticket about it and change it in the near
>> future.
>
> Do you need some additional "contractor" at the 'trainPart' level?
>
> Other opinions, comments, remarks...?
>
> Kind regards...
> Susanne
>
|
|
|
|
Current Time: Sun Sep 15 07:46:52 CEST 2024
|
Members
Search
Help
Login
Home
