Document requirements for exchanging 3.x infrastructure

We discussed how to identify and detect changes (movements) of elements of the functional infrastructure.

  1. producer and consumer of the railML need to have common designators (at least one needs to be understood by both) or UUIDs
  2. functional infrastructure elements need to be absolutely located (e.g. milage). Either by direct usage of a non relative position system, or by indirect usage of such (if the track is described with an absolute length, then intrinsic coordinate related to that track is enough).

We need to document that in the wiki3 at some place where it can easily be found.

First step provide a text to be integrated into the wiki, then identify a proper location then assign to Mr. Leberl for writing the article accordingly.

Links

Edited by IS Coordination

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