<div dir="ltr"><div>Seth: thanks for this RFC. IETF has api-catalog (draft, [1]) which I think would be a good candidate for this RFC. This is also an item for review in the OGC API - Records SWG [2].</div><div><br></div><div>Overall it looks pretty close to the RFC proposal. We can consider using api-catalog as a baseline and we can extend the JSON accordingly as needed for anything specific to our needs.</div><div><br></div><div>Cheers</div><div><br></div><div>..Tom</div><div><br></div><div>[1] <a href="https://datatracker.ietf.org/doc/draft-ietf-httpapi-api-catalog">https://datatracker.ietf.org/doc/draft-ietf-httpapi-api-catalog</a></div><div dir="ltr">[2] <a href="https://github.com/opengeospatial/ogcapi-records/issues/355">https://github.com/opengeospatial/ogcapi-records/issues/355</a></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Jan 18, 2025 at 5:39 PM Seth G via MapServer-dev <<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Looking again at the landing page JSON at <a href="https://demo.mapserver.org/cgi-bin/mapserv/localdemo/ogcapi?f=json" rel="noreferrer" target="_blank">https://demo.mapserver.org/cgi-bin/mapserv/localdemo/ogcapi?f=json</a> it is in the same format, so as you suggested could simply be expanded with links to WxS services, or even CGI generated responses. This would also more easily allow template reuse. <br>
<br>
Seth<br>
<br>
--<br>
web:<a href="https://geographika.net" rel="noreferrer" target="_blank">https://geographika.net</a> & <a href="https://mapserverstudio.net" rel="noreferrer" target="_blank">https://mapserverstudio.net</a><br>
mastodon: @geographika@mastodon.social<br>
<br>
On Sat, Jan 18, 2025, at 11:33 PM, Seth G via MapServer-dev wrote:<br>
> Hi Even,<br>
><br>
> Thanks for your valuable feedback. <br>
><br>
> The homepage would be a "superset" of all available Mapfiles in a <br>
> MapServer deployment, as listed in the CONFIG file. Each individual <br>
> Mapfile would still have its own OGC API landing page, so the homepage <br>
> is best described as a directory of all landing pages. <br>
><br>
> As most MapServer deployments will likely be serving out a combination <br>
> of WxS and new OGC API services for some time to come, it will allow <br>
> both types to be listed together (I'm unaware of a OGC API spec that <br>
> would cover this). <br>
><br>
> In regard to the JSON used for links, I was modelling it as closely as <br>
> possible to OGC API conventions. Looking at the pygeoapi demo home <br>
> page, it provides a set of links in a common format, so I'll likely <br>
> switch to this format/approach:<br>
><br>
> <a href="https://demo.pygeoapi.io/stable?f=json" rel="noreferrer" target="_blank">https://demo.pygeoapi.io/stable?f=json</a><br>
><br>
> A few of the "rel" values are defined as below, and can be reused:<br>
><br>
> alternate Provides an alternate representation (e.g., HTML version of a <br>
> resource).<br>
> service-desc Links to the machine-readable API description (e.g., <br>
> OpenAPI JSON).<br>
> service-doc Links to the human-readable API documentation (e.g., <br>
> OpenAPI HTML).<br>
> conformance Lists the standards and conformance classes supported by <br>
> the API.<br>
><br>
> I'll update the RFC with the above,<br>
><br>
> Seth<br>
><br>
> --<br>
> web:<a href="https://geographika.net" rel="noreferrer" target="_blank">https://geographika.net</a> & <a href="https://mapserverstudio.net" rel="noreferrer" target="_blank">https://mapserverstudio.net</a><br>
> mastodon: @geographika@mastodon.social<br>
><br>
> On Sat, Jan 18, 2025, at 12:39 PM, Even Rouault wrote:<br>
>> Seth,<br>
>><br>
>> Thanks for putting this together. I'm wondering how much your proposal <br>
>> relates/intersects with the concept of the landing page of OGC API <br>
>> services ? You mention some connection with it, but it is not <br>
>> immediately clear to me the exact nature of the connection. Perhaps it <br>
>> is just a matter of clarifying. I have put zero thoughts in it, but it <br>
>> would feel weird to invent a MapServer specific thing, so I'm naively <br>
>> wondering if we can't we just adopt the landing page formalism (for the <br>
>> JSON part), and potentially extend it by exposing old WxS services as <br>
>> well in the links as you suggest? I'm also wondering if there's some <br>
>> best practice used by other projects on how to expose for things like<br>
>><br>
>> {<br>
>> "href": <br>
>> "<a href="https://demo.mapserver.org/cgi-bin/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities" rel="noreferrer" target="_blank">https://demo.mapserver.org/cgi-bin/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetCapabilities</a>",<br>
>> "title": "GetCapabilities",<br>
>> "type": "WMS"<br>
>> },<br>
>><br>
>> so they can be interoperably consumed.<br>
>><br>
>> Even<br>
>><br>
>> Le 18/01/2025 à 09:11, Seth G via MapServer-dev a écrit :<br>
>>> Hi devs,<br>
>>><br>
>>> I've drafted an RFC with an approach of creating a MapServer homepage based on the MAPs referenced in a mapserver.conf file. This will allow MapServer installations to easily advertise available services, dynamically.<br>
>>><br>
>>> Text available in pull request at <a href="https://github.com/MapServer/MapServer-documentation/pull/996" rel="noreferrer" target="_blank">https://github.com/MapServer/MapServer-documentation/pull/996</a><br>
>>><br>
>>> Comments and thoughts appreciated,<br>
>>> Thanks,<br>
>>><br>
>>> Seth<br>
>>><br>
>>> --<br>
>>> web:<a href="https://geographika.net" rel="noreferrer" target="_blank">https://geographika.net</a> & <a href="https://mapserverstudio.net" rel="noreferrer" target="_blank">https://mapserverstudio.net</a><br>
>>> mastodon: @geographika@mastodon.social<br>
>>> _______________________________________________<br>
>>> MapServer-dev mailing list<br>
>>> <a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>><br>
>> -- <br>
>> <a href="http://www.spatialys.com" rel="noreferrer" target="_blank">http://www.spatialys.com</a><br>
>> My software is free, but my time generally not.<br>
>> Butcher of all kinds of standards, open or closed formats. At the end, <br>
>> this is just about bytes.<br>
> _______________________________________________<br>
> MapServer-dev mailing list<br>
> <a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
_______________________________________________<br>
MapServer-dev mailing list<br>
<a href="mailto:MapServer-dev@lists.osgeo.org" target="_blank">MapServer-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapserver-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</blockquote></div></div>