Add LicenseRef-doubleopen-jsr-356-websocket-spec #81
Conversation
|
@Toniprni What's your view (or others') regarding whether this license includes an obligation to include in notice file? In my view, it does not. The right to distribute the spec document itself is quite difficult to read from there, but it is there - within parenthesis towards the end of section 2. Other than that there is a requirement to not modify the spec, nor the software implementing it. Otherwise ok. I'm classifying it as proprietary free. By the way, this is an example of a repeating license that does not have a scancode naming. And I wonder what is the authoritative source for this license: I used this one, being license version 1.0 https://github.com/apache/cxf/blob/3.4.x-fixes/distribution/src/main/release/samples/jax_rs/search/src/main/resources/JavaWebSocketAPI_1.0_Final.pdf, whereas Oracle has the license version 1.1, https://download.oracle.com/otndocs/jcp/websocket-1_1-mrel-spec/license.html both of which apply to final spec version 1.0. Content-wise for our license classification reasons these are the same. While Oracle is the right holder here, the version 1.0 was included in the package I was reviewing. |
|
@willebra Should the WebSocket Specification license also have the property:patent-clause (see section 4 of the licence)? I agree, no need for include-in-notice-file. |
No description provided.