<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Tom, #361 touches on a different topic then the one from my email.</div><div><br class=""></div><div>I am curious if we had any prior documented discussion about extending the api document <a href="https://demo.pygeoapi.io/master/openapi" class="">https://demo.pygeoapi.io/master/openapi</a> with the specification of properties per featuretype.</div><div><br class=""></div><div>eg:</div><div><br class=""></div><div>As a sidenote, did we notice <a href="https://demo.pygeoapi.io/master/openapi" class="">https://demo.pygeoapi.io/master/openapi</a> is currently broken due to mixed content:</div><div><br class=""></div><div>index.js:1 Mixed Content: The page at '<a href="https://demo.pygeoapi.io/master/openapi#/unesco_pois_italy/get_collections_unesco_pois_italy_items' was loaded over HTTPS, but requested an insecure resource 'http://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/ogcapi-features-1.yaml" class="">https://demo.pygeoapi.io/master/openapi#/unesco_pois_italy/get_collections_unesco_pois_italy_items' was loaded over HTTPS, but requested an insecure resource 'http://schemas.opengis.net/ogcapi/features/part1/1.0/openapi/ogcapi-features-1.yaml</a>'. This request has been blocked; the content must be served over HTTPS.</div><div><br class=""></div><div>OGC seems not to offer a https version of the schemas… maybe reference a local copy instead?</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">---</span></font><br class=""><br class="">Hi Paul: see [1] (as you have since found :)<br class=""><br class="">..Tom<br class=""><br class="">[1] <a href="https://github.com/geopython/pygeoapi/issues/361" class="">https://github.com/geopython/pygeoapi/issues/361</a><br class=""><br class="">On Fri, 6 Mar 2020, Paul van Genuchten wrote:<br class=""><br class=""><blockquote type="cite" class="">Date: Fri, 6 Mar 2020 10:37:14 +0100<br class="">From: Paul van Genuchten <<a href="mailto:paul.vangenuchten@geocat.net" class="">paul.vangenuchten@geocat.net</a>><br class="">To: <a href="mailto:pygeoapi@lists.osgeo.org" class="">pygeoapi@lists.osgeo.org</a><br class="">Subject: [pygeoapi] describefeaturetype in openapidocument<br class=""><br class="">Hi list, gitter is having issues this morning, so let me try by mail (although this is probably more a gitter question)<br class=""><br class="">I remember we had some discussion about advertising data models as part of the open api document, similar to what describefeaturetype does on WFS. Currently openapidoc indicates /items will return a set of features and advertises only the common part of features.<br class=""><br class="">Is this a pending implementation task (is there i github issue to track this activity), or are we waiting for OGC to decide something in this area?<br class=""><br class="">Regards, Paul<br class=""><br class="">_______________________________________________<br class="">pygeoapi mailing list<br class=""><a href="mailto:pygeoapi@lists.osgeo.org" class="">pygeoapi@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/pygeoapi<br class=""></blockquote><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">pygeoapi mailing list<br class=""><a href="mailto:pygeoapi@lists.osgeo.org" class="">pygeoapi@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/pygeoapi<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">End of pygeoapi Digest, Vol 10, Issue 2<br class="">***************************************<br class=""></div></div></blockquote></div><br class=""></body></html>