| Re: [railML2] Extension proposal: new attributes for <category> [message #2600 is a reply to message #2564] |
Mon, 23 November 2020 21:01  |
Torben Brand
Messages: 158
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
|
|
|
|
Members
Search
Help
Login
Home
