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 71
    • Issues 71
    • 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
  • #189
Closed
Open
Issue created Nov 10, 2012 by IS Coordination@coordination.ISMaintainer

Restructuring references and cross-references for infrastructure elements

In the forum entry [http://www.railml.org/forum/ro/?group=1&offset=0&thread=58&id=234] Susanne suggested to extend the concept of cross-referencing to other infrastructure elements. In preparation of a major release, it is necessary to review all references and cross-references in order to define a more generic concept, which limits redundancy, but provides intuitive usage for all applications.

Assignee
Assign to
Time tracking

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