[Qgis-psc] QGIS server certified for OGC API for features

Fri Oct 23 09:10:03 PDT 2020

FYI, I did put some pressure on the OGC and raised the issue in the OSGeo
Discuss mailing list to see if we can find a global solution there

Bye'
Régis

Le ven. 23 oct. 2020 à 16:49, Andreas Neumann <andreas at qgis.org> a écrit :

> Hi all,
>
> I also think that we should ask them to give either a substantial discount
> (because we are an OS project) or we cancel our certification.
>
> This year we can pay the invoice. Please tell them to update the address
> to:
>
> QGIS.ORG
> Boeschacherstrase 10A
> 8624 Gruet (Gossau ZH)
> Switzerland
>
> Note that I replaced the german Umlauts. Most likely, if it is is a US
> based entity, they are not capable of handling foreign characters ...
>
> What is the rest of the PSC thinking about OGC certification?
>
> Greetings,
> Andreas
>
> On Fri, 23 Oct 2020 at 15:14, Alessandro Pasotti <apasotti at gmail.com>
> wrote:
>
>> On Fri, Oct 23, 2020 at 2:25 PM Régis Haubourg <regis.haubourg at gmail.com>
>> wrote:
>> >
>> > Hi all,
>> > any reaction here?
>> > At least Andreas, can I go further with the billing or should I fight a
>> bit more with the OGC ?
>>
>> Hi Régis,
>>
>> It looks like wasted time fighting bureaucrats.
>>
>> I say we pay now and never again.
>>
>>
>> >
>> > regards
>> > Régis
>> >
>> > Le jeu. 22 oct. 2020 à 15:09, Régis Haubourg <regis.haubourg at gmail.com>
>> a écrit :
>> >>
>> >> Okay,
>> >> so the bad news is that OGC seems to have stricter rules than before.
>> See the response below.
>> >>
>> >> We are now submitted to fees, which are 300 euros per certification
>> submission.
>> >> Currently we have 2 services only, for the server, WMS 1.3 and OGCAPI,
>> so this is 600 euros per year.
>> >>
>> >> I suppose we will have to pay for this one, since the job is done.
>> I'll ask them to emit a correct invoice with QGIS.org information and
>> adress.
>> >>
>> >> This opens a question for our certification strategy:
>> >>
>> >> Up to now it only involved some volunteer time. Now it would also
>> involve finances.
>> >> In my thoughts, the ideal situation was to certify all the supported
>> services, either on server and client side.
>> >> If we go this way, this will grow very fast to some thousand euros
>> each year and a lot of manual work. This seems overkill to me when thinking
>> of the benefits of thess certifications. I never answered any bid requiring
>> a certified engine yet - but you might have hit this issue before.
>> >>
>> >> I'm wondering if we shouldn't just ask for certification once per
>> service, just to prove QGIS is officially compliant once, and then let our
>> nightly testing platforms "prove" we are compliant on the long run.
>> >>
>> >> Instead of a recurrent charge,  this will be a one time charge only,
>> when needed, and when we want to make some buzz in this area.
>> >>
>> >> @Andreas, is this ok for the 300 euros bill, even if this was not
>> planned?
>> >>
>> >> @all any thoughts about our certification strategy?
>> >>
>> >> Best regards
>> >>
>> >> Régis
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>> On 22/10/2020 11:25, Gobe Hobona wrote:
>> >>>
>> >>> Hi Régis,
>> >>>
>> >>> We appreciate the work done by the QGIS and OSGeo community in
>> supporting OGC standards. Please note however that we are guided by our
>> policies, agreed on by the OGC Membership.
>> >>>
>> >>> Please see Sections 5.5 and 6.3 of the Compliance Testing Policy [
>> https://portal.opengeospatial.org/files/?artifact_id=55234].
>> >>>
>> >>> The fee is only waived for:
>> >>>
>> >>> * The first three implementations to pass 100% of the compliance
>> procedure, while the test is in beta. We refer to these as Early
>> Implementers.
>> >>> * The first two Reference Implementations that pass the test related
>> to a conformance class within a version of an Implementation Standard.
>> >>>
>> >>> In this case, the executable test suite of OGC API - Features - Part
>> 1: Core is already in production (i.e. it is no longer in beta).  Please
>> also note that there are already two current Reference Implementations of
>> the standard.
>> >>>
>> >>>
>> https://www.ogc.org/resource/products/compliant?display_opt=1&specid=1022
>> >>>
>> >>> QGIS Server is therefore not eligible for the fee waiver for
>> compliance certification for OGC API - Features - Part 1: Core.
>> >>>
>> >>> Regards,
>> >>>
>> >>> Gobe
>> >>
>> >>
>> >> Le jeu. 22 oct. 2020 à 10:23, Régis Haubourg <regis.haubourg at gmail.com>
>> a écrit :
>> >>>
>> >>> Ouch, in the meantime, I saw they are trying to charge us for this.
>> >>> I'm negotiating a free of charge policy, like they did with the
>> previous OGC team.
>> >>> I'll keep you posted.
>> >>>
>> >>> Régis
>> >>>
>> >>> Le jeu. 22 oct. 2020 à 10:14, Régis Haubourg <
>> regis.haubourg at gmail.com> a écrit :
>> >>>>
>> >>>> Hi all,
>> >>>> Thanks to the great work of Paul and Alessandro, I finally managed
>> to get QGIS server 3.10 certified for OGC API for Features (aka WFS3).
>> >>>>
>> >>>> The badge is at [0] and I updated the wiki accordingly [1]
>> >>>>
>> >>>> Next steps for me are :
>> >>>>
>> >>>> - push a blog post to QGIS.org website
>> >>>> - push a news in the QGIS feed (I'm unsure about this, any opinion
>> welcome)
>> >>>> - update the documentation
>> >>>>
>> >>>> I am really looking forward to the transactional WFS3 specification
>> [2], this will be a big win over current WFS-T for our web clients \o/
>> >>>>
>> >>>> Best regards
>> >>>> Régis
>> >>>>
>> >>>> [0] https://www.ogc.org/resource/products/details/?pid=1611
>> >>>> [1] https://github.com/qgis/QGIS/wiki/OGC-compliance-for-QGIS
>> >>>> [2] http://docs.opengeospatial.org/DRAFTS/20-002.html
>> >>>>
>> >>>>
>> >>>>
>> >>>> On 21/10/2020 19:56, Catherine Walline wrote:
>> >>>>
>> >>>> Hi Régis and Andreas,
>> >>>>
>> >>>> Thank you for your patience regarding the recent submission for OGC
>> compliance for QGIS Server 3.10 with OGC API Features 1.0. It has been
>> approved for the period from 21 October 2020 through 3 April 2021, to
>> coincide with the existing compliance period. The corresponding prorated
>> invoice is attached.
>> >>>>
>> >>>> We invite you to visit the public website to confirm that the
>> listings are displayed as intended:
>> >>>>
>> >>>> https://www.ogc.org/resource/products/details/?pid=1611
>> >>>>
>> >>>> We greatly appreciate your participation in OGC compliance. Please
>> let me know if there are any questions or concerns.
>> >>>>
>> >>>> Best wishes,
>> >>>>
>> >>>> Catherine
>> >>>>
>> >>>> --
>> >>>> Catherine Walline
>> >>>> Senior Accountant | Open Geospatial Consortium (OGC)
>> >>>> Office: 1-508-655-5858, ext 707
>> >>>> cwalline at ogc.org | ogc.org | @opengeospatial
>> >>>>
>> >>>> Sign up for OGC News
>> >
>> > _______________________________________________
>> > Qgis-psc mailing list
>> > Qgis-psc at lists.osgeo.org
>> > https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>
>>
>>
>> --
>> Alessandro Pasotti
>> QCooperative:  www.qcooperative.net
>> ItOpen:   www.itopen.it
>> _______________________________________________
>> Qgis-psc mailing list
>> Qgis-psc at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
>
>
> --
>
> --
> Andreas Neumann
> QGIS.ORG board member (treasurer)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20201023/7175008b/attachment-0001.html>