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
  • #491
Closed
Open
Issue created Jan 30, 2022 by IL Coordination@coordination.ILMaintainer

Element state in Common

Original proposal

The ElementState and StatesBaseElement as currently defined/used in Infrastructure shall be moved to Common to be available for general use in other subschemas.

Possible solutions

Three possible alternatives have been identified:

  1. Move the base types to Generic and introduce <rollingstockStates> under <rollingstock>, <interlockingStates> under <interlocking> etc., similar to <infrastructureStates> under <infrastructure>.
  2. Move <infrastructureStates> to <common> and rename to <states>. All types of elements can be referenced.
  3. Define states in Common and reverse the direction of the reference, so that all elements can reference defined states with a <validityTime> associated to each reference.
Edited Jun 05, 2024 by CO Coordination
Assignee
Assign to
Time tracking

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