Home » railML newsgroups » railml.common » roles
Re: roles [message #1120 is a reply to message #1118] Thu, 18 October 2012 11:44 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Susanne and Andreas,

> Other opinions, comments, remarks...?

If it is deemed necessary to keep the addresses, phone numbers a.s.o. of
such companies in RailML, I would also (like Andreas) not repeat them at
each <trainPart> nor <vehicle>. So, I agree that we should create a
central "address" list and make cross-references (ref's) to that list _if_
we want to handle them in RailML.

Since there are more possible kinds of companies as
> - contractor (Auftraggeber)
> - subcontractor (Fremdunternehmer)
> - concessionaire (Konzessionsinhaber)
> - operator (Betreiber)

(possibly "Aufgabenträger" but also "catering contractor...") I would
prefer not to have pre-defined elements for them at <trainPart>. Rather, I
could imagine a general enumerable list of "<contractor>" or "<partner>"
with an attribute for "kind of contractual relationship" =
Aufgabenträger/Auftraggeber/Subauftragnehmer/Caterer...

Probably we will first introduce this principle at <trainPart> but later
extend it for <vehicles>, IMs, TOCs. So the "central address list" (list
of "roles") should probably not be situated at <timetable>.

Best regards,
Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Identification in the XML list files and its references (was: small issues on "register" and "tLineInfrastructureManagerCode")
Next Topic: railML Trac hosting?
Goto Forum:
  


Current Time: Wed May 08 19:16:55 CEST 2024