[postgis-devel] Fwd: OGC Compliance Renewal Notification - 60 Day Expiration Notice

Simon (SPDBA) Greener simon at spatialdbadvisor.com
Mon Nov 11 13:21:58 PST 2019


The SFS 1.1 and 1.2 (plus SQL/MM) standards are foundational, but restrictive and static. There appears to be no evolution to create additional functionality for users in the vector space. So attaining compliance was important years ago but of little value in the marketplace today.

The certificates received years ago are functionally valid today. Unless the OGC tries to force you to removed references to that past compliance, what was done is sufficient.

But it is backwards looking.

PostGIS's power is its very extensive, dynamic, and evolutionary API that can't be recognised in the current specification space. 

PostGIS has moved on, unlike so many other DB implementations, from those standards. That is its acknowledged power. Demonstrating its value, looking forward, not backwards, is PostGIS's future.

Just my 2c worth.

Regards
Simon

⁣39 Cliff View Drive, Allens Rivulet, Tas 7150
(H) 0362396397
(M) 0418396391
www.spatialdbadvisor.com / www.spdba.com.au

Sent from BlueMail ​

On 12 Nov. 2019, 07:17, at 07:17, Regina Obe <lr at pcorp.us> wrote:
>I love that idea :)
>
> 
>
>We are the standard by all which all spatial databases are measured we
>should have our own compatibility :)
>
> 
>
> 
>
>From: Darafei "Kom?pa" Praliaskouski [mailto:me at komzpa.net] 
>Sent: Monday, November 11, 2019 12:56 PM
>To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
>Cc: Regina Obe <lr at pcorp.us>
>Subject: Re: [postgis-devel] Fwd: OGC Compliance Renewal Notification -
>60 Day Expiration Notice
>
> 
>
>Can we start collecting money for certifying databases for
>PostGIS-compatibility instead?
>(like, "you indeed pass our regression suite").
>
> 
>
>On Mon, Nov 11, 2019 at 8:52 PM Paul Ramsey <pramsey at cleverelephant.ca
><mailto:pramsey at cleverelephant.ca> > wrote:
>
>We haven’t been a certified implementation since Refractions paid for
>the process back in 1.2 era. The OGC certification process also
>requires a separate certification for EVERY RELEASED VERSION, so you
>can see how it rapidly became a Low Priority.
>It sure would be nice if that “OGC MOU with OSGeo” got us something
>like, say, no-pay certification of OSGeo projects, under the OSGeo
>organization header (that’s the other quirk, the listing for the
>certification ends up being under the sponsoring organization, so it
>was “Refractions Research PostGIS 1.2” that was certified.
>P.
>
>> On Nov 11, 2019, at 7:42 AM, Regina Obe <lr at pcorp.us
><mailto:lr at pcorp.us> > wrote:
>> 
>> strk,
>> 
>> The note I saw from Angelos talked about reference implementations. 
>PostGIS has never been a reference implementation to my knowledge.
>> 
>> As far as caring -- I think we wanted to follow the spec and may have
>been certified in OGC in 1.2 days, but we have an issue of two specs we
>got to worry about 
>> 
>> The ISO/SQL MM spec (which is more respected as far as databases go
>but costs money to even read the spec) , and the OGC spec - I'd be
>surprised if any database is completely certified in these.
>> 
>> We probably care less now than we did back then -- because back then
>we were small and largely ignored, now we are the most widely used
>spatial database so many spatial databases look to us for direction.
>> I'd be more concerned about growing our competitors though - as you
>don't want to be the only fish in the small spatial pond.
>> 
>> So perhaps we should care just a little if for no other reason than
>to have more competition.
>> 
>> Thanks,
>> Regina 
>> 
>> 
>> -----Original Message-----
>> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org
><mailto:postgis-devel-bounces at lists.osgeo.org> ] On Behalf Of Sandro
>Santilli
>> Sent: Monday, November 11, 2019 5:30 AM
>> To: postgis-devel at lists.osgeo.org
><mailto:postgis-devel at lists.osgeo.org> ; Paul Ramsey
><pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca> >
>> Subject: [postgis-devel] Fwd: OGC Compliance Renewal Notification -
>60 Day Expiration Notice
>> 
>> Hi old generation devs,
>> 
>> Angelos forwarded a reminder mail from OGC about expiring
>compatibility certifications.
>> 
>> On Sun, Nov 10, 2019 at 08:46:35PM +0200, Angelos Tzotsos wrote:
>>> This is a reminder from OGC for all our projects that want to pass 
>>> certification for the next year.
>>> Please contact me so I can add your tests to the OSGeo
>implementation list.
>> 
>> The list of certified projects did not include PostGIS at all, when
>did we stop caring ? Should we start again ?
>> Paul (or Angelos) do you know what does that imply ?
>> 
>> --strk;
>> 
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
>> https://lists.osgeo.org/mailman/listinfo/postgis-devel
>> 
>
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
>https://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
>
>
> 
>
>-- 
>
>Darafei Praliaskouski
>
>Support me: http://patreon.com/komzpa
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at lists.osgeo.org
>https://lists.osgeo.org/mailman/listinfo/postgis-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20191112/2ec1a1da/attachment-0001.html>


More information about the postgis-devel mailing list