Hi All, I apologize for the slow response and thank you all for your detailed and valuable contributions to this thread.
I am still waiting for funding confirmation, but I want to emphasize the importance of approaching this as a community-driven, collaborative effort. Once funding is secured, our focus will be on ensuring that the OGC Features API meets production readiness as per customer requirements. Consequently, any refactoring, design, or architectural decisions must be made collaboratively to ensure that other API implementations can seamlessly follow suit where applicable. To this end, I propose we develop a plan to initially refactor the gs-ogcapi-core and gs-ogcapi-features modules as extensions. Based on the concerns and ideas discussed in this thread, we should work towards the following objectives: * Defining and Implementing Service Metadata Independent of WFS Configuration: Currently, the service metadata and configuration for the OGC Features module use the WFS service configuration. We need to decouple it from the WFS configuration, and the exact approach is open for discussion. * Designing and Implementing a Mechanism to Enable/Disable Non-Finalized Parts of the Specification: The OGC Features API is divided into separate specifications, some of which are not finalized. It is crucial that these unfinished aspects of the API can be enabled or disabled via configuration. This configuration will likely be part of the ogcapi-specific service configuration mentioned above. * Setting Up CI/CD Pipelines: We need to establish and integrate continuous integration and deployment pipelines for automated testing. These pipelines should run CITE conformance tests and additional integration tests (e.g., against PostGIS). * Providing a Technical Preview Distribution of GeoServer: A technical preview distribution of GeoServer with the OGC APIs enabled will allow us to reach a wider audience for testing and early feedback. * Organizing a Code Sprint: To complement community discussions on design and implementation, it would be ideal to organize an online code sprint. Although we may not have sufficient funding for an on-site event, an online code sprint would still enable all interested parties to contribute focused time and effort. Thank you again for your initial thoughts. I look forward to getting started and hearing from all of you. Best regards, Gabe *camptocamp* INNOVATIVE SOLUTIONS BY OPEN SOURCE EXPERTS *Gabriel Roldán* Geospatial Developer On Sat, Jul 6, 2024 at 8:07 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Alexandre, > indeed they did. At the same time, the existing OWS APIs have been around > for such a long time, > what is the meaning of "deprecating", besides a formal statement? That > will have some effect on > large, formal organisations, but the rest of the world will carry on > unscathed. > > The worst they can do is to remove the schemas from > https://schemas.opengis.net/... that may > have some effect, but the net result will be to mostly piss off people and > give them a reason > to choose an "open specification" rather than an official standard, and > just prompt developers > to make sure their software is working offline (AFAIk Geoserver does not > need the schemas > over there, effort was put in to work mostly offline, but I may be wrong > and/or some > cases might not actually work). > > Regards, > > Andrea Aime > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > > > On Sat, Jul 6, 2024 at 1:55 PM Alexandre Gacon <alexandre.ga...@gmail.com> > wrote: > >> Regarding OGC web services vs OGC API, during the OGC presentation, the >> speaker mentioned that when they think that a given API is good enough, >> they will deprecate the matching OGC Web Service. >> >> >> Alexandre >> >> Le sam. 6 juil. 2024 à 09:29, Andrea Aime < >> andrea.a...@geosolutionsgroup.com> a écrit : >> >>> On Sat, Jul 6, 2024 at 9:27 AM Andrea Aime < >>> andrea.a...@geosolutionsgroup.com> wrote: >>> >>>> And then basically rinse and repeat for the other services (for extra >>>> fun, consider that today you cannot have WMS without WFS around, >>>> due to GetFeatureInfo depending on GML outputs). >>>> Mind, the above refactors are a good idea in general, not just for OGC >>>> API, and while most of it will just be moving classes >>>> around, there is also a part that involves >>>> >>> >>> Cliffhanger! Sorry, on the train and got distracted. >>> There is also a part that involves actual code development and likely >>> some nasty surprises. >>> >>> Cheers >>> Andrea >>> >>>> _______________________________________________ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
