Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Angelos Tzotsos
Hi all,

Just an update on the status of our OGC certification renewals:
We currently have 3 projects under certification:
MapServer, GDAL and pycsw.

pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
be certified once again.
Even has reported an issue with CITE tests and GDAL, so our application
is waiting for feedback from CITE developers.
Unfortunately MapServer has not yet responded (adding mapserver-dev list
in CC). There is still time for other projects to submit their CITE test
results and get certified through the OSGeo account.

Best,
Angelos

On 10/31/2017 04:03 PM, Barbara Sherman wrote:

>    Open Source Geospatial Foundation
>
> *! Your Compliance Records Expire Today !*
>
> This is an automated email to inform you that your OGC-certified compliance
> license(s) for the following products are due to be renewed by *October 31st,
> 2017*. After that date your products will no longer be listed as certified OGC
> compliant.
>
> If you have already received an earlier notice and have started the renewal
> process please ignore this message.
>
> We invite you to easily renew online in our implementation portal:
> http://www.opengeospatial.org/resource/products/registration
>
> As a reminder, the account used to manage your certification listings is: *osgeo
> ([hidden email] <mailto:[hidden email]>)*
>
> If you have any questions please send an email to [hidden email]
> <mailto:[hidden email]>. The OGC compliance team will be more
> than glad to help you.
>
> --------------------------------------------------------------------------------
>
>
>      Current OGC-Compliant Listings
>
>
>        GDAL/OGR 1.11
>
> Specification(s) Original Certification
> OGC KML 2.2.0 2014-08-15
> OGC KML (Level 2) 2.2.0 2014-08-15
> OGC KML (Level 3) 2.2.0 2014-08-15
>
>
>        GDAL/OGR 2.1
>
> Specification(s) Original Certification
> OGC KML 2.2.0
> (OGC Reference Implementation) 2016-11-30
> OGC KML (Level 2) 2.2.0
> (OGC Reference Implementation) 2016-11-30
> OGC KML (Level 3) 2.2.0
> (OGC Reference Implementation) 2016-11-30
>
>
>        MapServer 6.2
>
> Specification(s) Original Certification
> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
> (OGC Reference Implementation) 2016-01-12
>
>
>        pycsw 1.10
>
> Specification(s) Original Certification
> OpenGIS Catalogue Service Implementation Specification 2.0.2 2016-01-26
> OpenGIS Catalogue Service Implementation Specification [Catalogue Service for
> the Web] 2.0.2 2016-01-26
>
>
>        pycsw 2.0
>
> Specification(s) Original Certification
> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
> (OGC Reference Implementation) 2016-11-30
> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding (OpenSearch) 3.0
> (OGC Reference Implementation) 2016-11-30
> OpenGIS Catalogue Service Implementation Specification 2.0.2
> (OGC Reference Implementation) 2016-11-30
> OpenGIS Catalogue Service Implementation Specification [Catalogue Service for
> the Web] 2.0.2
> (OGC Reference Implementation) 2016-11-30
>
>
>

--
Angelos Tzotsos, PhD
Charter Member, Board of Directors
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos


--
Angelos Tzotsos, PhD
Charter Member
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

jmckenna
Administrator
I believe Stephan did this for WMS before, but I'm not sure where these
renewal notices are sent exactly for MapServer.  Stephan can you tackle
this again?  Or do you need assistance?  -jeff



On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:

> Hi all,
>
> Just an update on the status of our OGC certification renewals:
> We currently have 3 projects under certification:
> MapServer, GDAL and pycsw.
>
> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
> be certified once again.
> Even has reported an issue with CITE tests and GDAL, so our application
> is waiting for feedback from CITE developers.
> Unfortunately MapServer has not yet responded (adding mapserver-dev list
> in CC). There is still time for other projects to submit their CITE test
> results and get certified through the OSGeo account.
>
> Best,
> Angelos
>
> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>    Open Source Geospatial Foundation
>>
>> *! Your Compliance Records Expire Today !*
>>
>> This is an automated email to inform you that your OGC-certified
>> compliance
>> license(s) for the following products are due to be renewed by
>> *October 31st,
>> 2017*. After that date your products will no longer be listed as
>> certified OGC
>> compliant.
>>
>> If you have already received an earlier notice and have started the
>> renewal
>> process please ignore this message.
>>
>> We invite you to easily renew online in our implementation portal:
>> http://www.opengeospatial.org/resource/products/registration
>>
>> As a reminder, the account used to manage your certification listings
>> is: *osgeo
>> ([hidden email] <mailto:[hidden email]>)*
>>
>> If you have any questions please send an email to
>> [hidden email]
>> <mailto:[hidden email]>. The OGC compliance team will
>> be more
>> than glad to help you.
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>>      Current OGC-Compliant Listings
>>
>>
>>        GDAL/OGR 1.11
>>
>> Specification(s)    Original Certification
>> OGC KML 2.2.0     2014-08-15
>> OGC KML (Level 2) 2.2.0     2014-08-15
>> OGC KML (Level 3) 2.2.0     2014-08-15
>>
>>
>>        GDAL/OGR 2.1
>>
>> Specification(s)    Original Certification
>> OGC KML 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC KML (Level 2) 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC KML (Level 3) 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>>
>>
>>        MapServer 6.2
>>
>> Specification(s)    Original Certification
>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>> (OGC Reference Implementation)    2016-01-12
>>
>>
>>        pycsw 1.10
>>
>> Specification(s)    Original Certification
>> OpenGIS Catalogue Service Implementation Specification 2.0.2    
>> 2016-01-26
>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>> Service for
>> the Web] 2.0.2     2016-01-26
>>
>>
>>        pycsw 2.0
>>
>> Specification(s)    Original Certification
>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>> (OpenSearch) 3.0
>> (OGC Reference Implementation)    2016-11-30
>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>> (OGC Reference Implementation)    2016-11-30
>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>> Service for
>> the Web] 2.0.2
>> (OGC Reference Implementation)    2016-11-30
>>
>>\
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Stephan Meißl
I'm pretty sure WMS was done by Arnulf. I did WCS way back but
apparently that already fell off the list.

cu
Stephan


On 10/31/2017 08:45 PM, Jeff McKenna wrote:

> I believe Stephan did this for WMS before, but I'm not sure where these
> renewal notices are sent exactly for MapServer.  Stephan can you tackle
> this again?  Or do you need assistance?  -jeff
>
>
>
> On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:
>> Hi all,
>>
>> Just an update on the status of our OGC certification renewals:
>> We currently have 3 projects under certification:
>> MapServer, GDAL and pycsw.
>>
>> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
>> be certified once again.
>> Even has reported an issue with CITE tests and GDAL, so our
>> application is waiting for feedback from CITE developers.
>> Unfortunately MapServer has not yet responded (adding mapserver-dev
>> list in CC). There is still time for other projects to submit their
>> CITE test results and get certified through the OSGeo account.
>>
>> Best,
>> Angelos
>>
>> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>>    Open Source Geospatial Foundation
>>>
>>> *! Your Compliance Records Expire Today !*
>>>
>>> This is an automated email to inform you that your OGC-certified
>>> compliance
>>> license(s) for the following products are due to be renewed by
>>> *October 31st,
>>> 2017*. After that date your products will no longer be listed as
>>> certified OGC
>>> compliant.
>>>
>>> If you have already received an earlier notice and have started the
>>> renewal
>>> process please ignore this message.
>>>
>>> We invite you to easily renew online in our implementation portal:
>>> http://www.opengeospatial.org/resource/products/registration
>>>
>>> As a reminder, the account used to manage your certification listings
>>> is: *osgeo
>>> ([hidden email] <mailto:[hidden email]>)*
>>>
>>> If you have any questions please send an email to
>>> [hidden email]
>>> <mailto:[hidden email]>. The OGC compliance team will
>>> be more
>>> than glad to help you.
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>>      Current OGC-Compliant Listings
>>>
>>>
>>>        GDAL/OGR 1.11
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0     2014-08-15
>>> OGC KML (Level 2) 2.2.0     2014-08-15
>>> OGC KML (Level 3) 2.2.0     2014-08-15
>>>
>>>
>>>        GDAL/OGR 2.1
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 2) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 3) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>>
>>>        MapServer 6.2
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>>> (OGC Reference Implementation)    2016-01-12
>>>
>>>
>>>        pycsw 1.10
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2    
>>> 2016-01-26
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2     2016-01-26
>>>
>>>
>>>        pycsw 2.0
>>>
>>> Specification(s)    Original Certification
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>>> (OpenSearch) 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>> \
> _______________________________________________
> mapserver-dev mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev


_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Lime, Steve D (MNIT)
In reply to this post by jmckenna

I thought some of Dan's minions may have been involved - Alan or Julian. Regardless I think it would be good to maintain compliance. According to the OGC website only WMS 1.3 is certified and listed as an official reference implementation (see http://www.opengeospatial.org/resource/products/compliant). I imagine we had other certifications at one time but $'s probably limited participation. The CITE configurations must still exist somewhere.


Any one interested in leading?


Steve



From: mapserver-dev <[hidden email]> on behalf of Jeff McKenna <[hidden email]>
Sent: Tuesday, October 31, 2017 2:45:40 PM
To: [hidden email]
Subject: Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)
 
I believe Stephan did this for WMS before, but I'm not sure where these
renewal notices are sent exactly for MapServer.  Stephan can you tackle
this again?  Or do you need assistance?  -jeff



On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:
> Hi all,
>
> Just an update on the status of our OGC certification renewals:
> We currently have 3 projects under certification:
> MapServer, GDAL and pycsw.
>
> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
> be certified once again.
> Even has reported an issue with CITE tests and GDAL, so our application
> is waiting for feedback from CITE developers.
> Unfortunately MapServer has not yet responded (adding mapserver-dev list
> in CC). There is still time for other projects to submit their CITE test
> results and get certified through the OSGeo account.
>
> Best,
> Angelos
>
> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>    Open Source Geospatial Foundation
>>
>> *! Your Compliance Records Expire Today !*
>>
>> This is an automated email to inform you that your OGC-certified
>> compliance
>> license(s) for the following products are due to be renewed by
>> *October 31st,
>> 2017*. After that date your products will no longer be listed as
>> certified OGC
>> compliant.
>>
>> If you have already received an earlier notice and have started the
>> renewal
>> process please ignore this message.
>>
>> We invite you to easily renew online in our implementation portal:
>> http://www.opengeospatial.org/resource/products/registration
>>
>> As a reminder, the account used to manage your certification listings
>> is: *osgeo
>> ([hidden email] <[hidden email]>)*
>>
>> If you have any questions please send an email to
>> [hidden email]
>> <[hidden email]>. The OGC compliance team will
>> be more
>> than glad to help you.
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>>      Current OGC-Compliant Listings
>>
>>
>>        GDAL/OGR 1.11
>>
>> Specification(s)    Original Certification
>> OGC KML 2.2.0     2014-08-15
>> OGC KML (Level 2) 2.2.0     2014-08-15
>> OGC KML (Level 3) 2.2.0     2014-08-15
>>
>>
>>        GDAL/OGR 2.1
>>
>> Specification(s)    Original Certification
>> OGC KML 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC KML (Level 2) 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC KML (Level 3) 2.2.0
>> (OGC Reference Implementation)    2016-11-30
>>
>>
>>        MapServer 6.2
>>
>> Specification(s)    Original Certification
>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>> (OGC Reference Implementation)    2016-01-12
>>
>>
>>        pycsw 1.10
>>
>> Specification(s)    Original Certification
>> OpenGIS Catalogue Service Implementation Specification 2.0.2    
>> 2016-01-26
>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>> Service for
>> the Web] 2.0.2     2016-01-26
>>
>>
>>        pycsw 2.0
>>
>> Specification(s)    Original Certification
>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>> (OGC Reference Implementation)    2016-11-30
>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>> (OpenSearch) 3.0
>> (OGC Reference Implementation)    2016-11-30
>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>> (OGC Reference Implementation)    2016-11-30
>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>> Service for
>> the Web] 2.0.2
>> (OGC Reference Implementation)    2016-11-30
>>
>>\
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev

_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

jmckenna
Administrator
I'm interested in helping.  Not sure of what access I need.  But I am
throwing my hat in yes.  Maybe we can have several helping?  I feel this
is important, WMS reference implementation for MapServer. -jeff



On 2017-11-01 5:34 PM, Lime, Steve D (MNIT) wrote:

> I thought some of Dan's minions may have been involved - Alan or Julian.
> Regardless I think it would be good to maintain compliance. According to
> the OGC website only WMS 1.3 is certified and listed as an official
> reference implementation (see
> http://www.opengeospatial.org/resource/products/compliant). I imagine we
> had other certifications at one time but $'s probably limited
> participation. The CITE configurations must still exist somewhere.
>
>
> Any one interested in leading?
>
>
> Steve
>
>
> ------------------------------------------------------------------------
> *From:* mapserver-dev <[hidden email]> on behalf
> of Jeff McKenna <[hidden email]>
> *Sent:* Tuesday, October 31, 2017 2:45:40 PM
> *To:* [hidden email]
> *Subject:* Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal
> Notification (Final Expiration Notice)
> I believe Stephan did this for WMS before, but I'm not sure where these
> renewal notices are sent exactly for MapServer.  Stephan can you tackle
> this again?  Or do you need assistance?  -jeff
>
>
>
> On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:
>> Hi all,
>>
>> Just an update on the status of our OGC certification renewals:
>> We currently have 3 projects under certification:
>> MapServer, GDAL and pycsw.
>>
>> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
>> be certified once again.
>> Even has reported an issue with CITE tests and GDAL, so our application
>> is waiting for feedback from CITE developers.
>> Unfortunately MapServer has not yet responded (adding mapserver-dev list
>> in CC). There is still time for other projects to submit their CITE test
>> results and get certified through the OSGeo account.
>>
>> Best,
>> Angelos
>>
>> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>>    Open Source Geospatial Foundation
>>>
>>> *! Your Compliance Records Expire Today !*
>>>
>>> This is an automated email to inform you that your OGC-certified
>>> compliance
>>> license(s) for the following products are due to be renewed by
>>> *October 31st,
>>> 2017*. After that date your products will no longer be listed as
>>> certified OGC
>>> compliant.
>>>
>>> If you have already received an earlier notice and have started the
>>> renewal
>>> process please ignore this message.
>>>
>>> We invite you to easily renew online in our implementation portal:
>>> http://www.opengeospatial.org/resource/products/registration
>>>
>>> As a reminder, the account used to manage your certification listings
>>> is: *osgeo
>>> ([hidden email] <mailto:[hidden email]>)*
>>>
>>> If you have any questions please send an email to
>>> [hidden email]
>>> <mailto:[hidden email]>. The OGC compliance team will
>>> be more
>>> than glad to help you.
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>>      Current OGC-Compliant Listings
>>>
>>>
>>>        GDAL/OGR 1.11
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0     2014-08-15
>>> OGC KML (Level 2) 2.2.0     2014-08-15
>>> OGC KML (Level 3) 2.2.0     2014-08-15
>>>
>>>
>>>        GDAL/OGR 2.1
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 2) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 3) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>>
>>>        MapServer 6.2
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>>> (OGC Reference Implementation)    2016-01-12
>>>
>>>
>>>        pycsw 1.10
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2    
>>> 2016-01-26
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2     2016-01-26
>>>
>>>
>>>        pycsw 2.0
>>>
>>> Specification(s)    Original Certification
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>>> (OpenSearch) 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>>\
> _______________________________________________
> mapserver-dev mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev


--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Lime, Steve D (MNIT)
There's a WIKI entry on the old OSGeo TRAC that details at CITE compliance testing activities for a number of OGC specs:

  https://trac.osgeo.org/mapserver/wiki/MapServerOGCCITECompliance

Search CITE on that wiki and there is lots of info. I think many of the pages are also on the github WIKI but the formatting isn't as nice. It's all pretty dated info though. If we could just get a summary of the process that would help - maybe from someone that has gone through the process before?

Steve

-----Original Message-----
From: mapserver-dev [mailto:[hidden email]] On Behalf Of Jeff McKenna
Sent: Wednesday, November 01, 2017 6:19 PM
To: [hidden email]
Subject: Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

I'm interested in helping.  Not sure of what access I need.  But I am
throwing my hat in yes.  Maybe we can have several helping?  I feel this
is important, WMS reference implementation for MapServer. -jeff



On 2017-11-01 5:34 PM, Lime, Steve D (MNIT) wrote:

> I thought some of Dan's minions may have been involved - Alan or Julian.
> Regardless I think it would be good to maintain compliance. According to
> the OGC website only WMS 1.3 is certified and listed as an official
> reference implementation (see
> http://www.opengeospatial.org/resource/products/compliant). I imagine we
> had other certifications at one time but $'s probably limited
> participation. The CITE configurations must still exist somewhere.
>
>
> Any one interested in leading?
>
>
> Steve
>
>
> ------------------------------------------------------------------------
> *From:* mapserver-dev <[hidden email]> on behalf
> of Jeff McKenna <[hidden email]>
> *Sent:* Tuesday, October 31, 2017 2:45:40 PM
> *To:* [hidden email]
> *Subject:* Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal
> Notification (Final Expiration Notice)
> I believe Stephan did this for WMS before, but I'm not sure where these
> renewal notices are sent exactly for MapServer.  Stephan can you tackle
> this again?  Or do you need assistance?  -jeff
>
>
>
> On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:
>> Hi all,
>>
>> Just an update on the status of our OGC certification renewals:
>> We currently have 3 projects under certification:
>> MapServer, GDAL and pycsw.
>>
>> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
>> be certified once again.
>> Even has reported an issue with CITE tests and GDAL, so our application
>> is waiting for feedback from CITE developers.
>> Unfortunately MapServer has not yet responded (adding mapserver-dev list
>> in CC). There is still time for other projects to submit their CITE test
>> results and get certified through the OSGeo account.
>>
>> Best,
>> Angelos
>>
>> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>>    Open Source Geospatial Foundation
>>>
>>> *! Your Compliance Records Expire Today !*
>>>
>>> This is an automated email to inform you that your OGC-certified
>>> compliance
>>> license(s) for the following products are due to be renewed by
>>> *October 31st,
>>> 2017*. After that date your products will no longer be listed as
>>> certified OGC
>>> compliant.
>>>
>>> If you have already received an earlier notice and have started the
>>> renewal
>>> process please ignore this message.
>>>
>>> We invite you to easily renew online in our implementation portal:
>>> http://www.opengeospatial.org/resource/products/registration
>>>
>>> As a reminder, the account used to manage your certification listings
>>> is: *osgeo
>>> ([hidden email] <mailto:[hidden email]>)*
>>>
>>> If you have any questions please send an email to
>>> [hidden email]
>>> <mailto:[hidden email]>. The OGC compliance team will
>>> be more
>>> than glad to help you.
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>>      Current OGC-Compliant Listings
>>>
>>>
>>>        GDAL/OGR 1.11
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0     2014-08-15
>>> OGC KML (Level 2) 2.2.0     2014-08-15
>>> OGC KML (Level 3) 2.2.0     2014-08-15
>>>
>>>
>>>        GDAL/OGR 2.1
>>>
>>> Specification(s)    Original Certification
>>> OGC KML 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 2) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC KML (Level 3) 2.2.0
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>>
>>>        MapServer 6.2
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>>> (OGC Reference Implementation)    2016-01-12
>>>
>>>
>>>        pycsw 1.10
>>>
>>> Specification(s)    Original Certification
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2    
>>> 2016-01-26
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2     2016-01-26
>>>
>>>
>>>        pycsw 2.0
>>>
>>> Specification(s)    Original Certification
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>>> (OpenSearch) 3.0
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>> Service for
>>> the Web] 2.0.2
>>> (OGC Reference Implementation)    2016-11-30
>>>
>>>\
> _______________________________________________
> mapserver-dev mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/mapserver-dev


--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)

Daniel Morissette
Hi Steve,

Just a quick clarification: that wiki page dates from an OGC compliance
effort about 8 years ago in which Mapgears was involved with support
from USACE. It is completely out of date, maybe it should be removed?

The official OGC compliance certificates obtained a couple of years ago
were the result of the work of a few other project members who took this
one step further and went through the whole process including the
paperwork with OGC. I don't want to name anyone because my memory is
fuzzy and I don't want to forget or put anyone on the spot by mistake,
but several of the names have already been raised in this thread I think.

Daniel


On 2017-11-03 10:38 AM, Lime, Steve D (MNIT) wrote:

> There's a WIKI entry on the old OSGeo TRAC that details at CITE compliance testing activities for a number of OGC specs:
>
>    https://trac.osgeo.org/mapserver/wiki/MapServerOGCCITECompliance
>
> Search CITE on that wiki and there is lots of info. I think many of the pages are also on the github WIKI but the formatting isn't as nice. It's all pretty dated info though. If we could just get a summary of the process that would help - maybe from someone that has gone through the process before?
>
> Steve
>
> -----Original Message-----
> From: mapserver-dev [mailto:[hidden email]] On Behalf Of Jeff McKenna
> Sent: Wednesday, November 01, 2017 6:19 PM
> To: [hidden email]
> Subject: Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal Notification (Final Expiration Notice)
>
> I'm interested in helping.  Not sure of what access I need.  But I am
> throwing my hat in yes.  Maybe we can have several helping?  I feel this
> is important, WMS reference implementation for MapServer. -jeff
>
>
>
> On 2017-11-01 5:34 PM, Lime, Steve D (MNIT) wrote:
>> I thought some of Dan's minions may have been involved - Alan or Julian.
>> Regardless I think it would be good to maintain compliance. According to
>> the OGC website only WMS 1.3 is certified and listed as an official
>> reference implementation (see
>> http://www.opengeospatial.org/resource/products/compliant). I imagine we
>> had other certifications at one time but $'s probably limited
>> participation. The CITE configurations must still exist somewhere.
>>
>>
>> Any one interested in leading?
>>
>>
>> Steve
>>
>>
>> ------------------------------------------------------------------------
>> *From:* mapserver-dev <[hidden email]> on behalf
>> of Jeff McKenna <[hidden email]>
>> *Sent:* Tuesday, October 31, 2017 2:45:40 PM
>> *To:* [hidden email]
>> *Subject:* Re: [mapserver-dev] [OGC Portal] OGC Compliance Renewal
>> Notification (Final Expiration Notice)
>> I believe Stephan did this for WMS before, but I'm not sure where these
>> renewal notices are sent exactly for MapServer.  Stephan can you tackle
>> this again?  Or do you need assistance?  -jeff
>>
>>
>>
>> On 2017-10-31 3:15 PM, Angelos Tzotsos wrote:
>>> Hi all,
>>>
>>> Just an update on the status of our OGC certification renewals:
>>> We currently have 3 projects under certification:
>>> MapServer, GDAL and pycsw.
>>>
>>> pycsw has passed all the tests for CSW 2.0 and CSW 3.0 and is ready to
>>> be certified once again.
>>> Even has reported an issue with CITE tests and GDAL, so our application
>>> is waiting for feedback from CITE developers.
>>> Unfortunately MapServer has not yet responded (adding mapserver-dev list
>>> in CC). There is still time for other projects to submit their CITE test
>>> results and get certified through the OSGeo account.
>>>
>>> Best,
>>> Angelos
>>>
>>> On 10/31/2017 04:03 PM, Barbara Sherman wrote:
>>>>     Open Source Geospatial Foundation
>>>>
>>>> *! Your Compliance Records Expire Today !*
>>>>
>>>> This is an automated email to inform you that your OGC-certified
>>>> compliance
>>>> license(s) for the following products are due to be renewed by
>>>> *October 31st,
>>>> 2017*. After that date your products will no longer be listed as
>>>> certified OGC
>>>> compliant.
>>>>
>>>> If you have already received an earlier notice and have started the
>>>> renewal
>>>> process please ignore this message.
>>>>
>>>> We invite you to easily renew online in our implementation portal:
>>>> http://www.opengeospatial.org/resource/products/registration
>>>>
>>>> As a reminder, the account used to manage your certification listings
>>>> is: *osgeo
>>>> ([hidden email] <mailto:[hidden email]>)*
>>>>
>>>> If you have any questions please send an email to
>>>> [hidden email]
>>>> <mailto:[hidden email]>. The OGC compliance team will
>>>> be more
>>>> than glad to help you.
>>>>
>>>> --------------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>>       Current OGC-Compliant Listings
>>>>
>>>>
>>>>         GDAL/OGR 1.11
>>>>
>>>> Specification(s)    Original Certification
>>>> OGC KML 2.2.0     2014-08-15
>>>> OGC KML (Level 2) 2.2.0     2014-08-15
>>>> OGC KML (Level 3) 2.2.0     2014-08-15
>>>>
>>>>
>>>>         GDAL/OGR 2.1
>>>>
>>>> Specification(s)    Original Certification
>>>> OGC KML 2.2.0
>>>> (OGC Reference Implementation)    2016-11-30
>>>> OGC KML (Level 2) 2.2.0
>>>> (OGC Reference Implementation)    2016-11-30
>>>> OGC KML (Level 3) 2.2.0
>>>> (OGC Reference Implementation)    2016-11-30
>>>>
>>>>
>>>>         MapServer 6.2
>>>>
>>>> Specification(s)    Original Certification
>>>> OpenGIS Web Map Service (WMS) Implementation Specification 1.3.0
>>>> (OGC Reference Implementation)    2016-01-12
>>>>
>>>>
>>>>         pycsw 1.10
>>>>
>>>> Specification(s)    Original Certification
>>>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>>>> 2016-01-26
>>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>>> Service for
>>>> the Web] 2.0.2     2016-01-26
>>>>
>>>>
>>>>         pycsw 2.0
>>>>
>>>> Specification(s)    Original Certification
>>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding 3.0
>>>> (OGC Reference Implementation)    2016-11-30
>>>> OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding
>>>> (OpenSearch) 3.0
>>>> (OGC Reference Implementation)    2016-11-30
>>>> OpenGIS Catalogue Service Implementation Specification 2.0.2
>>>> (OGC Reference Implementation)    2016-11-30
>>>> OpenGIS Catalogue Service Implementation Specification [Catalogue
>>>> Service for
>>>> the Web] 2.0.2
>>>> (OGC Reference Implementation)    2016-11-30
>>>>
>>>> \
>> _______________________________________________
>> mapserver-dev mailing list
>> [hidden email]
>> https://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>


--
Daniel Morissette
Mapgears Inc
T: +1 418-696-5056 #201
_______________________________________________
mapserver-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/mapserver-dev