Paul -
Thanks for the email. I am not exactly sure of the full history of the SF SQL specification. However, this OGC specification was written by more than just Oracle. ESRI, Inc, IBM Corporation, Informix Software, Inc and MapInfo Corporation were also part of the submission team. There were multiple iterations of the submission based on review and comment by many other members. After review and reworking the document, it became an OGC specification in 1998. The current version of the Spec is 1.1, dated May 1999. This document has also been reviewed by the ISO TC 211 organization.
Now, in 1999, the OGC also developed a conformance testing suite for the SF SQL specification. In order to gain conformance, Oracle, ESRI, and others had to submit working product for testing. This was and still is an independent validation for conformance. Since then, Hitachi, IBM, and ESRI also have obtained conformance to the SF SQL specification.
Now in terms of your particular issue, anyone who has an issue with an OGC specification can write a formal change request and submit it to the OGC. You do not need to be a member to do this. We gladly accept all input from those working to implement our specifications.
At the same time, every OGC specification has a set of "mandatory" parts that must be implemented in order to be considered for conformance. This mandatory set is also defined and agreed to by the member consensus process. If there is an issue with this, then the same process can be followed. Send in a change request or comment.
Again, thanks for the question and expressing your concern.
Carl
To unsubscribe, write to gislist-unsubscribe@geocomm.com ________________________________________________________________________ GeoCommunity GeoBids - less than $1 per day! Get Access to the latest GIS & Geospatial Industry RFPs and bids http://www.geobids.com
Setup a GeoCommunity Account and have access to the GISDataDepot DRG & DOQQ Catalog http://www.geocomm.com/login.php
|