[Board] Fwd: OGC Compliance Renewal Notification - 60 Day Expiration Notice

Sun Jan 5 06:19:10 PST 2025

-------- Forwarded Message --------
Subject: 	Re: OGC Compliance Renewal Notification - 60 Day Expiration 
Notice
Date: 	Sun, 5 Jan 2025 16:18:23 +0200
From: 	Angelos Tzotsos <tzotsos at osgeo.org>
To: 	Micah Brachman <mbrachman at ogc.org>
CC: 	Angelos Tzotsos <gcpp.kalxas at gmail.com>, Even Rouault 
<even.rouault at spatialys.com>, Compliance <compliance at ogc.org>, 
info at osgeo.org <info at osgeo.org>, OSGeo Board <board at lists.osgeo.org>, 
Tom Kralidis <tomkralidis at gmail.com>

Dear Micah,

We have gathered all compliance tests and we are ready to submit.

Here is our status list, I would like to ask some questions:

Under the OSGeo organization we have several products listed in the OGC
compliance page.
1. For MapServer we have versions 5.0, 6.0, 6.2, 6.4, 7.0, 8.2
Only 6.2 has passed certification in the past so I assume we keep that
listed.
I added the latest 8.2 release that includes support for OGC API Features
(no cite tests yet).

2. For pygeoapi we have versions 0.7, 0.9, 0.17 and 0.19
We have provided new compliance tests against the latest 0.19 version and
we would like to ask to move reference implementation status (OGC API -
Features, OGC API - Processes and OGC API - Tiles) to that version . Is
that possible?
We did not manage to run new tests for OGC API - EDR so we would like to
keep RI to the previous pygeoapi 0.9 version for now.

3. For pycsw we have versions 1.1, 2.0, 2.2, 2.4 and 2.6
We provided certification tests against the latest version and we would
like to keep that version as CSW 2.0.2 and 3.0.0 reference implementation.
OGC API Records is implemented in pycsw 3.0.0 (not yet released as final).
We are waiting for the specification to be finalized and looking forward to
testing against a Records cite test.

4. GDAL/OGR we have versions 1.11, 2.1, 2.4, 3.0 and now 3.10
We provided certification tests against the latest version (3.10) and we
would like to ask to move all reference implementation status to that
version. Is that possible?

5. For GeoServer we have version 2.24
We do not have new compliance tests available so we would like to keep
version 2.24 listed.

Best regards,
Angelos

On Wed, Nov 13, 2024 at 7:09 PM Micah Brachman <mbrachman at ogc.org> wrote:

> That sounds great, Angelos – please let me know if you have any questions
> or need assistance.
>
>
>
> *From: *Angelos Tzotsos<gcpp.kalxas at gmail.com>
> *Date: *Wednesday, November 13, 2024 at 6:39 AM
> *To: *Micah Brachman<mbrachman at ogc.org>, Even Rouault <
> even.rouault at spatialys.com>, Compliance <compliance at ogc.org>,
> info at osgeo.org <info at osgeo.org>
> *Cc: *Angelos Tzotsos<tzotsos at osgeo.org>, OSGeo Board <
> board at lists.osgeo.org>
> *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:
>> Thanks for sharing these, Even.
>>
>> Angelos-
>>
>> I can see that you have submitted the last few compliance results.  Are
> you planning to submit these as well?
>> Best,
>>
>> Micah
>>
>>
>> Micah Brachman, PhD
>> Community Manager | Open Geospatial Consortium (OGC)
>> +1 (508) 655-5858<tel:+15086555858> ex 706
>> mbrachman<mailto:mbrachman at ogc.org>@ogc.org<mailto:mbrachman at ogc.org
> <mbrachman at ogc.org%3e at ogc.org%3cmailto:mbrachman at ogc.org>> | ogc.org< http://ogc.org/> | @opengeospatial
>>
>>
>> From: Even Rouault<even.rouault at spatialys.com>
>> Date: Monday, November 11, 2024 at 3:56 PM
>> To: Compliance<compliance at ogc.org>,info at osgeo.org <info at osgeo.org>
>> Cc: Angelos Tzotsos<tzotsos at osgeo.org>, OSGeo Board <
> board at lists.osgeo.org>, Angelos Tzotsos <gcpp.kalxas at gmail.com>
>> Subject: Re: OGC Compliance Renewal Notification - 60 Day Expiration
> Notice
>> 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,compliance at ogc.org<mailto:compliance at ogc.org
> <compliance at ogc.org>> a écrit :
>> Open Source Geospatial Foundation
>>
>> This is an automated email to inform you that your OGC-certified
> 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.
>> Since you have reference implementations in your listings please be
> aware of the following:
>>     *   You need to retest if you want to continue being listed as a
> reference implementation.
>>     *   If you want to provide a new version as a reference
> implementation you need to test that new version. The older version will no
> longer hold the status of reference implementations.
>>     *   If you want to continue displaying the certification for the
> older version of your product, then you will be required to pay for the
> certification.
>> Additional expiration warnings may be sent to you 1 month and 2 weeks
> prior to expiration, please begin the renewal process as soon as possible.
>> We invite you to easily renew online in our implementation portal:
> https://www.ogc.org/resource/products/registration
>> As a reminder, the account used to manage your certification listings
> is: osgeo (info at osgeo.org<mailto:info at osgeo.org>)
>> If you have any questions please send an email tocompliance at ogc.org<
> mailto:compliance at ogc.org <compliance at ogc.org>>. The OGC compliance team
> will be more than glad to help you.
>> ________________________________
>> 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
> Information 1.0
>> (OGC Reference Implementation)
>> 2024-01-09
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Acquisition
> Parameters 1.0
>> (OGC Reference Implementation)
>> 2024-01-09
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Data
> Identification 1.0
>> (OGC Reference Implementation)
>> 2024-01-09
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> Observation 1.0
>> (OGC Reference Implementation)
>> 2024-01-09
>> OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard: Earth
> Observation Collection 1.0
>> (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
> Information 1.0
>> (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
> Information 1.0
>> (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
> Service for the Web] 2.0.2
>> (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
> (OpenSearch) 3.0
>> (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
> Service for the Web] 2.0.2
>> (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<http://www.ogc.org/ogc/policies/privacy>
>>
>> --
>>
>> http://www.spatialys.com
>>
>> My software is free, but my time generally not.
>>
>> Butcher of all kinds of standards, open or closed formats. At the end,
> this is just about bytes.
>
>
> --
> Angelos Tzotsos, PhD
> President, Board of Directors
> Open Source Geospatial Foundation
> https://www.osgeo.org/member/angelos-tzotsos/
>

-- 
Angelos Tzotsos, PhD
President, Board of Directors
Open Source Geospatial Foundation
https://www.osgeo.org/member/angelos-tzotsos/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/board/attachments/20250105/65e61e3f/attachment-0001.htm>