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
  • #517
Closed
Open
Issue created Sep 04, 2023 by IS Coordination@coordination.ISMaintainer

Mileage change review

The information about incoming and outgoing mileage of a mileage change is implicitly defined by the value of the attribute @type (gap / overlap) and the mileage values defined within the spotLocation child elements. Therefore, the attributes @from and @to are redundant and not needed.

Links

  • Discussion:
    • Thomas Nygreen, 10.05.2023: https://www.railml.org/forum/index.php?t=msg&th=904&goto=3085&#msg_3085

Proposed solution railML 3.3

Mark <mileageChange> attributes @from and @to as deprecated.

Assignee
Assign to
Time tracking

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