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
  • #544
Closed
Open
Issue created May 06, 2024 by TT Coordination@coordination.TTMaintainer

//network/networkResource: unless it turns out that this element is used by someone, deprecate this element

During a review of the current 3.2 model it was noted, that the network resource modelling, that seems to have been taken over from the RTM model, doesnt serve any purpose in railML 3. Normally, NetElements are specified and referenced by a //network/level. However it is also possible to specify networkResources at the same level. It doesnt seem clear what the purpose of this would be. A forum post is to be made for this and if no reply is received, or replies are only in approval of deprecation, the element is supposed to be deprecated with railML 3.3.

Assignee
Assign to
Time tracking

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