Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • 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 2railML 2
  • Issues
  • #252
Closed
Open
Issue created May 26, 2014 by IS Coordination@coordination.ISMaintainer

Restructuring TAP TSI infrastructure information

Stefan Jugelt from ERA suggested in the forum (see [http://www.railml.org/forum/ro/index.php?group=1&offset=0&thread=79&id=398]) to modify the storage of TAP TSI relevant information in the infrastructure (codes):

In particular: The element "tsi" in operationalControlPoints/ocp/ and the type "tOcpTsi" shall be marked as deprecated and removed in further versions of railML. These elements dedicated for the usage in conjunction with TAP TSI shall be replaced by a more generic approach (new register named "Primary Location Code").

Assignee
Assign to
Time tracking

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