<html><body><html><head><meta charset="utf-8">
</head><body><div id="compose-body-wrapper" dir="auto"><div dir="auto">Hi to all</div><div dir="auto"><br></div><div dir="auto">My opinion  is more or less the same as Francesco. </div><div dir="auto"><br></div><div dir="auto">I like what it was done on pywps some years ago,  pywps became an API and other things like integration into flask or django because projects. This was a success.  Saw different developers focus better on different features. <span style> </span><span style>IMHO  pygeoapi-ui,  is a good idea.</span></div><div dir="auto"><br></div><div dir="auto">Since html is mandatory there is no much escape other than have minimal support, </div><div dir="auto"><br></div><div dir="auto">On the back of my mind, the API should focus on more technical issues, for example current code base doesn't implement async  python and this would be important for data streaming and better integration into web-frameworks like startlette, IMHO the API should focus more on code features that would allow higher quality code and integration (pydantic, async, plugins approach etc etc )</div><div dir="auto"><br></div><div dir="auto">Maybe an extra discussion on the next meeting  and a clear roadmap on the topic ??</div><div dir="auto"><br></div><div dir="auto">My 1 cent</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Jorge </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto" id="tmjah_g_1299"><p><font face="Calibri, sans-serif"><span style="font-size: 14.6667px;">ISRIC — World Soil Information</span></font><br></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">PO Box 353 | 6700 AJ Wageningen<o:p></o:p></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="https://www.wageningencampus.nl/nl/campus/over/gebouwen/show/Gaia-gebouwnummer-101.htm" title="https://www.wageningencampus.nl/nl/campus/over/gebouwen/show/Gaia-gebouwnummer-101.htm" target="_blank" style="font-family: Calibri, sans-serif; text-decoration: underline;"><span style="text-decoration-line: none;">Droevendaalsesteeg 3 (Building 101) </span><span style="text-decoration-line: none;">| 6708 PB Wageningen</span></a><o:p></o:p></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">The Netherlands<o:p></o:p></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">Telephone (Secretariat): +31 317 483735<o:p></o:p></p><p class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span lang="PT-BR">E-mail: </span><a href="blocked::mailto:soil.isric@wur.nl" title="blocked::mailto:soil.isric@wur.nl" target="_blank" style="font-family: Calibri, sans-serif; text-decoration: underline;"><span lang="PT-BR">info@isric.org</span></a></p><div><i style="font-family: Calibri, sans-serif; text-decoration: underline;"><br></i></div></div><br></div><div class="replyHeader" dir="auto">Francesco Bartoli wrote:</div><br><br><div><blockquote cite="mid:bd9ecc10-74f8-4da6-ae52-45365a96ba2f@Spark" type="cite" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title></title>
<div name="messageBodySection">
<div dir="auto">Hi folks,<br>
<br>
I want to continue the discussion already started in the gitter channel. Happy to hear more perspectives on the tables. I left just my last comment about the topic:<br>
<br>
<span style>I do believe the main focus for pygeoapi should remain that of an api-first building block for the digital transformation of SDIs. In other words, giving the minimal context to the user in the html form is fair enough for me but deviating from the api-first approach is just an anti-pattern. This wouldn’t exclude to have a pygeoapi-ui project for a web application to cover complex use cases. It’s not a negative aspect but web application and api-first concepts just collide in my opinion.</span></div>
</div>
<div name="messageSignatureSection"><br>
<div class="matchFont">Ciao<br>
Francesco</div>
</div>
</blockquote></div><div><blockquote cite="mid:bd9ecc10-74f8-4da6-ae52-45365a96ba2f@Spark" type="cite" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title></title>
<div name="messageBodySection">
<div dir="auto">Hi folks,<br>
<br>
I want to continue the discussion already started in the gitter channel. Happy to hear more perspectives on the tables. I left just my last comment about the topic:<br>
<br>
<span style>I do believe the main focus for pygeoapi should remain that of an api-first building block for the digital transformation of SDIs. In other words, giving the minimal context to the user in the html form is fair enough for me but deviating from the api-first approach is just an anti-pattern. This wouldn’t exclude to have a pygeoapi-ui project for a web application to cover complex use cases. It’s not a negative aspect but web application and api-first concepts just collide in my opinion.</span></div>
</div>
<div name="messageSignatureSection"><br>
<div class="matchFont">Ciao<br>
Francesco</div>
</div>
</blockquote></div>
</body></html></body></html>