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
  • #322
Closed
Open
Issue created Mar 12, 2018 by IS Coordination@coordination.ISMaintainer

Mark signal attributes being DEPRECATED

Description

It has been requested in the forum to review the current list of attributes for element as there are some attributes, which are not clear in their usage and which are not properly documented in the railML wiki.

Background

The questioned attributes are:

  • maskableRoute
  • maskableATC
  • sight
  • distNearestDangerPoint

It is assumed that these attributes have some meaning in interlocking related context. Since railML 2.x does not cover interlocking, it is suggested to remove these attributes for railML 2.x and review them for railML 3.x implementation (e.g. as part of interlocking schema).

Links

  • Forum discussion
  • Tobias Bregulla, 12.03.2018: [https://www.railml.org/forum/index.php?t=msg&th=552&goto=1717&#msg_1717]
  • Christian Rahmig, 11.06.2018: [https://www.railml.org/forum/index.php?t=msg&th=583&start=0&]
  • Trac ticket
  • Wiki documentation
  • IS:Signal: [http://wiki.railml.org/index.php?title=IS:signal]

Proposed solution railML 2.4

Mark the following attributes as being DEPRECATED:

  • maskableRoute
  • maskableATC
  • sight
  • distNearestDangerPoint

Proposed solution railML 3.x

Review the meaning of these attributes when discussing the first interlocking related use case. If required, propose a matching model implementation within the railML 3.x interlocking schema and document it in the railML v3 Wiki.

Assignee
Assign to
Time tracking

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