Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 3railML 3
  • Issues
  • #392
Closed
Open
Issue created Oct 05, 2020 by Organisation@organisation.GOVOwner

Add operatingRule description

Description

This ticket was raised by Norway as part of the standardization in Norway and shall be used commonly in the future.

This element is a new high-level grouping element introduced in raiLML2.4nor.

For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.26.

Which of the existing elements can be used?

  • none

Optional sub-elements:

  • <childRule> #397

For description of sub-elements see document above, point 4.26.1.

Links

  • Forum discussion:
    • Torben Brand, 04.12.2019: [https://www.railml.org/forum/index.php?t=msg&goto=2283&#msg_2283]
  • Trac tickets:
    • #392
  • Wiki documentation:
    • none

Proposed solution in railML 2.5

Many objects mapped by railML2.4nor have special operating rules. The new trunk element <operatingRules> will group and map those special rules. Only special rules that differ from the generic rule book and apply for specific physical objects are mapped.

The usage of the <operatingRule> element is optional

''agreed between JBD and railML.org on 25.03.2021: put on hold for railML 2 implementation. Need to be investigated in more detail for railML 3.x ''

Proposed solution in railML 3.4

tbd

Edited Jan 13, 2025 by IS Coordination
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany