<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">+1, thanks</div>
</div>
<div name="messageSignatureSection"><br />
Ciao<br />
Francesco</div>
<div name="messageReplySection">On 22 Apr 2024, 16:28 +0200, Tom Kralidis via pygeoapi <pygeoapi@lists.osgeo.org>, wrote:<br />
<blockquote type="cite">
<div dir="ltr">
<div>Hi all: FYI given that pygeoapi now passes OGC CITE compliance for OGC API - Processes - Part 1: Core, we have the opportunity to register compliance with OGC.</div>
<div><br /></div>
<div>Note that we are usually provided Compliance / Reference Implementation for no cost given our usual early adoption of the OGC standards, but in the OGC API - Processes case the time has passed in order for this to happen.</div>
<div><br /></div>
<div>The cost for compliance is 150 USD. I propose we use our OSGeo budget for this since pygeoapi is registered as an OSGeo project to OGC, as well as the value in order to provide a badge on our website and communications.</div>
<div><br /></div>
<div>If we have PSC consensus, the plan would be to apply for OGC API - Processes compliance once we release 0.17.0 in June.</div>
<div><br /></div>
<div>I will start with my +1.</div>
<div><br /></div>
<div>Thanks</div>
<div><br /></div>
<div>..Tom<br /></div>
</div>
_______________________________________________<br />
pygeoapi mailing list<br />
pygeoapi@lists.osgeo.org<br />
https://lists.osgeo.org/mailman/listinfo/pygeoapi<br /></blockquote>
</div>
</body>
</html>