Skip to content
GitLab
Open
Issue created by Organisation@organisation.GOVOwner

Add border type "project"

Open

Add border type "project"

Description

The element shall be used to define the border of an infrastructure project. It is suggested to extend the enumeration for attribute @type.

Background

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

It is a sub-element of , which belongs to , a high-level element of railML2.4.

The railML2.4 element is used in railML2.4nor to define the borders of projects, as described in chapter 4.12 (document link below). Please note that in railML2.4nor the element is only used to model the project area of the defined areas in chapter 4.9 (document link below). The borders of all further areas are modelled by references to existing infrastructure elements, e.g. interlocking elements.

The railML2.4 element is not extended by attributes. However, a new value for the enumeration attribute @type is introduced: “other:project”.

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

Links

Proposed solution in railML 2.5

The enumeration attribute @type shall be extended with a new value "project" to allow for modelling borders between infrastructure projects.

Proposed solution in railML 3.2

tbd

Edited

    Tasks

    0

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

    Activity

    • O
      Organisation @organisation.GOV ·
      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.
  
- It is a sub-element of <trackTopology>, which belongs to <ocp>, a high-level element of railML2.4.
?                                                           ^ ^

+ It is a sub-element of <trackTopology>, which belongs to <track>, a high-level element of railML2.4.
?                                                           ^^^ ^

  
  The railML2.4 <border> element is used in railML2.4nor to define the borders of projects, as described in chapter 4.12 (document link below). Please note that in railML2.4nor the <border> element is only used to model the project area of the defined areas in chapter 4.9 (document link below). The borders of all further areas are modelled by references to existing infrastructure elements, e.g. interlocking elements.
  
  The railML2.4 <border> element is not extended by attributes. However, a new value for the enumeration attribute @type is introduced: “other:project”.
  
  For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.12.
  
  Which of the existing elements can be used?
  
  * <border>
  
  === Background ===
  
  […]
  
  === Links ===
  
  * Forum discussion:
   * […]
  * Trac tickets:
   * #418
  * Wiki documentation:
   * none
  
  == Proposed solution in railML 2.5 ==
  
  tbd
    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer
      • Description changed
        == Description ==
+ 
+ The <border> element shall be used to define the border of an infrastructure project. It is suggested to extend the enumeration for attribute @type. 
+ 
+ === Background ===
  
  This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
  
  It is a sub-element of <trackTopology>, which belongs to <track>, a high-level element of railML2.4.
  
  The railML2.4 <border> element is used in railML2.4nor to define the borders of projects, as described in chapter 4.12 (document link below). Please note that in railML2.4nor the <border> element is only used to model the project area of the defined areas in chapter 4.9 (document link below). The borders of all further areas are modelled by references to existing infrastructure elements, e.g. interlocking elements.
  
  The railML2.4 <border> element is not extended by attributes. However, a new value for the enumeration attribute @type is introduced: “other:project”.
  
  For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.12.
  
- Which of the existing elements can be used?
- 
- * <border>
- 
- === Background ===
- 
- […]
- 
  === Links ===
  
  * Forum discussion:
   * […]
  * Trac tickets:
   * #418
  * Wiki documentation:
-  * none
+  * IS:border: [https://wiki2.railml.org/wiki/IS:border]
  
  == Proposed solution in railML 2.5 ==
  
- tbd
+ The enumeration attribute @type shall be extended with a new value "project" to allow for modelling borders between infrastructure projects.

      restructuring ticket and adding link to wiki

    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer
      • Description changed
        == Description ==
  
  The <border> element shall be used to define the border of an infrastructure project. It is suggested to extend the enumeration for attribute @type. 
  
  === Background ===
  
  This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
  
  It is a sub-element of <trackTopology>, which belongs to <track>, a high-level element of railML2.4.
  
  The railML2.4 <border> element is used in railML2.4nor to define the borders of projects, as described in chapter 4.12 (document link below). Please note that in railML2.4nor the <border> element is only used to model the project area of the defined areas in chapter 4.9 (document link below). The borders of all further areas are modelled by references to existing infrastructure elements, e.g. interlocking elements.
  
  The railML2.4 <border> element is not extended by attributes. However, a new value for the enumeration attribute @type is introduced: “other:project”.
  
  For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.12.
  
  === Links ===
  
  * Forum discussion:
-  * […]
+  * Torben Brand, 20.12.2018: [https://www.railml.org/forum/index.php?t=msg&th=626&goto=2051&#msg_2051]
  * Trac tickets:
   * #418
  * Wiki documentation:
   * IS:border: [https://wiki2.railml.org/wiki/IS:border]
  
  == Proposed solution in railML 2.5 ==
  
  The enumeration attribute @type shall be extended with a new value "project" to allow for modelling borders between infrastructure projects.

      adding link to forum

    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer
      • Summary changed from Add value to in to Add border type "project"
    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer
      • Description changed
        == Description ==
  
  The <border> element shall be used to define the border of an infrastructure project. It is suggested to extend the enumeration for attribute @type. 
  
  === Background ===
  
  This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.
  
  It is a sub-element of <trackTopology>, which belongs to <track>, a high-level element of railML2.4.
  
  The railML2.4 <border> element is used in railML2.4nor to define the borders of projects, as described in chapter 4.12 (document link below). Please note that in railML2.4nor the <border> element is only used to model the project area of the defined areas in chapter 4.9 (document link below). The borders of all further areas are modelled by references to existing infrastructure elements, e.g. interlocking elements.
  
  The railML2.4 <border> element is not extended by attributes. However, a new value for the enumeration attribute @type is introduced: “other:project”.
  
  For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.12.
  
  === Links ===
  
  * Forum discussion:
   * Torben Brand, 20.12.2018: [https://www.railml.org/forum/index.php?t=msg&th=626&goto=2051&#msg_2051]
+  * Torben Brand, 09.04.2021: [https://www.railml.org/forum/index.php?t=msg&th=576&goto=2690&#msg_2690]
  * Trac tickets:
   * #418
  * Wiki documentation:
   * IS:border: [https://wiki2.railml.org/wiki/IS:border]
  
  == Proposed solution in railML 2.5 ==
  
  The enumeration attribute @type shall be extended with a new value "project" to allow for modelling borders between infrastructure projects.
+ 
+ == Proposed solution in railML 3.2 ==
+ 
+ _tbd_

      add link to new forum post by Torben Brand (09.04.2021) and adding empty section for railML 3.x solution proposal

    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer

      In [changeset:"1138/railML"]:

      adding new border type "project", see #418
    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer
      • Status changed from new to accepted

      border type "project" has been added in enumeration; documentation in wiki is pending

    • IS Coordination
      IS Coordination @coordination.IS ·
      Maintainer

      re-assigned ticket to Mr. Ferri Leberl who is responsible for the Wiki documentation

    • Documentation
      Documentation @documentation.GOV ·
      Maintainer

      @coordination.IS Please, check

    • Documentation changed the description

      changed the description

    • Documentation removed Wiki label

      removed Wiki label

    • Documentation assigned to @coordination.IS and unassigned @root

      assigned to @coordination.IS and unassigned @root

    • TT Coordination changed milestone to %2.5

      changed milestone to %2.5

    • TT Coordination removed 2.5 label

      removed 2.5 label

    Please register or sign in to reply

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