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
  • #460
Closed
Open
Issue created Mar 02, 2021 by IS Coordination@coordination.ISMaintainer

TrainProtectionElement vs ETCS

Description

It must be clarified how ETCS based systems shall be modelled. In particular, the usage of <trainProtectionElement> for ETCS based systems should be questioned.

Background

The discussion was initiated at the railML ETCS use case working group meeting on February 26, 2021.

Links

  • Forum discussion
  • Trac ticket
    • #460 (closed)
  • Wiki documentation
    • IS:trainProtectionElement: [https://wiki3.railml.org/wiki/IS:trainProtectionElement]

Proposed solution railML 3.2

<trainProtectionElement> shall only be used for national and/or legacy train protection systems. ETCS based systems must not be modelled using <trainProtectionElement>.

This has to be clearly documented in the element annotations.

Edited Feb 03, 2025 by CO Coordination
Assignee
Assign to
Time tracking

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