<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table cellpadding="0" cellspacing="0" border="0"
class="moz-email-headers-table">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>Re: OGC Compliance Renewal Notification - 60 Day
Expiration Notice</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Sun, 5 Jan 2025 16:18:23 +0200</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><tzotsos@osgeo.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td>Micah Brachman <a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mbrachman@ogc.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">CC: </th>
<td>Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>, Even
Rouault <a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><even.rouault@spatialys.com></a>, Compliance
<a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>, <a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>, OSGeo Board
<a class="moz-txt-link-rfc2396E" href="mailto:board@lists.osgeo.org"><board@lists.osgeo.org></a>, Tom Kralidis
<a class="moz-txt-link-rfc2396E" href="mailto:tomkralidis@gmail.com"><tomkralidis@gmail.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
Dear Micah,<br>
<br>
We have gathered all compliance tests and we are ready to submit.<br>
<br>
Here is our status list, I would like to ask some questions:<br>
<br>
Under the OSGeo organization we have several products listed in
the OGC<br>
compliance page.<br>
1. For MapServer we have versions 5.0, 6.0, 6.2, 6.4, 7.0, 8.2<br>
Only 6.2 has passed certification in the past so I assume we keep
that<br>
listed.<br>
I added the latest 8.2 release that includes support for OGC API
Features<br>
(no cite tests yet).<br>
<br>
2. For pygeoapi we have versions 0.7, 0.9, 0.17 and 0.19<br>
We have provided new compliance tests against the latest 0.19
version and<br>
we would like to ask to move reference implementation status (OGC
API -<br>
Features, OGC API - Processes and OGC API - Tiles) to that version
. Is<br>
that possible?<br>
We did not manage to run new tests for OGC API - EDR so we would
like to<br>
keep RI to the previous pygeoapi 0.9 version for now.<br>
<br>
3. For pycsw we have versions 1.1, 2.0, 2.2, 2.4 and 2.6<br>
We provided certification tests against the latest version and we
would<br>
like to keep that version as CSW 2.0.2 and 3.0.0 reference
implementation.<br>
OGC API Records is implemented in pycsw 3.0.0 (not yet released as
final).<br>
We are waiting for the specification to be finalized and looking
forward to<br>
testing against a Records cite test.<br>
<br>
4. GDAL/OGR we have versions 1.11, 2.1, 2.4, 3.0 and now 3.10<br>
We provided certification tests against the latest version (3.10)
and we<br>
would like to ask to move all reference implementation status to
that<br>
version. Is that possible?<br>
<br>
5. For GeoServer we have version 2.24<br>
We do not have new compliance tests available so we would like to
keep<br>
version 2.24 listed.<br>
<br>
Best regards,<br>
Angelos<br>
<br>
<br>
On Wed, Nov 13, 2024 at 7:09 PM Micah Brachman
<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mbrachman@ogc.org></a> wrote:<br>
<br>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">That sounds great, Angelos – please let me know if you have any questions
or need assistance.
*From: *Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>
*Date: *Wednesday, November 13, 2024 at 6:39 AM
*To: *Micah Brachman <a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mbrachman@ogc.org></a>, Even Rouault <
<a class="moz-txt-link-abbreviated" href="mailto:even.rouault@spatialys.com">even.rouault@spatialys.com</a>>, Compliance <a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>,
<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>
*Cc: *Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><tzotsos@osgeo.org></a>, OSGeo Board <
<a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a>>
*Subject: *Re: OGC Compliance Renewal Notification - 60 Day Expiration
Notice
Hi Micah,
Thank you for the update.
I am going to submit once I gather info from all projects involved.
Best,
Angelos
On 11/13/24 02:48, Micah Brachman wrote:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Thanks for sharing these, Even.
Angelos-
I can see that you have submitted the last few compliance results. Are
</pre></blockquote>you planning to submit these as well?
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Best,
Micah
Micah Brachman, PhD
Community Manager | Open Geospatial Consortium (OGC)
+1 (508) 655-5858<a class="moz-txt-link-rfc2396E" href="tel:+15086555858"><tel:+15086555858></a> ex 706
mbrachman<a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org"><mailto:mbrachman@ogc.org></a>@ogc.org<<a class="moz-txt-link-freetext" href="mailto:mbrachman@ogc.org">mailto:mbrachman@ogc.org</a>
</pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:mbrachman@ogc.org%3e@ogc.org%3cmailto:mbrachman@ogc.org"><mbrachman@ogc.org%3e@ogc.org%3cmailto:mbrachman@ogc.org></a>> | ogc.org<a class="moz-txt-link-rfc2396E" href="http://ogc.org/"><
http://ogc.org/></a> | @opengeospatial
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
From: Even Rouault <a class="moz-txt-link-rfc2396E" href="mailto:even.rouault@spatialys.com"><even.rouault@spatialys.com></a>
Date: Monday, November 11, 2024 at 3:56 PM
To: Compliance <a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>, <a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><info@osgeo.org></a>
Cc: Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@osgeo.org"><tzotsos@osgeo.org></a>, OSGeo Board <
</pre></blockquote><a class="moz-txt-link-abbreviated" href="mailto:board@lists.osgeo.org">board@lists.osgeo.org</a>>, Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:gcpp.kalxas@gmail.com"><gcpp.kalxas@gmail.com></a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
</pre></blockquote>Notice
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Hi,
here are the results of running CITE tests for GDAL *3.10* :
- KML 2.2: s0028, s0029, s0030, s0031
- GeoTIFF 1.1: s0032 and s0033
- GMLJP2 v2: s0034
- GeoPackage 1.2: s0035, s0036, s0037 and s0038
Even
Le 10/11/2024 à 16:07, <a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><<a class="moz-txt-link-freetext" href="mailto:compliance@ogc.org">mailto:compliance@ogc.org</a>
</pre></blockquote><a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>> a écrit :
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">Open Source Geospatial Foundation
This is an automated email to inform you that your OGC-certified
</pre></blockquote>compliance license(s) for the following products are due to be renewed by
January 9th, 2025. After that date, your products will no longer be listed
as certified OGC compliant and you may not claim that they are compliant.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Since you have reference implementations in your listings please be
</pre></blockquote>aware of the following:
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
* You need to retest if you want to continue being listed as a
</pre></blockquote>reference implementation.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"> * If you want to provide a new version as a reference
</pre></blockquote>implementation you need to test that new version. The older version will no
longer hold the status of reference implementations.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre"> * If you want to continue displaying the certification for the
</pre></blockquote>older version of your product, then you will be required to pay for the
certification.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
Additional expiration warnings may be sent to you 1 month and 2 weeks
</pre></blockquote>prior to expiration, please begin the renewal process as soon as possible.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
We invite you to easily renew online in our implementation portal:
</pre></blockquote><a class="moz-txt-link-freetext" href="https://www.ogc.org/resource/products/registration">https://www.ogc.org/resource/products/registration</a>
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
As a reminder, the account used to manage your certification listings
</pre></blockquote>is: osgeo (<a class="moz-txt-link-abbreviated" href="mailto:info@osgeo.org">info@osgeo.org</a><a class="moz-txt-link-rfc2396E" href="mailto:info@osgeo.org"><mailto:info@osgeo.org></a>)
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
If you have any questions please send an email to <a class="moz-txt-link-abbreviated" href="mailto:compliance@ogc.org">compliance@ogc.org</a><
</pre></blockquote><a class="moz-txt-link-freetext" href="mailto:compliance@ogc.org">mailto:compliance@ogc.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:compliance@ogc.org"><compliance@ogc.org></a>>. The OGC compliance team
will be more than glad to help you.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
________________________________
Current OGC-Compliant Listings
GDAL/OGR 1.11
Specification(s)
Original Certification
OGC KML 2.2.0
(OGC Reference Implementation)
2014-08-15
OGC KML (Level 2) 2.2.0
(OGC Reference Implementation)
2014-08-15
OGC KML (Level 3) 2.2.0
(OGC Reference Implementation)
2014-08-15
GDAL/OGR 3.0.0
Specification(s)
Original Certification
OGC GeoTIFF Standard 1.1
(OGC Reference Implementation)
2020-07-29
OGC KML 2.2.0
(OGC Reference Implementation)
2020-01-09
OGC KML (Level 2) 2.2.0
(OGC Reference Implementation)
2020-01-09
OGC® GeoPackage Encoding Standard 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Extension Mechanism 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Features 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: Metadata 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GeoPackage Encoding Standard: RTree Spatial Indexes 1.2
(OGC Reference Implementation)
2022-01-09
OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core 2.0
(OGC Reference Implementation)
2020-04-28
GeoServer 2.24
Specification(s)
Original Certification
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
</pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
</pre></blockquote>Parameters 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data
</pre></blockquote>Identification 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
</pre></blockquote>Observation 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
</pre></blockquote>Observation Collection 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Geometry 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Links 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Metadata
</pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Offering 1.0
(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Product
</pre></blockquote>Information 1.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2024-01-09
OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Properties 1.0
(OGC Reference Implementation)
2024-01-09
MapServer 6.2
Specification(s)
Original Certification
OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
(OGC Reference Implementation)
2016-01-12
pycsw 2.4.0
Specification(s)
Original Certification
OpenGIS Catalogue Service Implementation Specification [Catalogue
</pre></blockquote>Service for the Web] 2.0.2
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2020-01-09
pycsw 2.6.0
Specification(s)
Original Certification
OGC GeoRSS Encoding Standard 1.0
(OGC Reference Implementation)
2022-04-28
OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
(OGC Reference Implementation)
2021-01-09
OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
</pre></blockquote>(OpenSearch) 3.0
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2021-01-09
OpenGIS Catalogue Service Implementation Specification 2.0.2
(OGC Reference Implementation)
2021-01-09
OpenGIS Catalogue Service Implementation Specification [Catalogue
</pre></blockquote>Service for the Web] 2.0.2
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">(OGC Reference Implementation)
2021-01-09
pygeoapi 0.17.0
Specification(s)
Original Certification
OGC API - Processes - Part 1: Core 1.0
2024-07-24
pygeoapi 0.9.0
Specification(s)
Original Certification
OGC API - Environmental Data Retrieval Standard 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Environmental Data Retrieval Standard: Collections 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Environmental Data Retrieval Standard: JSON 1.0.1
(OGC Reference Implementation)
2022-11-10
OGC API - Features - Part 1: Core 1.0
(OGC Reference Implementation)
2021-01-09
OGC API - Tiles - Part 1: Core 1.0
(OGC Reference Implementation)
2024-02-08
OGC API - Tiles - Part 1: GeoDataTilesets 1.0
(OGC Reference Implementation)
2024-02-08
OGC API - Tiles - Part 1: TilesetsList 1.0
(OGC Reference Implementation)
2024-02-08
________________________________
OGC Privacy Policy<a class="moz-txt-link-rfc2396E" href="http://www.ogc.org/ogc/policies/privacy"><http://www.ogc.org/ogc/policies/privacy></a>
--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end,
</pre></blockquote>this is just about bytes.
<blockquote type="cite"><pre wrap="" class="moz-quote-pre">
</pre></blockquote>
--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature">--
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/member/angelos-tzotsos/">https://www.osgeo.org/member/angelos-tzotsos/</a>
</pre>
</div>
</body>
</html>