Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
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
  • #407
Something went wrong while setting issue due date.
Closed
Open
Issue created 4 years ago by Organisation@organisation.GOVOwner
  • New related issue

  • New related issue

Add revision description to a project

Open

Add revision description to a project

Description

This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.

is a sub-element of the high-level element (see trac ticket #390), both were introduced in railML 2.4nor. This element further defines the revision of a project. In addition to a selection of the common attributes listed in chapter 3.7 (document linked below), this element has the following attribute: @initialProjectRef.

For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.13.3.

Which of the existing elements can be used?

  • none

The sub-element has the following optional sub-elements:

  • (#409)
  • (#410)
  • (#411)
  • (#412)

For description of sub-elements see document above, point 4.13.3.

Background

[…]

Links

  • Forum discussion:
  • […]
  • Trac tickets:
  • #407
  • Wiki documentation:
  • none

Proposed solution in railML 2.5

tbd

Edited 2 years ago

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • O
      Organisation @organisation.GOV · 4 years ago
      Author Owner
      • Description changed
        == Description ==
        
        This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
        
        <revision> is a sub-element of the high-level element <project> (see trac ticket #390), both were introduced in railML 2.4nor. This element further defines the revision of a project. In addition to a selection of the common attributes listed in chapter 3.7 (document linked below), this element has the following attribute: @initialProjectRef.
        
        For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.13.3.
        
        Which of the existing elements can be used?
        
        * none
        
        The sub-element has the following optional sub-elements:
        
      - * <objectRevised> (#)
      + * <objectRevised> (#409)
      ?                     +++
      
      - * <revisedBy> (#)
      + * <revisedBy> (#410)
      ?                 +++
      
      - * <checkedBy> (#)
      + * <checkedBy> (#411)
      ?                 +++
      
      - * <approvedBy> (#)
      + * <approvedBy> (#412)
      ?                  +++
      
        
        For description of sub-elements see document above, point 4.13.3.
        
        === Background ===
        
        […]
        
        === Links ===
        
        * Forum discussion:
         * […]
        * Trac tickets:
         * #407
        * Wiki documentation:
         * none
        
        == Proposed solution in railML 2.5 ==
        
        tbd
    • Coordination
      Coordination @coordination.GOV · 4 years ago
      Owner
      • Owner set to @coordination.CO
      • Status changed from new to assigned
    • CO Coordination
      CO Coordination @coordination.CO · 3 years ago
      Maintainer

      Committed to railML2.5-beta2 branch in [1241]. Wiki updates remaining.

    • TT Coordination mentioned in issue #412 2 years ago

      mentioned in issue #412

    • TT Coordination mentioned in issue #409 2 years ago

      mentioned in issue #409

    • TT Coordination mentioned in issue #410 2 years ago

      mentioned in issue #410

    • TT Coordination mentioned in issue #411 2 years ago

      mentioned in issue #411

    • TT Coordination changed the description 2 years ago

      changed the description

    • TT Coordination changed milestone to %2.5 2 years ago

      changed milestone to %2.5

    • TT Coordination removed 2.5 label 2 years ago

      removed 2.5 label

    Please register or sign in to reply
    Assignee
    CO Coordination's avatar
    CO Coordination
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets

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