Peter Baumann

@manolama sounds great - can you advise me about next steps?

> Are these correct? If so, it's impossible to CURIEize these, since the "OGC" prefix can't map to both "http://www.opengis.net/def/crs/OGC/1.3/" and "http://www.opengis.net/def/crs/OGC/0/". Unless I'm misunderstanding how CURIEs work. Indeed, as...

@pvretano I was just reporting the decision by OGC-NA at that time. But personally I see no problem in having 2 paths from a CURIE leading to a single result.

@pvretano > Our confusion on the matter might be less so if we could get a list of OGC CURIE prefixes but so far I have been unable to coax...

@pomakis @ghobona thanks for this big effort, Keith! IMHO this underlines the need for a concerted synchronization action under the lead of OGC-NA, resulting in a single authoritative repository modified...

@pomakis > Is saving 29 highly-compressible bytes really worth the complication of allowing CURIEs and breaking RFC 8288? yes. not for machines, but for humans. By way of history, from...

Hi @selmaVH1 , thanks for your quick response. The old issue IMHO can be closed because 2 (other) working WCS 2.x plugins exists in the repo meanwhile. A main issue...

verified now that the core WCS plugin indeed supports 1.x, see source file: https://github.com/qgis/QGIS/pull/54707/commits/4c36f297deaf9f31b702aed99df3af450c44055c#diff-b963b7c25674c9626e171d652b8c8c2ba7f1e7fc5ecdb6a4c7f033be6222867c line 1000 onwards

> [@pebau](https://github.com/pebau) Is there a reason why the support of WCS 2.x can't land in QGIS core? no reason, just the QGIS OK is needed, then we can contribute. Some...

@selmaVH1 > There’s a general “rule” not to document external plugins inside the official QGIS documentation understood, makes sense. Now that we have to work on it anyway (the existing...