Skip to content
GitLab
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
  • #390
Closed
Open
Issue created Sep 25, 2020 by Organisation@organisation.GOVOwner

Add project description

Description

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

This element is a new high-level grouping element introduced in raiLML2.4nor.

The element describes the purpose of the infrastructure objects which are part of a model. One can have multiple projects ().

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

Which of the existing elements can be used?

  • none
  • Integration of DublinCore V2 to be checked.

Sub-elements:

  • (#405)
  • (#406)
  • (#407)
  • (#408)

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

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

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

For description of sub-elements see document above, pages 53-55.

Background

Introduced in railML2.4nor to describe the purpose of the infrastructure objects which are part of a model.

Semantic constraint: There shall be only one version of , , , ... per file and they shall be consistent.

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, 15.03.2021 [https://www.railml.org/forum/index.php?t=msg&goto=2682]
  • Trac tickets:
  • #390
  • Wiki documentation:
  • none

Proposed solution in railML 2.5

tbd

Proposed solution in railML 3.2

tbd

Assignee
Assign to
Time tracking

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