Sequences of elements changed in infrastructure from 3.1 to 3.2alpha

Description

The order of elements within sequences has changed in multiple sequences. Identified in infrastructure, rtm4railml3 and gml4railml3 schemas. Thomas is working on a list of all changed sequences per schema and will update the issue ASAP.

See #446 (closed) and #448 (closed) for similar previous issues.

Proposed solution in railML 3.2

For elements that already existed in railML 3.1, the order shall be the same in 3.2, and must be corrected where it has changed.

• Description changed

  == Description ==
  
  The order of elements within sequences has changed in multiple sequences. Identified in infrastructure, rtm4railml3 and gml4railml3 schemas. Thomas is working on a list of all changed sequences per schema and will update the issue ASAP.
  
+ See #446 and #448 for similar previous issues.
+ 
  == Proposed solution in railML 3.2 ==
  
  For elements that already existed in railML 3.1, the order shall be the same in 3.2, and must be corrected where it has changed.

changed milestone to %3.2

removed 3.2b1_ETCS label

assigned to @coordination.CO and unassigned @coordination.IS

Is there still sth to do for me?

I fixed these issues in infrastructure, rtm and common. rtm to the point where it affects infrastructure. so i think this could be closed although i would prefer it if someone could crosscheck my changes.

3.2 was published, so this is outdated

closed