Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
    • Contributors
    • Graph
    • Compare
  • Issues 82
    • Issues 82
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.org
  • railML 3railML 3
  • Issues
  • #463

Closed
Open
Created Mar 03, 2021 by CO Coordination@coordination.COMaintainer

Sequences of elements changed in interlocking from 3.1 to 3.2alpha

Description

The order of elements within sequences has changed in at least one sequence in the interlocking schema. Thomas is working on a list of all changed sequences per schema and will update the issue ASAP.

See #446 (closed) and #448 (closed) for similar previous issues in the infrastructure schema.

Proposed solution in railML 3.2

For elements that already existed in railML 3.1, the order shall be the same in 3.2, and must be corrected where it has changed.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking

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