OGC Policy

Compliance Testing Program Policies & Procedures
Gobe Hobona Editor
Version: 1.1
OGC Policy


Document number:08-134r11
Document type:OGC Policy
Document subtype:
Document stage:Approved
Document language:English

License Agreement

Permission is hereby granted by the Open Geospatial Consortium, (“Licensor”), free of charge and subject to the terms set forth below, to any person obtaining a copy of this Intellectual Property and any associated documentation, to deal in the Intellectual Property without restriction (except as set forth below), including without limitation the rights to implement, use, copy, modify, merge, publish, distribute, and/or sublicense copies of the Intellectual Property, and to permit persons to whom the Intellectual Property is furnished to do so, provided that all copyright notices on the intellectual property are retained intact and that each person to whom the Intellectual Property is furnished agrees to the terms of this Agreement.

If you modify the Intellectual Property, all copies of the modified Intellectual Property must include, in addition to the above copyright notice, a notice that the Intellectual Property includes modifications that have not been approved or adopted by LICENSOR.


This license is effective until terminated. You may terminate it at any time by destroying the Intellectual Property together with all copies in any form. The license will also terminate if you fail to comply with any term or condition of this Agreement. Except as provided in the following sentence, no such termination of this license shall require the termination of any third party end-user sublicense to the Intellectual Property which is in force as of the date of notice of such termination. In addition, should the Intellectual Property, or the operation of the Intellectual Property, infringe, or in LICENSOR’s sole opinion be likely to infringe, any patent, copyright, trademark or other right of a third party, you agree that LICENSOR, in its sole discretion, may terminate this license without any compensation or liability to you, your licensees or any other party. You agree upon termination of any kind to destroy or cause to be destroyed the Intellectual Property together with all copies in any form, whether held by you or by any third party.

Except as contained in this notice, the name of LICENSOR or of any other holder of a copyright in all or part of the Intellectual Property shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Intellectual Property without prior written authorization of LICENSOR or such copyright holder. LICENSOR is and shall at all times be the sole entity that may authorize you or any third party to use certification marks, trademarks or other special designations to indicate compliance with any LICENSOR standards or specifications. This Agreement is governed by the laws of the Commonwealth of Massachusetts. The application to this Agreement of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded. In the event any provision of this Agreement shall be deemed unenforceable, void or invalid, such provision shall be modified so as to make it valid and enforceable, and as so modified the entire Agreement shall remain in full force and effect. No decision, action or inaction by LICENSOR shall be construed to be a waiver of any rights or remedies available to it.

None of the Intellectual Property or underlying information or technology may be downloaded or otherwise exported or reexported in violation of U.S. export laws and regulations. In addition, you are responsible for complying with any local laws in your jurisdiction which may impact your right to import, export or use the Intellectual Property, and you represent that you have complied with any regulations or registration procedures required by applicable law to make this license enforceable.

I.  Abstract

This document describes the Open Geospatial Consortium (OGC) Compliance Testing Program. The document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards.

II.  Security considerations

No security considerations have been made for this document.

III.  Submitters

All questions regarding this submission should be directed to the editor or the submitters:

Name Affiliation Role
Gobe Hobona OGC Editor
Luis Bermudez OGC Editor Emeritus
Sam Bacharach OGC Editor Emeritus

Compliance Testing Program Policies & Procedures

1.  Scope

This document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards.

2.  Terms and definitions

This document uses the terms defined in OGC Policy Directive 49, which is based on the ISO/IEC Directives, Part 2, Rules for the structure and drafting of International Standards. In particular, the word “shall” (not “must”) is the verb form used to indicate a requirement to be strictly followed to conform to this document and OGC documents do not use the equivalent phrases in the ISO/IEC Directives, Part 2.

This document also uses terms defined in the OGC Standard for Modular specifications (OGC 08-131r3), also known as the ‘ModSpec’. The definitions of terms such as standard, specification, requirement, and conformance test are provided in the ModSpec.

For the purposes of this document, the following additional terms and definitions apply.

2.1. Abstract Test Suite (ATS)

A set of testable assertions about the functionality of a standard, which an implementation must support in order to achieve compliance to the standard. ATS are based on the conformance clauses defined in the standard.

2.2. Compliance

A state of a specific software product, which implements an OGC Standard and has passed the Compliance Testing Evaluation.

2.3. Compliance and Interoperability Testing & Evaluation (CITE)

The same as Compliance Testing Program.

2.4. Conformance

A standard’s “abstract conformance” to Standards Packages for that standard (see ISO 19105:2000 Geographic information — Conformance and Testing at ).

2.5. Candidate Organization

An organization that has made, or intends to make, an application for compliance testing.

2.6. Candidate Product

A particular product version that has been submitted for compliance testing by a Candidate Organization.

2.7. Certification Authority

The body that certifies that a Candidate Organization meets the requirements to receive a Compliance Certificate—in this case, the Open Geospatial Consortium, Inc.

2.8. Compliance Testing Engine

A software tool use to evaluate compliance of candidate products.

2.9. Compliance Testing Evaluation Procedure

Set of steps used to evaluate a software product for proper implementation of an OGC standard.

2.10. Compliance Test Package (CTP)

This includes the ETS, test data sets, and a reference to the Standards Package and TEAM Engine build. This is versioned to represent a particular state of each component (ETS, test data). Note that changes to Test Package components may not necessitate a change in the Standards Package.

2.11. Compliance Testing Language (CTL)

An XML grammar used for documenting and scripting suites of tests, used by the Compliance Testing Engine. It is the OGC best practice document OGC 06-126.

2.12. Executable Test Suite (ETS)

A set of code (e.g. Java and CTL) that provides runtime tests for the assertions defined by the ATS. Test data required to do the tests are part of the ETS.

2.13. Implementation

A computer program that claims to fulfill the requirements defined in a particular OGC Standard.

2.14. Implementation Standard

A document or set of documents containing a technology specification created and approved by OGC. It may define a service interface, an encoding language, specific message encodings or data formats.

2.15. Licensee

Organization that has been granted an OGC Certification Trademark License over a implementation software product, which a version has been certified as compliant for a particular version of a standard.

2.16. OGC CITE Subcommittee (SC)

A sub-committee of the OGC Technical Committee (TC) consisting of OGC Members interested in the Compliance Testing Program. The SC guides the direction and focus of CITE, through its role in reviewing formal motions brought from OGC Members and Staff, and recommending approval by the TC.

2.17. OGC Member

an organization that is a member in good standing of OGC.

2.18. OGC Planning Committee (PC)

A committee of the OGC consisting of representatives from OGC Principal and Strategic Members. The PC guides the direction and focus of the OGC Specification Program, through its role in approving formal motions brought from the OGC TC.

2.19. OGC Staff

Individuals employed directly by OGC or seconded to OGC by its Strategic Members.

2.20. OGC Technical Committee (TC)

A committee of the OGC consisting of representatives from all OGC member organizations. The TC develops standards, specifications, and best practices, subject to approval by the OGC Planning Committee.

2.21. OGC Compliance Test Coordinator (CTC)

The OGC staff member responsible to coordinate and manage the operation of the Compliance Testing Program.

2.22. OGC Web Testing Facility

Software used by OGC to check compliance of software to OGC standards. It is available as a web interface. OGC has an official web site for approved official CTPs and a beta web site for beta CTPs.

2.23. Reference Implementation (RI)

A fully functional, licensed copy of a tested, branded software that has passes the test for an associated conformance class in a version of an Implementation Standard and that is free and publicly available for testing via a web service or download. The RI does not need to pass all the conformance classes within the standard. In most of the cases, the Reference Implementation will pass at least the core and possibly some number of extension conformance classes. Multiple reference implementations can exist for an associated version of an Implementation Standard

2.24. Software Implementation

The same as Implementation.

2.25. Standards Package

A set of documents including the Implementation Standard Revision, all appropriate schemas supporting the Implementation Standard Revision, the conformance clauses, and the ATS. This is versioned to represent a particular state of each component (standard, schemas, conformance clauses).

2.26. Testing Evaluation And Measurement (TEAM) Engine

An open source software package designed for testing web services and other resources. It executes test scripts written in Compliance Test Language (CTL). It is used at the OGC Web Testing Facility.

2.27. TestNG

A testing framework implemented in the Java programming language and supporting unit, functional, end-to-end, integration, and other forms of testing.

3.  Introduction

3.1.  Overview Document

The Compliance Test Program provides the resources, procedures, and policies to certify products for compliance with one or more OGC standards.

The primary purpose of the Compliance Testing Program is to increase systems interoperability while reducing technology risks by providing a process whereby compliance with OGC standards can be tested. The Compliance Testing Program provides confidence to technology vendors and buyers. Vendors feel confident that they are providing a product compliant with OGC standards, which will be easier to integrate and easier to market. Buyers fill confident that a compliant product will work with another compliant product based on the same OGC standard, regardless of which company developed the product.

3.2.  Changes to this document

Any changes to this document are discussed at the OGC CITE Steering Committee (SC). Main changes are discussed at the Planning Committee (PC). Ultimately the Technical Committee (TC) votes for the release and approval of this document. A change request can also be submitted against this document via the OGC web site at

4.  Compliance Testing Program Roles and Responsibilities

4.1.  CITE Subcommittee

The CITE Subcommittee (CITE SC) is a committee of the OGC TC consisting of OGC Members interested in the Compliance Testing Program. CITE SC has the following responsibilities:

  • Guides the direction of the Compliance Testing Program.

  • Reviews formal motions brought from OGC Members and OGC Staff.

  • Submits formal motions and recommends approval by the TC.

  • Reviews and approves roadmap.

4.2.  Director of Interoperability Certification

The Director of interoperability Certification currently oversees the Compliance Testing Program and acts as the Compliance Testing Coordinator.

4.3.  The Compliance Testing Coordinator

The Compliance Testing Coordinator (CTC) is the OGC Staff member responsible for coordinating and managing the operation of the Compliance Testing Program. The CTC has the following responsibilities:

  • Propose candidate guidelines, policies, and procedures to the CITE SC.

  • Coordinate the developing and maintenance of Compliance Test Packages.

  • Coordinate the developing and maintenance of the Compliance Testing Engine.

  • Propose candidate Compliance Test Packages to the CITE SC.

  • Maintain guidelines and documentation of the Program.

  • Select Reference Implementations (RI) for a Compliance Test Package and coordinate with the Reference Implementations developers for proper maintenance.

  • Coordinate the Compliance Testing Evaluation of a Candidate Product.

  • Manage and execute the interpretation and clarification process in collaboration with Standards Working Groups and Revision Working Groups.

  • Manage and execute the dispute and challenge resolution process in collaboration with the
    appropriate working groups and OGC Member discussion forums.

4.4.  The CITE Subcommittee, Technical and Planning Committees (PC)

With respect to compliance testing, the SC, TC and PC have the following responsibilities:

  • Review and approve compliance testing guidelines, policies, and procedures.

  • Review and select Compliance Test Packages including adaptations and provide an analysis of the adaptations to the CTC.

  • Approve the release of Compliance Test Package versions.

4.5.  OGC Compliance Team

The OGC Compliance Team is composed of OGC staff supporting this program. It includes the Compliance Testing Coordinator and other OGC staff.

For compliance testing, the OGC Staff has the following responsibilities:

  • Support the Compliance Testing Coordinator related to the Compliance Testing Program.

  • Administer the certification process including invoice processing and fees.


5.  Compliance Testing Evaluation Procedure

5.1.  Description of the Compliance Testing Evaluation Procedure

The Compliance Testing Evaluation Procedure is a set of steps used to evaluate a software product for proper implementation of an OGC standard. OGC has setup a web site providing an online procedure for most of the tests; however, there are some tests that are not available via the web site. The tests not available as an online test (e.g. Simple Feature related tests) can be found here:

The online test procedure is detailed in Figure 1. A box indicates a process. A red box indicates a process for which a Candidate Organization (CO) is responsible. A blue box indicates a process for which the Compliance Team (CT) is responsible.

In August of 2013, OGC made available a compliance submission website simplifying the submission process and the need to submit forms and results manually. The forms are available as online web forms and the web site links with the testing website facility. Link:


Figure 1

Figure 1 – Flow chart for the Compliance Testing Evaluation Procedure

5.2.  Policy on Previously Approved Products and Future Releases

Compliance will be determined once for a product version with respect to a particular Implementation Standard Version, and requires the successful completion of the Testing Procedure. Compliance of future releases of the same product requires the successful completion of the Testing Procedure.

5.3.  Compliance Determination

Candidate Products that pass all the tests in a Compliance Test Package, and that OGC has reviewed and certified as having passed those tests, are considered compliant with that Implementation Standard version. This is the sole criterion for determining the compliance of a Candidate Product.

5.4.  Test Records

The CTC will maintain a file of records pertaining to testing, hereafter referred to as the OGC Testing Record. Records pertaining to a particular organization will be available for examination by that organization upon request. Records maintained in the OGC Testing Record will be maintained for a minimum of three (3) years.

OGC will make a good faith effort to retain the following documents in the OGC Test Record:

  • Abstract Test Suites,

  • Executable Test Suites,

  • Test Summary Reports (and all attachments),

  • Test Failure Notification Letters,

  • Compliance Certificates,

  • Trademark License Agreements,

  • Compliant Product Records, and

  • Any other correspondence of importance related to the OGC Compliance Testing Program.

5.5.  Certificate Issuance

A Compliance Certificate (Appendix F) is issued for tested software products that successfully pass the Compliance Testing Evaluation Procedure.

The holder of such a certificate is entitled to use the ”Certified OGC Compliant” mark (Figure 2) according to terms and conditions set forth in the Trademark License Agreement (Appendix E) and after the applicable Trademark Licensing Fee has been paid (Appendix G). The Trademark Licensing Fee shall be paid annually in order to maintain a valid certificate.


Figure 2

Figure 2 – Certified OGC Compliant Mark

The Compliance team will create an OGC Testing Record with a copy of the Compliance Certificate and the supporting Test Summary Report. The Compliance Team will add any product that receives a Compliance Certificate to the Compliant Products Record (Appendix F). Products that are added to the Compliant Products Record will be removed three (3) months after failure to pay the annual trademark-licensing fee, or by written request of the Candidate Organization. Relevant information from the Compliant Products Record will be maintained on the OGC public web site ( for every product that receives a Compliance Certificate.

In order to avoid confusion in the place, OGC reserves the right to terminate the right of a Candidate Organization to use OGC trademarks to indicate successful Compliance testing at such time as OGC deems consumer confusion likely. In the event that this occurs, OGC shall give advance notice to the extent possible, and transitional steps will be taken, to minimize any inconvenience to vendors of Candidate Products.

4.6. Live Logos

OGC provides a link to live logos for organizations that have successfully passed the Compliance Testing Evaluation Procedure. Every product has its own link where an image is automatically generated. An example is shown in Figure 3. The image contains the company name, the product name and the standards for which the product has been certified with. It also contains the date of validity. The logo links directly to the OGC public record that contains more information about the company.


Figure 3

Figure 3 – Live Logo

6.  Compliance Test Package Development

Subject to available resources and the perceived need of the marketplace, OGC intends to adopt and maintain at least one Compliance Test Package (CTP) for each conformance class in each OGC Implementation Standard.

A CTP is composed of an Abstract Test Suite (ATS) and an Executable Test Suite (ETS). An ATS is a set of testable assertions about the functionality of a standard, which an implementation must support in order to achieve compliance to the standard. An ATS is based on the conformance classes defined in the standard in accordance with the latest revision of “OGC 08-131r3 The Specification Model — A Standard for Modular specifications”. An ETS is a set of code (e.g. Java and CTL) that provides runtime tests for the assertions defined by the ATS. Test data required to do the tests are part of the ETS.

OGC provides the following resources that support the development and maintenance of the CTP:

The CITE wiki ( provides further information about these resources.

The overall process to develop a CTP is illustrated in Figure 4.


Figure 4

Figure 4 – Overall Compliance Test Package Development

Tests are composed of conformance classes. It is required to have at least three implementations that pass a conformance class for a conformance class to be released as official. However, if a test has been in beta for more than 6 months and one or two implementations have passed the test, the CITE SC can consider a motion related to releasing the test as official with an exception about requiring three minimum implementations.

When the TC approves a Compliance Test Package. It is published at the OGC Web-based Testing Facility. Organizations may then certify their products using the new Compliance Test Package as described in Clause 5.

The roadmap is maintained at the public CITE wiki (

6.1.  Parties Who May Develop Compliance Test Packages

Candidate Compliance Test Packages may be developed by any of:

  • OGC Members

  • The CTC and/or other OGC Staff

  • OGC Testing Contractors (under the direction of the CTC)

Candidate Compliance Test Packages must be submitted to the CTC for review and (potential) adoption.

6.2.  Compliance Test Package Maintenance and Criteria for Review

In general, OGC testing staff will maintain CTP under the direction of the CTC. This maintenance responsibility may be delegated to an OGC member or OGC Staff by the CTC. Compliance Test Package maintenance is called for when a new Implementation Standard version is issued by OGC, when the dispute resolution process mandates such a change (see Clause 9), or when the CTC, in his/her sole discretion finds issues that require maintenance.

In any case, the CTC is responsible for the review of minor revisions to the Compliance Test Package. The resulting Compliance Test Package revision will then be made available to the OGC membership via the CITE SC mailing list for a minimum of five business days. The criteria for the CTC review and TC approval is that:

  • The Compliance Test Package revision is complete with respect to the Compliance Testing Guideline for that particular Implementation Standard version.

  • Consistency with the wording and intent of the particular Implementation Standard version.

  • Consistency with OGC policy and practice.

  • Versions of compliance test packages are maintained in the configuration management system and recorded with the compliance test execution.

Delivery, testing, configuration control of compliance test packages is described in the CITE Configuration Management Procedures.

Major revisions to a Compliance Test Package shall go through the same process as a new Compliance Test Package, as described in Clause 6, Compliance Test Package Development.

A revision is considered major by the judgment of the CTC. However, any revision resulting in the change of greater than 20 percent of executable tests must be considered a major revision.

6.3.  Compliance Test Package Availability

Compliance Test Packages will be provided in electronic form, when they are available, via OGC’s public web site. The Compliance Test Package will be made available along with full documentation of the OGC Compliance Testing Program (this document) and Compliance Testing Guidelines.

6.4.  Compliance Test Package Submitters

Compliance Test Package submitters must provide either 1) unrestricted ownership of the Compliance Test Package to OGC, or 2) an agreement to grant OGC a non-exclusive, royalty-free, paid-up, unrestricted worldwide license to copy and distribute their submission to the OGC membership, and, if adopted by OGC, the unrestricted right to modify, enhance, and make derivative works from the materials and to copy and distribute the materials, modifications, enhancements, and derivative works both inside and outside of the OGC membership. Materials include software source code, documentation in multimedia or text formats, and in other resource part of the test package or required to perform the testing.

6.5.  Beta Testing impact on Certificates

These first three implementations (can be reference implementations or not) to pass 100% of the compliance procedure, while the test is in beta, will have their Trademark License Fee waived through the annual licensing period for the product.

7.  Reference Implementations

7.1.  Definition and Determination

A fully functional, licensed copy of a tested, branded software that has passes the test for an associated conformance class in a version of an Implementation Standard and that is free and publicly available for testing via a web service or download. The Reference Implementation does not need to pass all the conformance classes within the standard. In most of the cases, the Reference Implementation will pass at least the core and possibly some number of extension conformance classes. Multiple reference implementations can exist for an associated version of an Implementation Standard. The coordinator after reviewing the results and checking the public interface of the software will determine if the implementation can be a reference implementation.

OGC will make its best effort to host Reference Implementations on an OGC server to help others in the community to develop compliant implementations.

7.2.  Service Level Requirements

If the Reference Implementation is not hosted by OGC, it is expected the following from the organization providing the Reference Implementation

The Reference Implementation should

  • be available in a reliable web server with 99% uptime.

  • pass the test for every operational release of OGC Testing infrastructure (e.g. TEAM Engine)

If any of the aforementioned conditions fail the CITE coordinator can remove the Reference Implementation label of an existing implementation.

7.3.  Fee Incentives for Reference Implementations

OGC will provide an incentive to the first two Reference Implementations that pass the test related to a conformance class within a version of an Implementation Standard. OGC will waive the license fee every year as long as the Reference Implementation passes again the conformance class test successfully.

8.  Compliance Test Engine Maintenance

The OGC’s accepted Compliance Test Engine is an open source product called the TEAM Engine. New contributions to the source are encouraged to enhance and extend the capability of compliance testing. Developers of the Compliance Test Engine Extent are responsible for ensuring the software is operational with existing compliance test packages and Reference Implementations.

A production and a beta version of TEAM engine are released by the CTC. After passing an acceptance period, the beta version is released into production.

When major changes are made to the TEAM engine, regression testing is performed with the latest released version of compliance tests for every specification version and OGC profile and Reference Implementation. If the results of the regression testing match the current compliance test and released TEAM Engine version, the new version of TEAM Engine is put into beta test. In some cases, the new version of TEAM Engine may be incompatible with previous compliance tests or reference implementations with an acceptable technical explanation. When incompatibilities cause differences in the test results, the CTC may require a change to the compliance test package or RI. A change in dependent software or obsolete reference implementations may deprecate past versions of compliance tests with the new versions of TEAM Engine.

Delivery, testing, and configuration control of compliance TEAM Engine is described in the CITE Configuration Management Procedures.

9.  Processing Disputes/Challenges

9.1.  Dispute Procedure

A “Compliance Issue” is defined as a problem identified from third party review or experience with a product after testing is completed and the product is available in the marketplace. The submitter of the issue should send an email to summarizing the problem.

The receipt of a Compliance Issue by CTC will set the following procedure in motion:

  1. The CTC will coordinate that the issue is captured in the Compliance Issue a tracking system.

  2. The CTC will provide clarification to the issue, if possible. If not, the CTC will suggest to use the CITE forum.

  3. The CTC will notify the disputing organization of the resolution and record the dispute as resolved, closing the issue in the issue tracker. The disputing organization may appeal the decision by submitting another Compliance issue.

  4. If issue submitter disagrees with the decision of the CTC, then CTC will forward the Compliance Issue to the OGC Review Board (CITE SC) for resolution along with proposed resolution alternatives and a recommendation. The issue will be opened again in the issue tracker.

  5. The CTC will then notify the disputing agreement the decision of the OGC Review Board (CITE SC). And will follows step 3.

9.2.  Adaptation of Compliance Test Packages

Organizations may have to adapt Compliance Test Packages to work with their products. OGC will provide guidance regarding allowable adaptations. In any case, OGC testing staff, in consultation with and under the approval authority of the CTC, must review the adaptation. The OGC testing staff review and CTC approval is to ensure that the original intent and functionality of the test suite is maintained. OGC testing staff must also document the adaptation, by inclusion of the adapted test suite, in the Compliance Test Summary Report (Appendix A). Candidate Organizations must submit adapted Compliance Test Packages at the time they submit a Self-Test Summary Report.

9.3.  Interpretation and Clarification of Standards

Issues regarding the interpretation or clarification of Implementation Standards are the responsibility of the applicable Standards Working Group (SWG) of the OGC Technical Committee (specifically, the SWG that corresponds to the Implementation Standard in question). If no SWG is currently active, then the TC Chair will form an ad hoc committee (comprised of the last standing SWG membership, if possible) to process the interpretation/clarification. The TC Chair can also decide to submit the issue to the OGC Review Board.

10.  Fees and Costs

OGC will not charge a fee for compliance testing under the Testing Procedure.

OGC will charge a fee for trademark licensing for Candidate Products that successfully pass a compliance test under the Testing Procedure; this fee is termed the Trademark Licensing Fee. This fee must be paid by organizations that wish to claim compliance with OGC Implementation Standards. This fee is not required to initiate and complete a test. The current fee structure is found in Appendix G of this document.

OGC will invoice a Candidate Organization that has submitted a Test Summary Report for the Trademark License Fee. This invoice must be paid before OGC will issue a Compliance Certificate and before OGC will deliver a countersigned Trademark License Agreement.

Annex A
Test Summary Report (TSR)

Submitters should now use the online test submission facility here

The web testing facility will capture and maintain the following information

Table A.1

Test Summary Report (TSR)
1. Test Completion Date
2. Web Testing (if using online OGC testing facility)
2a. Username
2b. Session Numbers
3. Candidate Organization
3a. Name of Organization
3b. Mailing Address
3c. City
3d. State/ Province
3e. Country
3f. Postal Code
3g. Web Link
4. Total Gross Annual Revenue of the organization that owns the IPR of the product ($US)
  • $0M-<$5M

  • $5M-<$50M

  • $50M-<$500M

  • $500M+

5. Technical Point of Contact
5a. Name of Individual
5b. Mailing Address
5c. City
5d. State/ Province
5e. Country
5f. Postal Code
5g. Telephone Number
5h. Facsimile Number
5i. Email Address
6. Financial Point of Contact
6a. Name of Individual
6b. Name of Department
6c. Mailing Address
6d. City
6e. State/ Province
6f. Country
6g. Postal Code
6h. Telephone Number
6i. Facsimile Number
6j. Email Address
7. Candidate Product Information
7a. Product Name
7b. Product Version
7c. Operating System Required
7d. Hardware Required
7e. Required Software
8. Implementation Standard Information
8a. Standard Name
8b. Standard Version
8c. Conformance Classes
I, being duly authorized to sign legal documents on behalf of my organization, certify that the Candidate Product complies with the above-indicated Implementation Standard(s).
9. Official Signature

Additional Instructions

Questions concerning the technical content of summary reports or the Compliance Testing Program in general should be addressed to:

Questions concerning payment should be addressed to the same address or contact the OGC’s General Enquiries desk (phone details are at

Annex B

This section is intentionally left blank.

Annex C

This section is intentionally left blank.

Annex D
Compliance Certificate Format

Compliance Certificates will have the following format, and will be available online on the OGC web site, Hard copy of the certificate can be made available upon request.


Figure D.1

Annex E
Trademark License Agreement

A TLA is an agreement between OGC and an organization that desires to use the OGC Compliance Mark in association with successful OGC Compliance Testing Evaluations involving one or more product and one ore more standards. The TLA must be completed when a company passes the Compliance Evaluation of their first product and desires to be certified complaint, which will allow the organization to use the OGC Certified Compliant Mark (See Appendix H). The TLA will be sent by OGC to the organizations that have submitted a test report.

Questions concerning the TLA should be addressed to:

Questions concerning payment should be addressed to the same address or contact the OGC’s General Enquiries desk