Home » railML newsgroups » railml.timetable » [railML2] Extension proposal: new attributes for <category> (category@nor:organizationalUnitRef and categoy@nor:parentRef)
Re: [railML2] Extension proposal: new attributes for <category> [message #2564 is a reply to message #2553] Wed, 28 October 2020 10:04 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Hello Torben,

concerning the addition of the organizationalUnitRef attribute I agree.
It is possible that different operators use the same category names and
that a distinction can therefore only be made on the basis of the
operator. However, we should specify which type of <organizationalUnit>
is to be referenced, e.g. <railwayUndertaking> or <operationalUndertaking>.
With regard to an attribute parentRef I have no general objections, but
I do not yet really understand the use case. Could you give me a few
simple examples, with explanations of how the attributes of the
top-level categories and the subordinate categories interact?

Best Regards
Christian Rößiger
--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: [railML2] Extension proposal: Stopping point reference for elements not of type <stopPost>
Next Topic: [railML2] Organizational units
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun May 12 14:36:20 CEST 2024