| Re: [railML2] Adding a new element informationArea to ocp [message #2789 is a reply to message #2787] |
Sat, 10 July 2021 22:11   |
Thomas Nygreen
Messages: 68
Registered: March 2008
|
Member |
|
|
Dear all,
I have two comments:
1: We should avoid two completely different <area> elements in IS (see Christian's comment from 25 June 2021). Of the options listed there, I prefer calling the new element <genericArea>. Another alternative is something like <infrastructureArea>.
2: I find the requirement that the first and final point of a polygon must be identical to be redundant. I suggest skipping this requirement, reducing the multiplicity to 3..∞ and defining that the final edge of the polygon, from the final to the first vertex is implied. In addition to remove redundancy, this also removes the question how to interpret a provided polygon where the first and final vertices do not match. Should anyone still happen to copy the first vertex at the end, the interpretation is still unambiguous and unchanged.
Best regards,
Thomas
Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
