Sun Industry Standards Source License v1.1

Also known as SISSL, Sun Industry Standards Source License 1.1, Sun Industry Standards Source License v1.1.

Commercial use: allowed
Share alike: required
Attribution: required (keep the copyright and license notices)

Compare with… Add to the compatibility check Download JSON-LD Turtle RDF/XML Text

Write this as a license text (needs an account) DALICC reads the model above and writes what it permits, requires and prohibits in plain English. Without an account, the Text download above writes the model out from the vocabulary.

Canonical URI https://dalicc.net/licenselibrary/SISSL

Permissions

Change license from the text
Charge distribution fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Notice from the text
- Share alike from the text
- Source code from the text
- Standards conformance from the text
Display from the text
Distribute from the text
Duties
- Attribution from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Notice from the text
- Share alike from the text
- Source code from the text
- Standards conformance from the text
Patent grant from the text
Present from the text
Reproduce from the text
Sublicense from the text

Prohibitions

Promote from the text

License-wide duties

This license states no duties that apply to the work as a whole.

What applies by default

The statements above are the library's reading of this license: each is marked with the sentence it rests on, or as a library convention where the text is not explicit. The statements below are the ones the DALICC reasoner supplies for acts the license says nothing about, from the default rules of the dependency graph it reasons with. Each one names the legal source it rests on. None of it is in the record.

No default rule of that graph reaches this license: it speaks about every act the rules are about.

Further terms

These are the things the license says about itself beyond the acts it permits, forbids and requires: when it ends, how long there is to put a breach right, which law governs it, and so on. A term that comes from the DALICC vocabulary links to its definition.

Cure period: 30 days
Terminates on breach: Yes

Clauses

Warranty disclaimer

ORIGINAL CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE ORIGINAL CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE ORIGINAL CODE IS WITH YOU. SHOULD ANY ORIGINAL CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY ORIGINAL CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

Limitation of liability

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF ORIGINAL CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

Additional clauses

3.1 Application of License. The Source Code version of Original Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. Your license for shipment of the Contributor Version is conditioned upon Your full compliance with this Section. The Modifications which You create must comply with all requirements set out by the Standards body in effect one hundred twenty (120) days before You ship the Contributor Version. In the event that the Modifications do not meet such requirements, You agree to publish either (i) any deviation from the Standards protocol resulting from implementation of Your Modifications and a reference implementation of Your Modifications or (ii) Your Modifications in Source Code form, and to make any such deviation and reference implementation or Modifications available to all third parties under the same terms as this license on a royalty free basis within thirty (30) days of Your first customer shipment of Your Modifications. 3.3 Distribution of Executable Versions. You may distribute Original Code in Executable and Source form only if the requirements of Sections 3.1 and 3.2 have been met for that Original Code, and if You include a notice stating that the Source Code version of the Original Code is available under the terms of this License. The notice must be conspicuously included in any notice in an Executable or Source versions, related documentation or collateral in which You describe recipients' rights relating to the Original Code. You may distribute the Executable and Source versions of Your version of the Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License. If You distribute the Executable and Source versions under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer. You hereby agree to indemnify the Initial Developer for any liability incurred by the Initial Developer as a result of any such terms You offer. 8.0 TERMINATION 8.1 This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Original Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. 8.2 In the event of termination under Section 8.1 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. 11.0 MISCELLANEOUS This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/SISSL.html
Legal code: http://www.openoffice.org/licenses/sissl_license.html
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Sun Microsystems, Inc.
Attribution name: Sun Microsystems, Inc.
SPDX identifier: SISSL on the SPDX license list
DALICC identifier: SISSL

This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.

Use this license

Everything below is generated from this record. Replace the example address with the address of your own work.

JSON sidecar

{
  "license-uri": "https://dalicc.net/licenselibrary/SISSL",
  "license-title": "Sun Industry Standards Source License v1.1",
  "spdx-id": "SISSL",
  "attribution": "Copyright (c) [year] [copyright holder]",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle

@prefix cc: <http://creativecommons.org/ns#> .

<https://example.org/my-work>
    cc:license <https://dalicc.net/licenselibrary/SISSL> .

RDF, JSON-LD

{
  "@context": {
    "cc": "http://creativecommons.org/ns#"
  },
  "@id": "https://example.org/my-work",
  "cc:license": {
    "@id": "https://dalicc.net/licenselibrary/SISSL"
  }
}

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/SISSL" rel="license">Sun Industry Standards Source License v1.1</a>.</p>

This license asks for attribution, so the credit line is part of it.

Badge

Markdown

[![License: Sun Industry Standards Source License v1.1](https://dalicc.net/license-library/SISSL/badge.svg)](https://dalicc.net/license-library/SISSL)

HTML

<a href="https://dalicc.net/license-library/SISSL"><img src="https://dalicc.net/license-library/SISSL/badge.svg" alt="License: Sun Industry Standards Source License v1.1"></a>

Review

Written from the license text by: Giray Havur
Written on: 2026-09-15
Second review: not yet done
Record changed since this review: yes (version 2, 2026-09-24)
Findings: 8 recorded, 5 applied to the record, 0 proposed

Models the Sun Industry Standards Source License, an MPL 1.1 derivative whose reciprocity is triggered not by modification as such but by a modification that departs from a named standard. The record carries the MPL 1.1 shape and quotes the standards clause verbatim. Nothing here is legal advice.

8 findings

major Rubric 3 odrl:permission applied

Section 2.1(a) grants rights "under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code", so dalicc:sublicense is a permission, and 2.1(b) grants a patent licence, so dalicc:patentGrant is a permission.
major Rubric 4 odrl:prohibition applied

The grant excludes trademark rights in as many words, so dalicc:promote is a prohibition. Section 8 has no patent retaliation limb, unlike MPL-1.1, so dalicc:patentRetaliationTermination is absent. dalicc:ChangeLicense is prohibited for the source code version.
major Rubric 5 odrl:duty applied

Section 3.1 requires that "The Source Code version of Original Code may be distributed only under the terms of this License" and, where the modifications leave the standard, that the licensee publish the deviation and a reference implementation or the modifications in source form "to all third parties under the same terms as this license on a royalty free basis". cc:ShareAlike, cc:SourceCode, cc:Notice and cc:Attribution therefore hang off odrl:distribute, odrl:modify and odrl:derive. Unlike every other member of this family SISSL has no description-of-modifications clause, so no dalicc:modificationNotice duty is written.
major Rubric 6 dalicc:additionalClauses applied

Section 3.1 is quoted in full because the trigger of the reciprocity, a departure from "all requirements set out by the Standards body in effect one hundred twenty (120) days before You ship the Contributor Version", cannot be expressed by cc:ShareAlike alone. Section 3.3, the termination clause and the applicable-law clause are quoted as well.
minor Rubric 7 cc:jurisdiction applied

The grant itself is world-wide ("a world-wide, royalty-free, non-exclusive license"), so cc:jurisdiction stays dalicc:worldwide and the applicable-law and venue clause is quoted in dalicc:additionalClauses instead of being turned into a bpicounty IRI. A choice of law is not a jurisdiction port and the library reserves cc:jurisdiction with a country for ports.
gap Rubric 8 dalicc:additionalClauses none

There is no term for a duty conditioned on conformance to an external technical standard. Proposed term: dalicc:standardsConformance, an action that a licence may require of a modified version. Termination on breach has no property either (proposed dalicc:terminatesOnBreach). Both clauses are quoted.
info Rubric 9 record none

The consistency check of app.services.composer with the dependency graph dg_default returned an empty conflict list. cc:ShareAlike is required and dalicc:ChangeLicense is prohibited, which is the combination the check expects; asserting both cc:ShareAlike and a dalicc:ChangeLicense permission would have been reported as a direct conflict.
info Rubric 10 record none

Diffed against MPL-1.1. Also compared with licensedata/licenses/SunPublicLicenseVersion10.ttl, the other Sun licence in the library; that record uses a different and older shape (duties on cc:DerivativeWorks rather than on odrl:derive) which this record does not copy.

Report an issue The review record as JSON The review checks the model against the license text. It is not legal advice.

History

This license model has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.

Version 2 current2026-09-24 Giray Havur

The changes since version 1 recorded which sentence of the text each statement rests on and named the license the record itself is published under.

View version 2 JSON-LD Turtle RDF/XML
5 changes
- changed permission dalicc:sublicense
  
  was permission dalicc:sublicense
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and"
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:standardsConformance]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:standardsConformance]
  
  Manual edit Its duty cc:ShareAlike quotes "In the event that the Modifications do not meet such requirements, You agree to publish either (i) any deviation from the Standards protocol resulting from implementation of Your Modifications and a reference implementation of Your Modifications or (ii) Your Modifications in Source Code form, and to make any such deviation and reference implementation or Modifications available to all third parties under the same terms as this license on a royalty free basis within thirty (30) days of Your first customer shipment of Your Modifications."
- changed permission odrl:distribute with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode]
  
  was permission odrl:distribute with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode]
  
  Manual edit Its duty cc:ShareAlike quotes "In the event that the Modifications do not meet such requirements, You agree to publish either (i) any deviation from the Standards protocol resulting from implementation of Your Modifications and a reference implementation of Your Modifications or (ii) Your Modifications in Source Code form, and to make any such deviation and reference implementation or Modifications available to all third parties under the same terms as this license on a royalty free basis within thirty (30) days of Your first customer shipment of Your Modifications."
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:standardsConformance]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:standardsConformance]
  
  Manual edit Its duty cc:ShareAlike quotes "In the event that the Modifications do not meet such requirements, You agree to publish either (i) any deviation from the Standards protocol resulting from implementation of Your Modifications and a reference implementation of Your Modifications or (ii) Your Modifications in Source Code form, and to make any such deviation and reference implementation or Modifications available to all third parties under the same terms as this license on a royalty free basis within thirty (30) days of Your first customer shipment of Your Modifications."
- added dct:license <https://creativecommons.org/licenses/by/4.0/>
  
  Manual edit Every record is published under CC BY 4.0. cc:license names the record DALICC keeps of that licence; dct:license now names it by the address Creative Commons publishes it at, so that a consumer matching the canonical IRI finds it.
Version 1

Created from the license text on 2026-09-15 (Mozilla and CDDL).

View version 1 JSON-LD Turtle RDF/XML

Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.

Nothing on this page is legal advice. What a license means is decided by its text; ask a legal advisor before you rely on it.