Java Advanced Imaging TCK

Print-friendly Version

At this time, the TCK for the Java Advanced Imaging 1.1 API is available only by the licensing of the Base Porting Kit (BPK). The BPK may be obtained from your Sun sales representative, or send email to the Java Advanced Imaging API product marketing manager. The current cost to license this kit is $25000.

The BPK includes:

• Interim code drops,
• Access to the Test Compatibility Kit (TCK),
• Documentation such as white papers, and
• Java Partner web site access.

Please note that this license is required only if you need the source code to the reference implemenation or TCK, or the binary of the TCK. The BPK is not necessary for you to use the Java Advanced Imaging API, or to distribute products which use the Java Advanced Imaging API.

Java Advanced Imaging API TCK First-level Appeals Process:

This section documents the first-level TCK appeals process. This is here for the convenience of those interested in licensing the BPK and obtaining the TCK binary and source. It shows how challenges to the accuracy of the TCK and its interpretation of the specification are handled.

• Who can make challenges to the TCK?

  Any licensee of the technology.

• What challenges to the TCK may be submitted?

  Individual or related tests may be challenged for reasons such as:

  • Test is faulty (for example, program logic errors)
  • Specification item covered by the test is ambiguous
  • Test does not match the specification
  • Test assumes unreasonable hardware and/or software requirements

• How are challenges to the TCK submitted?

  Challenges must be written and sent to the Maintenance Lead or his designee contesting the validity of one or a related set of TCK tests. A detailed justification for why each test should be invalidated must be included with the challenge. Such challenges should be sent to jai-spec-comments@sun.com.

• How and by whom are challenges addressed?

  The process is managed by the Maintenance Lead or his designee as follows: The Maintenance Lead evaluates the challenge and prepares a response. If the appeal is incomplete or unclear, it is returned to the Java Community Member for correction. The Maintenance Lead will check with the test developers (if possible) to review the purpose and validity of the test before writing the response. The Maintenance Lead will also attempt to complete the response within 5 business days. If this is not possible, the Maintenance Lead will tell the Java Community Member when it will be completed (maximum 10 business days from receipt of challenge).

  If a challenge is identical to a previously rejected challenge (that is, same test and justification), the Maintenance Lead will not be required to escalate it to the TIC, but will send the previous TIC response to the Java Community Member. Challenge and response are sent by the Maintenance Lead to the TIC for evaluation.

  If a challenge is clearly correct and a test must be invalidated, the Maintenance Lead may choose to alert the TIC of this fact, and wait 3 working days for any disagreement before invalidating the test.

  The Technical Interpretations Committee (TIC) will be chosen from among the following groups: the Expert Group, other Java Community Member organizations, TCK test developers, and academia. The TIC is run by the Maintenance Lead and is chartered to review all challenges to the TCK by any Java Community Member. The TIC will be comprised of individuals who are technology experts and familiar with the JAI specification, the RI, and the TCK.

  The TIC will make a decision of test validity or invalidity within 10 working days of receipt of the challenge and its response by the Maintenance Lead. If a challenged test has been adopted from another TCK, the test must also be reviewed by its respective TIC or Maintenance Lead. In this case, another 5 working days may be added to the response period for each additional TCK appeals process involved in the decision. All decisions must be documented with an explanation of why test validity was maintained or rejected.

• How are accepted changes to the TCK managed?

  The Java Community Member is informed of the decision and proceeds accordingly. If the test challenge is approved and one or more tests are invalidated, the Maintenance Lead removes the test(s) from the Test Suite or invalidates the test(s) so as to exclude them as part of the testing requirements for all implementors. If the test appeal is rejected, the Java Community Member may choose to escalate the decision to the Java Community Process Executive Committe. In addition, an alternate test may be developed by the TIC for use by the test challenger. Such a test would be deemed equivalent to the original test for meeting the testing requirements.