Home » railML newsgroups » railml.timetable » [railML2] Extension proposal: new attributes for <category> (category@nor:organizationalUnitRef and categoy@nor:parentRef)
[railML2] Extension proposal: new attributes for <category> [message #2553] Tue, 13 October 2020 12:18 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 156
Registered: March 2016
Senior Member
Dear railML-community,

parentRef
In the Norwegian railway sector, we have defined top-level train categories for data exchange. If there is a need to define more detailed categories in addition to the common top-level categories, they can be added. Any new category will be a sub-category of either a top-level category or another organization-specific one and must be linked to their parent category by using newly introduced attribute @nor:parentRef in railML2.4nor. This way, any new category can be traced to one of the top-level categories.

organizationalUnitRef
Additionally, all new categories should declare the organizational unit that has created it. Therefore, we extended the element <category> by another attribute: @nor:organizationalUnitRef.

If these attributes are of interest for more users, we would welcome a discussion for a possible integration in railML2.5. Any feedback is highly appreciated.

Best regards

Torben Brand
in this topic on behalf of Jernbanedirektoratet and Bane NOR
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 next message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 59
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
Re: [railML2] Extension proposal: new attributes for <category> [message #2600 is a reply to message #2564] Mon, 23 November 2020 21:01 Go to previous message
Torben Brand is currently offline  Torben Brand
Messages: 156
Registered: March 2016
Senior Member
Hi Christian and the rest of the railML-community,

We think that any organisationsUnit that has created a <category> can be referenced.

Adding organization-specific or custom categories
If there is a need to define more detailed categories in addition to the common top-level categories listed above, they can be created by adding new ones. Any new category must be linked to an existing parent category, which can be either a top-level category or another organization-specific one. By following the values of the attribute @nor:parentRef, one must always be able to trace a new category to one of the top-level categories. All new categories must declare the organisational unit that created it.

Charge categories
For charge categories for billing purposes of the access charge (named "produktkode for markedssegmentering» by Bane NOR), make new operational category instances with @nor:parentRef to the relevant operational category listed here.

Marketing categories
For commercial categories to the public for marketing purpose (named "togtype" by Bane NOR), make new product category instances with @nor:parentRef to the relevant product category listed here.

Typical use case in Norway is:
Type of category-Organisation name-Organisation type-Parent Ref:
Operational-Bane NOR-InfrastructureManager-none
Product-Jernbanedirektoratet-customer-none
Charge-Bane NOR-InfrastructureManager-operational
Marketing-Vy-railwayUndertaking-product

Code example:
<categories>
  <category id="c1" code="Pt" name="Persontog"
            trainUsage="passenger"/> 
  <category id="c2" code="T1" name="Trafikkpk.1/SB"
            trainUsage="passenger"
            nor:organizationalUnitRef="[@id for "Bane NOR"]"
            nor:parentRef="c1"/>
  <category id="c3" code="FJ" name="Fjerntog"
            trainUsage="passenger"/>
  <category id="c4" code="Sø" name="Sørtoget"
            trainUsage="passenger"
            nor:organizationalUnitRef="[@id for "GO Ahead"]" 
            nor:parentRef="c3"/>
</categories>
...
<trainpart id="tp1" categoryRef="c4">
...
<train>
 <trainpartSequence categoryRef="c2">
  <trainPartRef ref="tp1"/>

For further explanation of the proposed <category> extensions, please see the railML2.4norTT documentation chapter 4.1 here: https://www.jernbanedirektoratet.no/globalassets/documenter/ railml/20200703_railml2.4norttdocumentation_v1.0.pdf



Kind regards


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


Current Time: Fri Mar 29 07:57:25 CET 2024