Khronos Frequently Asked Questions

OpenGL

What is the relationship between SGI and Khronos Group?

SGI is not a member of the Khronos Group. Khronos licenses the OpenGL ES trademark from SGI. Khronos is authorized to run the OpenGL ES adopter program.

Is an OpenGL ES adopter required to comply with OpenGL licensing when they have an OpenGL ES conformant product?

No.

OpenGL ES

What is the minimal agreement our company has to get in with Khronos to access Conformance test Suite for OpenVG (till 1.1), OpenGL ES (till 2.0) and OpenWF drivers?

All Khronos members which have accepted the Conformance Test Source License Agreement (CTSLA) section of
the Member’s agreement can access all conformance test suites for those APIs
for which a conformance test program is in place for no additional fees
beyond the annual membership fee.

In order to submit a product for certification, there is a one-time adopter
fee of $10,000 for Members, $15,000 for non-members. The adopter fee is
one-time for the life of the API version and allows for unlimited product
submissions with no additional fees.

What is the relationship between SGI and Khronos Group?

SGI is not a member of the Khronos Group. Khronos licenses the OpenGL ES trademark from SGI. Khronos is authorized to run the OpenGL ES adopter program.

Is an OpenGL ES adopter required to comply with OpenGL licensing when they have an OpenGL ES conformant product?

No.

We would like to know what membership will cost to obtain OpenVG and OpenGL, with the exact same type of membership?

The Khronos membership agreement includes a Conformance Test Source License Agreement (CTSLA). Members that have not excluded themselves from the CTSLA, have access to the conformance test source. Members wishing to claim conformance to OpenVG and OpenGL ES specifications would be required to execute the adopters agreement and pay the applicable fee for each API.

Current Adopter fees are available here: http://www.khronos.org/adopters/

COLLADA Pipeline

Where can I find frequently asked questions for COLLADA?

The official FAQ section for COLLADA is on the COLLADA.org website.

OpenMAX

We are looking forward to implementing OpenMAX compliance of codecs. Will the implementers get Khronos SDKs? If so please provide me the necessary directions.

OpenMAX has 3 levels of APIs, with separate specifications: OpenMAX AL, OpenMAX IL and OpenMAX DL. Referring to a codec implementation, I suspect the specification you would like to implement is OpenMAX IL.

There is currently no SDK available for OpenMAX IL. An open source implementation called Bellagio exist on SourceForge, but this implementation is not maintained by Khronos and does not provide you with any guarantee your components will be conformant with the OpenMAX IL specification. As the original work (Bellagio) has not been tested for conformance, any derivative work based on it, unless submitted for conformance testing as a complete work, could not be declared conformant either as you cannot guarantee that the interface for the codec was conformant in the first place.

The correct way forward to ensure conformance would be to sign the Khronos Adopters Agreement, pay the associated Conformance Testing Fees, then access and run the Conformance Test associated with the specification. You will find all the necessary information on the Khronos adopter page.

What steps will the Khronos Group take to create strong positive reaction in the marketplace?

Wide acceptance is important. The Khronos Group intends to give the specification high visibility to create and build industry awareness. Each Khronos Group promoter will work to sign on contributors and adopters so that extensive distribution of the specification can occur. This direct evangelism to all major application and device vendors will promote acceptance and adoption of the specifications the Khronos Group creates. The OpenMAX WG is creating and maintining a web site, white papers, and collateral. Members will assist in placing articles for print and evaluating specialized advertising.

Who will define and maintain the OpenMAX specification?

The Khronos Group will retain this responsibility.

What interaction will OpenMAX have with international and industry standards bodies?

The various founders of OpenMAX WG are also members of organizations such as MIPI,  ISO/MPEG and 3GPP. The WG will maintain relationships with these and other industry groups where appropriate.

How can interested parties get involved with the OpenMAX specification?

Interested parties can contact any of the Khronos promoting members to inquire about contributing to the specification. To learn more about becoming a Contributor or Promoter to the OpenMAX specification, visit the Membership FAQ.

When will the OpenMAX specification be complete?

We anticipate that the first specification for OpenMAX will appear in the second quarter of 2005.

How does OpenMAX work with Operating Systems?

It is an important goal of the OpenMAX standard to complement the multimedia frameworks of popular industry Operating Systems. Specifically, OpenMAX co-exists with and is complementary to existing APIs and libraries, including those from the Khronos Group and those provided by OS vendors; it is designed to be used by developers of those libraries and will support a wide range of processor architectures and their tool chains.

Are wireless applications the main focus of the OpenMAX standard?

Mobile and wireless computing have some very specific challenges in terms of performance, battery life and time to market. The founders of OpenMAX were the first to see this requirement, but the technologies and concepts are applicable to all applications where multimedia and graphics performance are important.

What are the benefits of such an open standard to the industry?

In order to create compelling multimedia products such as smartphones, media players and games consoles, developers need optimized low-level code. Currently this code is written mostly in assembly language and has to be rewritten on every different hardware platform.  This is expensive and time consuming.  With the OpenMAX standard, developers will have this optimized low-level code provided to them with the hardware platform.  This allows the developer to focus on creating higher level functionality, getting to market sooner and supporting a broader range of hardware platforms.

What "critical need" is OpenMAX solving?

With the wide range of hardware platforms, a standards-based approach aids in solving the problems associated in porting and optimizing middleware applications such as multimedia codecs, and graphics libraries between these platforms.

What is the goal of the OpenMAX effort?

OpenMAX was founded to address the need to accelerate the growth of compelling multimedia platforms and hence end-user products.  The end result is to standardize a set of open APIs for a variety of multimedia applications, including smartphones, media players, games and graphics, thus reducing the cost and complexity of porting multimedia software to new processors and architectures thereby accelerating application development overall.

What does OpenMAX stand for?

Open Media Acceleration primitives.

OpenVG

What is the minimal agreement our company has to get in with Khronos to access Conformance test Suite for OpenVG (till 1.1), OpenGL ES (till 2.0) and OpenWF drivers?

All Khronos members which have accepted the Conformance Test Source License Agreement (CTSLA) section of
the Member’s agreement can access all conformance test suites for those APIs
for which a conformance test program is in place for no additional fees
beyond the annual membership fee.

In order to submit a product for certification, there is a one-time adopter
fee of $10,000 for Members, $15,000 for non-members. The adopter fee is
one-time for the life of the API version and allows for unlimited product
submissions with no additional fees.

We would like to know what membership will cost to obtain OpenVG and OpenGL, with the exact same type of membership?

The Khronos membership agreement includes a Conformance Test Source License Agreement (CTSLA). Members that have not excluded themselves from the CTSLA, have access to the conformance test source. Members wishing to claim conformance to OpenVG and OpenGL ES specifications would be required to execute the adopters agreement and pay the applicable fee for each API.

Current Adopter fees are available here: http://www.khronos.org/adopters/

OpenWF

Why do the Composition and Display APIs have similar features for on-screen composition?

Both of the APIs can perform similar operations to the inputs and output to a screen. By having overlapping features it is not neccessary to implement both APIs, but choose the most suitable one. A WFD device is intended to expose the limitations of the underlying HW. There may be for example a limited number of pipelines in the display controller HW. A WFC device can always compose to memory, so it can overcome limitations by outputting intermediate results to memory and using them again as input.

When would it make sense for a WFD implementation to expose no pipelines?

The expected case for zero exposed pipelines is when the same manufacturer provides a WFD implementation as well as other graphics composition APIs, for instance WFC, such that exposing the WFD pipelines would be unnecessary since other more capable, less limited, composition graphics APIs exist. Given this case, the WFD implementation would be used to manage and configure the display hardware, but not be involved in the composition of displayed content.

What is the purpose of the "attribList" parameter of the WFC or WFD "create" functions?

The creation attribute list parameters are expected to be one of the primary means of extending the functionality of the APIs. At the moment most of the create functions do not have any defined attributes that can be passed in, but providing this feature allows for extensions to be written for these APIs in a fairly clean manner.

Why are the WFC & WFD extension query functions different than other Khronos APIs?

The OpenWF extension query functions (GetStrings, IsExtensionSupported) were developed per recommendations from several of the other Khronos working groups. Members of these other working groups have found that the previously defined methods are more cumbersome then expected, so suggestions were made to address this. It is expected that other Khronos APIs will, over time, move towards this new style of extension functions.

What is the point of allowing creation of more than one composition device with the same device ID?

As the multiple devices created from the same ID do not share any state, it is possible to create a device – context pair for each screen supported by the device and have a separate error state for each screen/ context.

Why is the WFD pipeline direct refresh attribute _not_ available for stream input?

The thought was that in the streaming case there is no need for the user to be aware of this since the buffers are provided/managed by the stream, not the user.

How can a WFC implementation access the screen using WFD API?

If a WFC implementation tries to access the screen using the public WFD API, it is likely to result in an error or preventing other clients from using WFD. The reason is that WFD API allows only one device instance created per device ID. It is recommended that interaction between the two APIs is handled using a propriety solution.

How and when is the WFD pipeline layering order decided?

Layering order of the WFD pipelines that can be bound to a particular port is expected to be a static feature of the implementation and likely of the hardware itself. For shareable pipelines, those that can be bound to more than one port (not simultaneously), the layering number of the pipeline for each port may be different, but the layering number in relation to a particular port is intended to be static.

What is the purpose for the WFD pipeline direct refresh attribute?

The WFD pipeline direct refresh attribute is intended to indicate to the client that the hardware is refreshing from the client provided directly bound image buffer. This is intended to denote to the client that any changes to the bound buffer contents may cause visual tearing or other display artifacts.

Does WFD support sharing of object handles?

The WFD specification was written with the expectation of a single client, the platform windowing system. The WFD object handles are single instance handles, meaning only one handle to an object can be created at any point in time. WFD handles are intended to be safe for use by multiple threads, in the same process, but the handle sharing mechanism is left to the API user.

Are OpenWF APIs thread and process safe?

The API specifications note that thread safety is indeed a goal. There is no requirement for per thread data storage. All API functions are intended to be safe when accessed from multiple threads within the same process. The subject of process safey is not addressed by the specifications. Process safety is left to the API user to resolve.

What pixel formats are supported by WFC or WFD APIs?

Input or output pixel formats are not addressed by the API specifications. Functions involving pixel input and output typically raise an error, if an unsupported format is used. To avoid trial and error type of usage, the native stream type, and/or EGL image type, may allow querying for supported pixel formats.

What is the minimal agreement our company has to get in with Khronos to access Conformance test Suite for OpenVG (till 1.1), OpenGL ES (till 2.0) and OpenWF drivers?

All Khronos members which have accepted the Conformance Test Source License Agreement (CTSLA) section of
the Member’s agreement can access all conformance test suites for those APIs
for which a conformance test program is in place for no additional fees
beyond the annual membership fee.

In order to submit a product for certification, there is a one-time adopter
fee of $10,000 for Members, $15,000 for non-members. The adopter fee is
one-time for the life of the API version and allows for unlimited product
submissions with no additional fees.

For Implementors

Why do the Composition and Display APIs have similar features for on-screen composition?

Both of the APIs can perform similar operations to the inputs and output to a screen. By having overlapping features it is not neccessary to implement both APIs, but choose the most suitable one. A WFD device is intended to expose the limitations of the underlying HW. There may be for example a limited number of pipelines in the display controller HW. A WFC device can always compose to memory, so it can overcome limitations by outputting intermediate results to memory and using them again as input.

When would it make sense for a WFD implementation to expose no pipelines?

The expected case for zero exposed pipelines is when the same manufacturer provides a WFD implementation as well as other graphics composition APIs, for instance WFC, such that exposing the WFD pipelines would be unnecessary since other more capable, less limited, composition graphics APIs exist. Given this case, the WFD implementation would be used to manage and configure the display hardware, but not be involved in the composition of displayed content.

What is the purpose of the "attribList" parameter of the WFC or WFD "create" functions?

The creation attribute list parameters are expected to be one of the primary means of extending the functionality of the APIs. At the moment most of the create functions do not have any defined attributes that can be passed in, but providing this feature allows for extensions to be written for these APIs in a fairly clean manner.

Why are the WFC & WFD extension query functions different than other Khronos APIs?

The OpenWF extension query functions (GetStrings, IsExtensionSupported) were developed per recommendations from several of the other Khronos working groups. Members of these other working groups have found that the previously defined methods are more cumbersome then expected, so suggestions were made to address this. It is expected that other Khronos APIs will, over time, move towards this new style of extension functions.

What is the point of allowing creation of more than one composition device with the same device ID?

As the multiple devices created from the same ID do not share any state, it is possible to create a device – context pair for each screen supported by the device and have a separate error state for each screen/ context.

How can a WFC implementation access the screen using WFD API?

If a WFC implementation tries to access the screen using the public WFD API, it is likely to result in an error or preventing other clients from using WFD. The reason is that WFD API allows only one device instance created per device ID. It is recommended that interaction between the two APIs is handled using a propriety solution.

For Integrators

Why is the WFD pipeline direct refresh attribute _not_ available for stream input?

The thought was that in the streaming case there is no need for the user to be aware of this since the buffers are provided/managed by the stream, not the user.

How and when is the WFD pipeline layering order decided?

Layering order of the WFD pipelines that can be bound to a particular port is expected to be a static feature of the implementation and likely of the hardware itself. For shareable pipelines, those that can be bound to more than one port (not simultaneously), the layering number of the pipeline for each port may be different, but the layering number in relation to a particular port is intended to be static.

What is the purpose for the WFD pipeline direct refresh attribute?

The WFD pipeline direct refresh attribute is intended to indicate to the client that the hardware is refreshing from the client provided directly bound image buffer. This is intended to denote to the client that any changes to the bound buffer contents may cause visual tearing or other display artifacts.

Does WFD support sharing of object handles?

The WFD specification was written with the expectation of a single client, the platform windowing system. The WFD object handles are single instance handles, meaning only one handle to an object can be created at any point in time. WFD handles are intended to be safe for use by multiple threads, in the same process, but the handle sharing mechanism is left to the API user.

Are OpenWF APIs thread and process safe?

The API specifications note that thread safety is indeed a goal. There is no requirement for per thread data storage. All API functions are intended to be safe when accessed from multiple threads within the same process. The subject of process safey is not addressed by the specifications. Process safety is left to the API user to resolve.

What pixel formats are supported by WFC or WFD APIs?

Input or output pixel formats are not addressed by the API specifications. Functions involving pixel input and output typically raise an error, if an unsupported format is used. To avoid trial and error type of usage, the native stream type, and/or EGL image type, may allow querying for supported pixel formats.

Technology Adopters and Conformance Tests

In reading your Adopter's Agreement, we noticed that in section 2, "Confidential Information" that the test results fall under this heading. Depending on the results of the tests, we'd want to share those results (not the Adopter's Package) with the vendor. Is this use of the test results acceptable? The vendor is under NDA with us.

Test results may be disclosed under NDA between customer and vendor or the other way around as long as it is made clear to the party receiving that:

  1. This does not allow a vendor to claim conformance unless they have filed the results and conformance has been granted
  2. The results are not allowed to be publically disclosed as proof of conformance
  3. Conformance does not flow from one party to another (i.e. if your company files conformance on an OEM product, that doesn’t automatically give the silicon vendor or IP supplier conformance)
What is the minimal agreement our company has to get in with Khronos to access Conformance test Suite for OpenVG (till 1.1), OpenGL ES (till 2.0) and OpenWF drivers?

All Khronos members which have accepted the Conformance Test Source License Agreement (CTSLA) section of
the Member’s agreement can access all conformance test suites for those APIs
for which a conformance test program is in place for no additional fees
beyond the annual membership fee.

In order to submit a product for certification, there is a one-time adopter
fee of $10,000 for Members, $15,000 for non-members. The adopter fee is
one-time for the life of the API version and allows for unlimited product
submissions with no additional fees.

You say that we must “successfully run the implementation with the Conformance Tests;” but these other conforming members are doing this on our platforms, aren’t we covered?

Conformance claims to not “pass through” from customers.

You say that we must “obtain the required license from the Khronos Group by signing the appropriate License Agreement;” , but I believe we are covered as member company

Not in the case of conformance- you will have to adopt and submit test results for approval to claim conformance.

I do not understand why we are being referred to the “adopter documents”.

An adopter may be a member or non-member, but all must adhere to the adopter process to make claims of conformance.

Our company does not submit conformance tests, but we require our graphics IP provider to do so with our products. Under http://www.khronos.org/adopters/conformant-products/#topengles you can see that other companies have submitted multiple tests with our company’s products. What’s the problem with us doing that?

Claims of conformance do not “pass-through” from customers.

We do not need to use the Khronos logos or trademarks in our marketing. Conformance submissions would hence not be needed. Is there a reduced fee for this kind of adopter?

Are you sure you do not need to use the name of the APIs in association with your product/platform?  Any use of a Khronos trademark (e.g. using the API name) in association with a specific product requires the execution of the Adopters Agreement and passing the conformance tests through making a submission.  Any company using Khronos trademarks in association with a specific product needs to be an Adopter - as the Adopters agreement contains the trademark license.

However - if a company is acting purely as a subcontractor to another Adopter and is willing to forgo any rights to use the marks in their own right then that company may apply for a fee waiver as a subcontractor.

Is there a fee for becoming an Adopter, other than the conformance fees paid for each API?

The conformance fee per API is the only payment due.  The conformance fee enables an unlimited number of submissions for that version of the specification.

Does a company have to be an Adopter to get access to Khronos conformance test sources? If not, what are the requirements for getting the right to utilize the conformance tests?

Any company using the Khronos Conformance tests to test products have to become Adopters through executing the Adopters Agreement.  This is necessary as the Adopters Agreement contains the source code license to the conformance tests for this purpose.

If a company buys a conformant product from a Khronos Adopter to deploy in their own product(s), do they have to be a paid adopter and also have passed conformance tests in order to use the relevant Khronos marks and claims of conformance?

Even though a piece of IP passes conformance, an SoC product implementing that IP does not inherit the conformance. Alterations in CPU config, memory system, target resolution etc. are potential variables which could cause a previously conformant product to fail conformance. Therefore SoC’s designs containing IP, with or without previous conformance filings must still file for conformance for that SoC implementation.

We plan on using a Conformance Test to test our phone. To do it, we would like to hand the Conformance Test source code to a subcontract company and let them make the test environment. Is this allowed and what is the procedure?

It is allowable for Member Adopter Company to provide a subcontractor company the conformance test source code so that subcontractor may test Adopter Member Company’s product(s) as long as the agreement between Member Adopter Company and the subcontractor preserves Khronos Group’s rights/NDA as provided in the Membership and Adopter documents.

SGI still has the trademark rights of OpenGL. Is the Khronos Group allowed to use this trademark with the permission of SGI?

Yes. The OpenGL trademark agreement is informal. The Khronos Group are in discussions with SGI to allow Khronos run an OpenGL Conformance program.

What is the relationship between SGI and Khronos Group?

SGI is not a member of the Khronos Group. Khronos licenses the OpenGL ES trademark from SGI. Khronos is authorized to run the OpenGL ES adopter program.

Is an OpenGL ES adopter required to comply with OpenGL licensing when they have an OpenGL ES conformant product?

No.

How does Khronos Group set the Adopter Fees?

The adopter fee is set by the individual workgroups and then approved by the Khronos board of promoters at the time the conformance test becomes available. For most of the Khronos APIs the adopter fee is currently $15,000 with a $5000 discount for paid Khronos Members. (Promoter or Contributor level membership, price subject to change). The adopter fee is a one-time charge per version of the API and allows adopting company unlimited conformance test submissions of products for certification for the life of the API.

Additional information can be found on the Khronos Adopters page.

We are looking forward to implementing OpenMAX compliance of codecs. Will the implementers get Khronos SDKs? If so please provide me the necessary directions.

OpenMAX has 3 levels of APIs, with separate specifications: OpenMAX AL, OpenMAX IL and OpenMAX DL. Referring to a codec implementation, I suspect the specification you would like to implement is OpenMAX IL.

There is currently no SDK available for OpenMAX IL. An open source implementation called Bellagio exist on SourceForge, but this implementation is not maintained by Khronos and does not provide you with any guarantee your components will be conformant with the OpenMAX IL specification. As the original work (Bellagio) has not been tested for conformance, any derivative work based on it, unless submitted for conformance testing as a complete work, could not be declared conformant either as you cannot guarantee that the interface for the codec was conformant in the first place.

The correct way forward to ensure conformance would be to sign the Khronos Adopters Agreement, pay the associated Conformance Testing Fees, then access and run the Conformance Test associated with the specification. You will find all the necessary information on the Khronos adopter page.

The chip we want to certify as conformant uses a core that we know to be conformant: is it possible to submit a conformance test result package for the core itself and have all chips using that core be covered under the one test?

From section A8 of the Conformance Process Document, any company can submit results for any implementation they like, and that submission will cover any products that fall into the criteria below:

“Implementations claimed as Conformant Products must be similar to the Conformant Implementation in the following ways:
. the identical rendering pipeline - i.e. identical binaries and/or accelerator data path to the display, or if a JIT compiler is used to generate binaries then the use of the identical JIT compiler binary, or new versions of the binaries and/or accelerator data path or JIT compiler binary that do not cause any previously passing test to fail; . the same major version of the same OS that uses substantially similar display functionality or minor version updates to the OS that do not cause any previously passing test to fail; . the identical set, or a subset, of supported configs. Different display resolutions are permitted.”


So - Yes, the Adopter Company can submit results for a core, or a chip - and the use of the mark will cover the products that are similar according to the above rules.

Can we get a membership which grants us access the conformance suite for OpenGL or any other API and allows us to make requests for software limitations or defects we find?

The Khronos contributor membership allows members to participate in all Khronos working groups including OpenGL. Members have the ability to participate and monitor progress of projects as well as the opportunity for input as related to limitations, bugs, defects, and the opportunity to participate in the ongoing evolution of the specification.

How are your licenses distributed?

The Khronos Conformance Test Source License Agreement (CTSLA) enables members to cooperate in building conformance tests – the license states that any modifications to the tests would be passed back to Khronos.

Can we get a membership to use code within our company, and not be involved in submitting code back to Khronos?

Khronos Ratified specifications are publicly available on the Khronos Web-site.  If your company wishes to use Khronos trademarks for conformant implementations of APIs, then the Adopters’ Agreement, along with applicable payment, provides access to the testing procedure and provides a trademark license.

We would like to know what membership will cost to obtain OpenVG and OpenGL, with the exact same type of membership?

The Khronos membership agreement includes a Conformance Test Source License Agreement (CTSLA). Members that have not excluded themselves from the CTSLA, have access to the conformance test source. Members wishing to claim conformance to OpenVG and OpenGL ES specifications would be required to execute the adopters agreement and pay the applicable fee for each API.

Current Adopter fees are available here: http://www.khronos.org/adopters/

If we decide to enter the conformance test process, does it require our SDK, and our Demo Board?

You do not need to submit your SDK or demo board-only the conformance test results for peer review.

If we have fail a conformance test result, how much is the re-test fee ?

Khronos conformance test submission fee is only paid once per API version. Therefore, if a test fails, you may re-submit unlimited conformance test results for that API with no additional fee.

If we decide to enter the conformance test process, how long will it take for the test?

Typically, the conformance test result peer review is 30 days. Please see conformance test procedure documents for more information.

There is one issue that our attorney raised with the section 4.3 of the Members Agreement that we would like to address.

The full question:
“The Source Package distributed under the Source License is subject to the confidentiality provisions of the Base Agreement.  As already noted, that agreement appears to preclude the use of the Source Package to do conformance testing, which is an obvious oversight by Khronos.  In addition, however, the same portion of the Base Agreement limits disclosure of confidential information to employees, on a need to know basis.  This means that it is not permitted to show any of the Conformance Testing Source Package to any subcontractors doing software coding work on this project.”

Could you please confirm that it is NOT Khronos intent to preclude the use of the Source Package to do conformance testing as it might be construed from Section 4.3 of the Membership Agreement?

The Answer:
It is NOT Khronos’ intent to preclude the use of the Source Package to do conformance testing as it might be construed from Section 4.3 of the Membership Agreement.
Section 4.2 states:  “Signatory may use Confidential Information in any Khronos-related activities.”

On the matter of subcontractors, subcontractor access is NOT automatically granted - but we do have a provision where a bona fide subcontractor can execute the Conformance Source License with no fee if approved by the Board.

Can we access the Conformance Test Package (CTP) before the actual payment? In the Khronos Adopter's Agreement, it says the total due should be paid prior to getting the CTP.

Conformance test submission fee payment must be received before conformance test results may be posted for review. If you would like an invoice for Conformance Testing, please follow the directions on our Adopters page. We will return invoice promptly for your review.

We are a Member of Khronos Group and have an Adopter Agreement for OpenGL ES. Our OpenVG team wants to access an OpenVG Conformance Package before the submission of actual Conformance Test. Is it possible to access the OpenVG Conformance Package and do we need an Adopter Agreement for OpenVG additionally?

Yes, as Khronos member you can get access to the Conformance Kit before paying for submission.

The only condition is signing of the Khronos Conformance Test Source License Agreement (CTSLA) by your company which is required only once, so quite likely it is in place already. If so, you should be able to get the test package from the Subversion repository right away.

This will give you access to the entire Conformance Test Suite (CTS). You can run all test cases internally and make sure that your implementation passes them. This isn’t equivalent to submission of your product for conformance.

If you don’t have access, please work with .(JavaScript must be enabled to view this email address) to put the Agreement in place.

What is the policy about the payment for a Conformance Test? In the Khronos Adopter's Agreement, it says the total dues should be paid prior to getting the Conformance Test Package (CTP). Can we access the CTP before the actual payment?

Conformance test submission fee payment must be received before you may download the official conformance test package and before you can submit your results for review. If you would like an invoice to become an adopter for any of our APIs, please review the Adopter pages.

We, are working with a Khronos Adopter as a subcontractor on for a Khronos Technology. This Adopter has used the sample source code, customized it and distributed to us as a source code and a binary code. We need to integrate this with our own software modules, and then distribute to our customers after we compile them together. What are the limitations on redistribution?

The Adopters Agreement for Khronos Technologies includes a license for the source to the tests.

The Test Source may ONLY be used to port and run the tests - this code may not be re-distributed.

Any Open Source sample source wrappers or implementations may be distributed freely as long as the copyright notices in the software are met.

How many conformance tests can I submit for a particular technology?

Your conformance test fee lets you make an unlimited number of Submissions for any number of Conformant Products using any version of the technology up to and including the latest version of the Tests included in the current Adopters Package at the time of execution of the Adopters Agreement, at your selected Fee.

What are the currently available conformance tests and fees?
All memberships levels and pricing are available from our Become a Member Information page. Currently available conformance tests are available here.
How much does it cost to become an Adopter Member and submit Conformance Tests for a particular Khronos technology?
All memberships levels and pricing are available from our Become a Member Information page.
How do I become a Khronos Adopting Member and submit my product to the Conformance Test Process

To understand the Adopters program and conformance testing, please review the Adopters web page. Be sure to review these documents:

  1. Khronos Adopters Agreement
  2. Khronos Group Conformance Test Process Procedures
  3. Khronos Group Conformance Test Process Presentation
What are the Khronos Conformance Tests and why do I want to submit my product?

Conformance Testing is performed to ensure that a product complies with the Khronos technology standards.  Products that pass the Khronos Conformance Tests are certified as compliant with the standard and may use the technology logo to advertise and promote their products.  This insures consumers with a guaranteed level of performance and thus helps product developers with a way to differentiate and validate their offerings.

Conformance Test will be available for all of the Khronos technologies.  More information is available on the Adopters web page.

Licensing and Trademarks

Please provide more information about section 5.3 of the IP Rights Policy located in the Khronos Membership Agreement

Clause 5.3 is to encourage members with knowledge of Necessary Claims to file an IP Disclosure for the information of the working group -  though that IP will not be licensed in any case because of the Working Group Exclusion certificate.
  Furthermore:

     
  • it is advantageous to a working group if that member has actual knowledge of essential claims that will not be licensed under the Khronos standard reciprocal license, that the working group be notified of that fact through an IP Disclosure Certificate.  Hence the existence of Clause 5.3.
  •  
  • all Khronos Confidential information for all working groups is made accessible to all members, regardless of any working group exclusions, at least in part for the above reason
  •  
  • however - as per section 3.3 of Attachment A - a member is NOT obligated to proactively search their IP portfolios:  "Members are not required to conduct searches of their patent portfolios, nor are they required to disclose Necessary Patent Claims of other Members or other third party patents"
  •  
  • So, a member that excludes from particular working group is under no obligation to monitor any activities or drafts from those excluded working groups, nor to check drafts from the excluded working groups against their IP Portfolio.  And in any case, the excluded member will not have any IP Licensing obligations for any ratified specifications from an excluded working group.

 

In the case of reciprocal licenses, how often do member companies submit exclusion certificates and disclosure certificates? It would seem that if these are provided in large quantities by the large companies that comprise your membership, there would be many exclusions on licensing that would be difficult to sort out for other member companies interested in adopting the standard.

Yes – however the good news is that IP Disclosure (exclusion) certificates are used extremely rarely. In the whole history of Khronos, over 10 years with 14 active working groups each Ratifying multiple specifications, only 5 IP Disclosure Certificates have ever been issued.

There are a number of reasons for this - and we are happy to discuss any of this in more detail:

  • the Khronos members, in general, participate in Khronos because of a belief in the power of royalty-free standards to grow market opportunities;
  • the Khronos IP framework takes great care to define essential IP to very effectively protect members IP (while providing essential protection for the specifications in the industry) so members that participate in the reciprocal license are not “losing control” of their IP in any way;
  • the license is reciprocal – so any company licensing its essential IP – is in exchange receiving a license from 100 other member companies – and this is most often an attractive proposition.
It would appear that specific patent claims would have to be submitted contemporaneously with the submission of a contribution of patented technology for the purpose of consideration and adoption for inclusion in a spec. Is this reading correct?

The Khronos IP framework is constructed so that the default approach to IP (and the one used in the overwhelming majority of cases in practice) is that there is NO DISCLOSURE NECESSARY (sec 3.2 of Attachment A – the IP Rights Policy) for essential IP that can be licensed under the default reciprocal license. The IP Rights Policy provides for two types of explicit IP Disclosure:

  • IP Disclosure for IP that will NOT be licensed in relation to relation to a draft specification (sec A.3.3);
  • Reciprocal License Certificate to explicitly offer IP under license (perhaps to be used to reassure a working group to integrate patented technology) (sec A.6).
How does Khronos treat information that a member company submits about how that company uses OpenGL, and why that company may want to add (or prevent subtraction of) certain features? Is it treated as confidential information, and if so, is the company deemed to have waived confidentiality if the information is used in the development of the standard?

All information generated in association with Khronos business and circulated within Khronos is confidential (sec 4.1 of the membership agreement). If a contribution from a member is directly incorporated into a specification then that confidentiality is waived on Ratification (last sentence of sec 4.1). However, general comments and feedback related to a specification and not directly integrated into the specification itself would remain confidential.

SGI still has the trademark rights of OpenGL. Is the Khronos Group allowed to use this trademark with the permission of SGI?

Yes. The OpenGL trademark agreement is informal. The Khronos Group are in discussions with SGI to allow Khronos run an OpenGL Conformance program.

Is SGI a Khronos Group member?

No.

What is the relationship between SGI and Khronos Group?

SGI is not a member of the Khronos Group. Khronos licenses the OpenGL ES trademark from SGI. Khronos is authorized to run the OpenGL ES adopter program.

Can we get a membership to use code within our company, and not be involved in submitting code back to Khronos?

Khronos Ratified specifications are publicly available on the Khronos Web-site.  If your company wishes to use Khronos trademarks for conformant implementations of APIs, then the Adopters’ Agreement, along with applicable payment, provides access to the testing procedure and provides a trademark license.

Can our customer use the patents related to the Khronos technologies under a royalty-free license?

There are two ways which an individual or company can make use of the Khronos Technologies:

  1. Implementers - may create and deliver a product using the publicly released specifications and patents related to the Khronos technologies under a royalty-free license. But they cannot claim the product is “compliant” or if it is a software or hardware engine, they cannot advertise it using technology logos or trademarks. The Implementor option carries no cost or license fees.
  2. Adopters -  can download and run the conformance tests and if the implementation passes, they can advertise and promote the product as being compliant; using the technology logos and trademarks under a royalty-free license.
Our group is developing a graphics chip which complies with one of the public Khronos technologies. We would like to sell these chips to our customer. Can our customer use technology logos and trademarks under a royalty-free license?

Only if that product has been submitted to the Khronos Conformance Test Process.  Any product must be submitted to the Conformance Process before the technology trademark can be used on that product (fee schedules can be found here).  Any company can become an Adopter Member and submit the test results for a product.  Once passed - any company that uses that product, may use the technology trademark when related to the product.

Member Site Access and Resources

Is SGI a Khronos Group member?

No.

How can a member be considered for demo or exhibit opportunities with Khronos?

When we have demo and speaking opportunities, we send out an “all hands call for participation” email to the “Khronos General” email list, asking for any interested members to contact the Khronos marketing team or the Work Group chair of the API that interests them.

After the general announcement, we then only email directly to the Work Groups (WGs) or the Work Group Chairs (WGCs). The WGCs will then seek out speakers and demoers from active participants. If you don’t actively participate in Work Groups, you will still see the opportunities over email at least once. You can find opportunities on our members events page and public events page.

We strongly suggest that both your technical and marketing associates sign up to the specific Work Groups that interest your company the most. Also, make sure you do not unsubscribe from the Khronos General mailing list in your account profile.

I was looking at the Khronos website member list and found out our company name is missing on the contributor list. Could you tell me who should I talk with to add our company logo and what the process is?

Please send to the Khronos Webmaster:

Your company logo: both a web logo (jpg, png or gif) and a print quality logo (vector eps or hi-res jpg or png)

A description of your company’s specific interests in technology and markets that relate to Khronos Group APIs, not your company’s ‘standard boilerplate.’
(An example: Digital Media Professionals Inc. is focusing on developing very high performance graphics processor based on revolutionary physical model based rendering which is covering wide range of graphics applications including high end gaming to embedded solutions. DMP will provide support for the OpenGL ES programming interface in our next generation visualization products.)

The Khronos IPR policy states that contributions may not be withdrawn once they are “accepted” by Khronos.  When does such acceptance occur?

The phrase “cannot be withdrawn once accepted” as rather vague as it is intended to communicate the spirit of contributions. Contributions should not be made unless the intention is for them to be covered by the IP framework so as to minimize disruption to the working group.

The legal framework for contributions is:

     
  • a reciprocal license is granted for essential claims, for any contribution, at the Board’s Ratification of a draft specification that incorporates that contribution
  •  
  • prior to Ratification, any member may issue an IP Disclosure Certificate to exclude specific essential claims from the reciprocal license - regardless of whether those claims are associated with a explicit contribution from the member or not

Logistically:

     
  • if a member makes verbal or written contributions that are never incorporated into a draft specification - there is no licensing obligation
  •  
  • if a member sees any contributions incorporated into a draft that would require the member to issue an IP Disclosure Certificate - the member should inform the working group as quickly as possible at a high-level without reference to specific claims
  •  
  • specific IP claims should never be disclosed or discussed outside a formally issued IP disclosure certificate - or through using the IP Committee Process
  •  
  • the working group will make the decision whether the draft specification should be updated to remove the contribution from the draft specification
  •  
  • if the contribution is not removed - the member may issue an IP Disclosure Certificate to exclude any essential claims from the reciprocal license at Ratification of the draft
We would like to know what membership will cost to obtain OpenVG and OpenGL, with the exact same type of membership?

The Khronos membership agreement includes a Conformance Test Source License Agreement (CTSLA). Members that have not excluded themselves from the CTSLA, have access to the conformance test source. Members wishing to claim conformance to OpenVG and OpenGL ES specifications would be required to execute the adopters agreement and pay the applicable fee for each API.

Current Adopter fees are available here: http://www.khronos.org/adopters/

Is there a membership that allows us to see and customize Khronos code, to accommodate our testing and API usage?

We have two Khronos membership levels, Contributor and Promoter. Both membership levels allow access to all development activity. Members are able to participate in any and all work groups and public events that are of interest. Member companies may exclude themselves from certain API activity simply by executing a document that allows a company to exclude itself from IP discussions on that topic. Members have access to all draft specs in progress, a vote at any working groups that you elect to participate in, a grant of the reciprocal IP license to ratified specifications, and access to the Khronos Conformance Test source for all its APIs for development purposes under the Conforomance Test Source License Agreement (CTSLA).

We are a Member of Khronos Group and have an Adopter Agreement for OpenGL ES. Our OpenVG team wants to access an OpenVG Conformance Package before the submission of actual Conformance Test. Is it possible to access the OpenVG Conformance Package and do we need an Adopter Agreement for OpenVG additionally?

Yes, as Khronos member you can get access to the Conformance Kit before paying for submission.

The only condition is signing of the Khronos Conformance Test Source License Agreement (CTSLA) by your company which is required only once, so quite likely it is in place already. If so, you should be able to get the test package from the Subversion repository right away.

This will give you access to the entire Conformance Test Suite (CTS). You can run all test cases internally and make sure that your implementation passes them. This isn’t equivalent to submission of your product for conformance.

If you don’t have access, please work with .(JavaScript must be enabled to view this email address) to put the Agreement in place.

I'm new to Khronos and want to catch up on the recent work group activity. What should I do?

The best way to catch up is to review the working group email lists archives for the technologies in which you have interest.

My company is a Khronos Member. Can I sign up for a work group email list using my personal email (Yahoo, Google etc) account?

No, to participate in the Khronos Working Group email lists, you must use an email account with a domain name that matches your parent company.  We require this for security reasons and maintain a very strict policy.  If you are a subcontractor to a Khronos members, you should try to obtain an email address from the Khronos Member company.

I want to enter a bug report into Bugzilla

Khronos members have access to the Members Only Bugzilla.  This information is described on in the Members Only area. To enter a bug report, simply create an account and submit your report.

I am logged into the Members Only area of the website and am able to view the Khronos Members Only Wiki, but I can't edit anything. It says that I need to log in?

The Wiki uses its own login system. Once you have reached the Wiki in the Members Only area, you can create a Wiki account that will let you edit any page on the Wiki.

How do I get access to the Members Only areas of the website?

If your company is a Khronos Member and membership dues are current, you can sign up as a company representative at http://www.khronos.org/members/signup.  Your signup will usually be validated and approved within 48-72hr.  Note: Your email address must match the domain of your parent company.

If your company is not yet a member, then they need to complete a membership agreement and pay yearly dues before any representatives will be able to access the Members Only areas of the website.

My company is a Khronos Member. I am trying to access the SVN, but when I go to a particular folder and enter my username and password, I get an "access denied" error message. How do I get access.

Each SVN repositories has a unique set of permissions.  Some repositories and folders allow access to any registered Khronos member.  Other repositories related to the Conformance Tests for that technology, require that the member company has signed the Khronos Conformance Test Development Source Agreement.  Your company will need to sign this document for you to get access.  (Note:  the 2007 membership agreement has the CTDSA incorporated into the membership agreement, so new companies will have automatic access unless they specifically decline the terms of the CTDSA).

General Membership & Billing

How can my company participate in Khronos Group activities?

There are many ways to get involved in Khronos Group activity!

If your company is not yet active with the Khronos Group you can apply for Contributor, Academic Contributor, Promoter or Adopter membership, please follow the steps below:

  • Adopters participate in the Conformance Test Process for particular Khronos Technologies.
  • Academic Contributor Members (for accredited academic institutions only)  have full specification working group participation at reduced membership dues but without working group voting rights.
  • Contributor Members have full specification working group participation and voting rights, and generous marketing benefits.
  • Promoter Members act as the “Board of Directors” to set the direction of the Group, with final specification ratification voting rights and the right to designate a Director to the Board. Applications to this class of membership must be approved by the Khronos Board of Directors.

See Membership Benefits and the Member Agreement (154k pdf) for a complete list of benefits and obligations for each class of membership.

 

safety