DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard
0 stars 0 forks source link

Lexical space of D2Attribute srsName is not well defined #492

Open JosefKaltwasser opened 3 days ago

JosefKaltwasser commented 3 days ago

What happened?

DATEX II allows specifying coordinates which are not ETRS89 in several places:

  1. Attribute srsName in class PointCoordinatesExtended in Level B Extension in Namespace GnssExtension
  2. Attribute srsName in class GmlLineString in Namespace LocationReference They do have slightly different definitions, and none of them clearly specifies the expected lexical space for the String content. Attribute 2 is clearly taken over from GML, and the lexical space is heavily debated on platforms like StackOverflow. Whether Attribute 1 was intended to by a copy from Attribute 2 is not clear, since this class is not tied at all to GML. From interoperability perspective it seems unacceptable to allow modellers to write whatever they want. Would we see "GPS", "WGS84", "EPSG:4326", "http://www.opengis.net/def/crs/EPSG/0/4326" all as valid values (all with the same meaning)? I propose to change both definitions to specify clearly the expected (possibly, not necessarily the same) lexical space. If the agreed definitions allow, this space should be reflected in an according facet.

Version

3

Code of Conduct