You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.
The reciprocity language in current JSPA provides powerful protection. In effect, it allows a Spec lead to outbound-license the inbound patent rights associated with a specification such that asserting patents against a compatible implementation of a JSR would become impractical for any company making use of the JSR technology.
Given the prevalent use of some JSRs this provides all users of those JSRs with powerful protection against patent attacks. E.g. very few companies exist that can afford to stop making any use of Java SE or Java EE.
The question here is: Should we extend this powerful reciprocity protection across JSRs, such that IP rights involved in ANY JSR technology depends on the licensee's willingness to provide reasonable license terms to patents the licensee holds on ANY JSR.
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user gtene:
The reciprocity language in current JSPA provides powerful protection. In effect, it allows a Spec lead to outbound-license the inbound patent rights associated with a specification such that asserting patents against a compatible implementation of a JSR would become impractical for any company making use of the JSR technology.
Given the prevalent use of some JSRs this provides all users of those JSRs with powerful protection against patent attacks. E.g. very few companies exist that can afford to stop making any use of Java SE or Java EE.
The question here is: Should we extend this powerful reciprocity protection across JSRs, such that IP rights involved in ANY JSR technology depends on the licensee's willingness to provide reasonable license terms to patents the licensee holds on ANY JSR.
The text was updated successfully, but these errors were encountered: