The Open Brand -- Problem Reporting and Interpretations System
2. Submitting Problem Reports
The Problem Report Submission page allows a user to submit a problem report. The report information is collected using a web form, and then forwarded into the Problem Reporting system. The required review group will then be notified of the new report, so that a review can begin. The review group will be the Test Suite Maintenance Authority (TSMA) for reports classified as Test Suite problems (TSDs), the Certification Authority (CA) for reports classified as Certification System problems (CSDs), or the Specification Authority (SA) for all other reports. In all cases the SA and CA will be notified of the submission of the new problem report so that they can monitor it.
When filling in the forms it is important to give as much information as possible. Only a few fields are optional, and these depend on the classification that is given to the report as it is created. If any mandatory fields are left blank the form will be returned with a message explaining what is missing, and a request to add the missing details. The fields are shown below.
2.1 Confidential Information
The confidential fields are only be visible to members of the Certification Authority, and are not visible to other users of the Problem Reporting system.
Enter your name here, or the name of a contact person if you are submitting on behalf of a group of people.
Enter your email address here, or a contact email address if you are submitting on behalf of a group of people.
Enter the name of the company or organization that you represent.
Enter a telephone number which can be used in case of urgent issues with the resolution of your problem report.
You may enter a reference number if you want, which will be quoted in correspondence relating to the problem report.
If you classify your problem as a Test Suite Deficiency, then please enter the name and version of the product that you were testing when the problem in the test suite became evident.
If you classify your problem as a Test Suite Deficiency, then please enter some details of the environment in which the product was running when the test suite problem became evident. E.g. operating system, Hardware, etc.
2.2 Public Information
The following information will be available for all users of the problem reporting system regardless of privilege.
Please enter the classification of the problem you are raising. The options are explained in the table below.
Problem Classifications Classification Description Test Suite Deficiency (TSD) An error in a test suite, which is causing it to produce an incorrect result code that impacts certification. Certification System Problem (CSD) An error in the certification system, which is inhibiting the certification process. The certification system includes both the certification process and information systems provided to implement certification. Specification Problem (PIN or TIN) There is ambiguous text in the specification, and the test suite or certification system have interpreted the text in a different way to the way it has been interpreted during the development of your product. These are also known as Grey Areas. Minor System Fault (MSF) This is an implementation error, demonstrated to be of a minor nature, with negligible impact on interoperability or portability. The Open Group at its sole discretion may issue a temporary waiver for this case to allow Product Registration to proceed.
The name of the Certification Program that includes the test suite, certification system or specification to which your problem report refers.
Provide a summary of the problem, containing key words. This summary is used in table listings of problem reports returned by searches, for example when another user of the Problem Reporting system is checking whether the problem they are encountering has already been reported. Please do not include any information that would identify you, your company or your product.
Linked Problem Reports
If you think that your problem relates to any existing problem report in the Problem Reporting system, provide the relevant report number(s) here. This will allow cross referencing between reports for reviewers and other users of the system. If you enter multiple problem report numbers, please enter them as a comma separated list.
Please be aware that you should only enter a problem report number in this field if you are aware of a related problem report. If no related problem report exists, or if you do not wish to enter a related problem report number, please leave this field blank.
Enter a full description of the problem you are encountering. Your description should be detailed enough to enable reviewers to agree or disagree with your assessment during the resolution process. It should also be presented in a way that will enable other users of the Problem Reporting system to identify whether they are seeing the same problem, when they search resolved problem reports. Please do not include any information that would identify you, your company or your product.
Provide the name and version of the Test Suite that was in use when the problem was encountered. In general, test suite output should always be provided unless its a problem that occurs independent of the test suite, for example a specification problem for which there is no relevant test.
Provide the full name of the test and test case that is showing the problem. Ensure the name is not ambiguous. You may include multiple test cases if required. Example full test identities are:
- A single test: POSIX.os/files/readdir/T.readdir.2
- A range of tests: POSIX.os/files/readdir/T.readdir.2,3,6-9
If the problem you are not reporting does not include test suite output, this field is optional.
If your problem is identified in the test journal output, you should enter the relevant fragment of test output here. This will be used by the reviewers in resolving your problem, and by future users of the Problem Reporting system when searching for existing known problems.
Provide the name and version of the Specification that contains the problem being reported, or which contains the references that justify the behaviour of your product. If you are not reporting a specification problem, this field is optional.
Location in Specification
Provide a reference to the location in the specification to which your problem or justification refers.
Contact the Certification Authority