This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.Questions on this system should be addressed to the Conformance Statement manager at The Open Group.
Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.
A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.
Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.
Question 1: What connection mechanisms does your API support?
Response
Rationale
The connection mechanisms supported by a single API may include TCP/IP, DECnet or others. It is useful to know which connection mechanisms are supported to determine which conformant X/Open Window Management displays can be used with a particular API.
Reference
CAE Specification, X/Open Window Management: Xlib - C Language Binding, Section 3.1, Opening the Display.
Question 2: Are you aware of any additions or omissions from the list of Xlib functions with respect to your API implementation, as detailed in Appendix A (pp.607-617) of the referenced CAE Specification? If so, please list them below.
List the xlib bindings and whether they are additions or omissions.
Are you aware of any deviations from the specified syntax and/or semantics for the Xlib functions with respect to your API implementation, as detailed in Appendix A (pp.607-617) of the referenced CAE Specification? If so, please list them below. Question 4: Are you aware of any Xlib functions with respect to your API implementation, as detailed in Appendix A (pp.607-617) of the referenced CAE Specification, that emit protocol requests that are not conformant with their associated semantics and/or encoding as defined in the CAE Specification, X Window System Protocol? If so, please list them below. Response Rationale To ensure interoperability and the ability to reproduce the test suite results, the vendor of the API must commit to identify any deviations (either additions or omissions) from the CAE Specification. Reference CAE Specification, X/Open Window Management: Xlib - C Language Binding, Section 3.1, Opening the Display. 2. Appendix This appendix contains additional, explanatory material that was provided by the vendor. Copyright © All rights reserved. 3. Change History DateNameComment New
Question 4: Are you aware of any Xlib functions with respect to your API implementation, as detailed in Appendix A (pp.607-617) of the referenced CAE Specification, that emit protocol requests that are not conformant with their associated semantics and/or encoding as defined in the CAE Specification, X Window System Protocol? If so, please list them below.
To ensure interoperability and the ability to reproduce the test suite results, the vendor of the API must commit to identify any deviations (either additions or omissions) from the CAE Specification.
Copyright © All rights reserved.