[jakarta.ee-spec.committee] Requirements for claims of compatibility

[Scott Stark <sstark@xxxxxxxxxx>]

The last topic we were on in today’s TCK process call was the issue of what steps needed to be followed in order to be able to claim compatibility. 

https://www.eclipse.org/legal/tck.php

1. A Product will be deemed to be “compatible” with the Specification if it fully and completely meets and satisfies all requirements of the TCK. 
2. Before any claim of compatibility (or any similar claim suggesting compatibility) is made based on the TCK, the testing party must:
   1. use the TCK to demonstrate that the Product fully and completely meets and satisfies all requirements of the TCK; 
   2. make TCK test results showing full and complete satisfaction of all requirements of the TCK publicly available on the testing party’s website and send a link to such test results to Eclipse at tck@xxxxxxxxxxx; and
   3. comply with any requirements stated in the Specification with regard to subsetting, supersetting, modifying or extending the Specification in any Product claimed to be compatible with the Specification.

In the current TCK process draft we are stating that one needs to make a certification request that requires a number of items, one of which is a link to the test results. After a certification request is approved by the corresponding specification project, it is stated that one email the tck@xxxxxxxxxxx list with the certification request issue, which would transitively include the TCK test results.

The point of contention was the order in which things had to happen. Some were arguing that we have no ability to avoid a testing party sending their results to tck@xxxxxxxxxxx and then being able to claim compatibility. Others were arguing that the TCK requirements could be a forcing function that ensured that there was a certification request issue opened and approved before one could send a message to the tck@xxxxxxxxxxx list.

Let’s continue the discussion as we need to wrap up the TCK process doc.