Issue Details (XML | Word | Printable)

Key: WEBSOCKET_SPEC-1
Type: Task Task
Status: Closed Closed
Resolution: Invalid
Priority: Major Major
Assignee: dannycoward
Reporter: starksm64
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
websocket-spec

TCK license conflicts with JCP 2.8 section 1.4

Created: 02/Mar/12 06:56 AM   Updated: 30/Oct/12 08:16 PM   Resolved: 30/Oct/12 08:16 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. PDF File SATCK JSR 356 JavaAPI for Web Sockets 1.0 redline 2 29 12.pdf (569 kB) 02/Mar/12 07:04 AM - starksm64


Tags:
Participants: dannycoward and starksm64


 Description  « Hide

There are several statements in the TCK license that appear to conflict with the following requirement from JCP 2.8:

"TCK license terms must permit implementors to freely and publicly discuss the testing process and detailed TCK test results with all interested parties."



starksm64 added a comment - 02/Mar/12 07:09 AM

Items that continue be in conflict with the requirement include the following from section 2.1(b) of the attached TCK redline document:

(iv) develop other test suites intended to validate compatibility with the Java Specification(s) to which the TCK(s) licensed hereunder corresponds; or

(vi) use the TCK to make claims of comparative compatibility (for example, a claim either that a Product is “90% compatible” or that the Product is “more compatible” than another implementation of the same Java Specification).


dannycoward added a comment - 30/Oct/12 08:16 PM

This is the venue for tracking technical issues with the JSR 356 specification.

I am closing this issue because it isn't a technical; this is not the right venue for a discussion about the legal aspects of Oracle's TCK License.

Scott, I am going to ask you to raise this at in JCP Executive Committee directly through your representative, Mark Little.