How to deal with UUIDs

Background:

railML3.2 has id attribute as union of XML id and UUID. This creates issues for type recognition, interpretation during import, XML validation and code generation.

Proposed solution:

create a new UUID attribute

  • Remove UUIDs from the tID and tRef types.
  • Create a new entry in Registers.xml to include UUID as a designator.
  • Ensure that all relevant entities offer <designator>
  • Avoid required elements and attributes as siblings to <designator>, to enable elements that are empty husks only containing id and <designator>

Links:

Edited by CO Onto

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