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
  • #441
Closed
Open
Issue created Jan 06, 2021 by IS Coordination@coordination.ISMaintainer

Extension of <opEquipment>

Description

Background

OperationalPoint can reference platforms, tracks, signals, stoppingPlaces and serviceSections, but not switches and derailers.

Links

  • Forum discussion:
    • Heidrun Jost, 29.05.2019: [https://www.railml.org/forum/index.php?t=msg&th=667&start=0&]
  • Trac tickets
    • #441 (closed)
  • Wiki documentation
    • IS:opEquipment: [https://wiki3.railml.org/wiki/IS:opEquipment]
    • CO:ownsInfrastructureElement: [https://wiki3.railml.org/wiki/CO:ownsInfrastructureElement]

Solution proposal railML 3.2

Option 1: extend with specific equipment elements

Element shall be extended with child elements:

  • <ownsSwitch>
  • <ownsStoppingPlace>
  • <ownsDerailer>

Option 2: extend with generic equipment element

Element <opEquipment> shall be extended with a generic child element <ownsInfrastructureElement>

Option 2 is the preferred one.

Edited Feb 19, 2022 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