Sybase Open Watcom Public License 1.0

Also known as Open Watcom Public License, Sybase Open Watcom Public License, Sybase Open Watcom Public License 1.0, Watcom-1.0.

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/Watcom-1.0

Permissions

Change license from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Add statement from the text
- Attribution from the text
- Modification notice from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Display from the text
Distribute from the text
Duties
- Add statement from the text
- Attribution from the text
- Notice from the text
- Source code from the text
Modified works from the text
Modify from the text
Duties
- Add statement from the text
- Attribution from the text
- Modification notice from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Network use trigger from the text
Duties
- Source code from the text
Patent grant from the text
Present from the text
Reproduce from the text

Prohibitions

Add limitation from the text
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.

Patent license ends if you sue: Yes. Not a ban on suing: a patent claim over the work ends the patent license, or the whole license, as the text provides.
Cure period: 30 days
Governing law: the laws of the United States and the State of California
Government rights limitation: United States government end users acquire the covered code with only the rights the licence gives every other licensee
Source publication period: for as long as the covered code is deployed or twelve (12) months from the date of initial deployment, whichever is longer
Terminates on breach: Yes

Clauses

Warranty disclaimer

The Covered Code may contain in whole or in part pre-release, untested, or not fully tested works. The Covered Code may contain errors that could cause failures or loss of data, and may be incomplete or contain inaccuracies. You expressly acknowledge and agree that use of the Covered Code, or any portion thereof, is at Your sole and entire risk. THE COVERED CODE IS PROVIDED "AS IS" AND WITHOUT WARRANTY, UPGRADES OR SUPPORT OF ANY KIND AND SYBASE AND SYBASE'S LICENSOR(S) (COLLECTIVELY REFERRED TO AS "SYBASE" FOR THE PURPOSES OF SECTIONS 8 AND 9) AND ALL CONTRIBUTORS EXPRESSLY DISCLAIM ALL WARRANTIES AND/OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES AND/OR CONDITIONS OF MERCHANTABILITY, OF SATISFACTORY QUALITY, OF FITNESS FOR A PARTICULAR PURPOSE, OF ACCURACY, OF QUIET ENJOYMENT, AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SYBASE AND EACH CONTRIBUTOR DOES NOT WARRANT AGAINST INTERFERENCE WITH YOUR ENJOYMENT OF THE COVERED CODE, THAT THE FUNCTIONS CONTAINED IN THE COVERED CODE WILL MEET YOUR REQUIREMENTS, THAT THE OPERATION OF THE COVERED CODE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE COVERED CODE WILL BE CORRECTED. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY SYBASE, A SYBASE AUTHORIZED REPRESENTATIVE OR ANY CONTRIBUTOR SHALL CREATE A WARRANTY. You acknowledge that the Covered Code is not intended for use in the operation of nuclear facilities, aircraft navigation, communication systems, or air traffic control machines in which case the failure of the Covered Code could lead to death, personal injury, or severe physical or environmental damage.

Limitation of liability

TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT SHALL SYBASE OR ANY CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INCIDENTAL, SPECIAL, INDIRECT, CONSEQUENTIAL OR OTHER DAMAGES OF ANY KIND ARISING OUT OF OR RELATING TO THIS LICENSE OR YOUR USE OR INABILITY TO USE THE COVERED CODE, OR ANY PORTION THEREOF, WHETHER UNDER A THEORY OF CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCTS LIABILITY OR OTHERWISE, EVEN IF SYBASE OR SUCH CONTRIBUTOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY REMEDY. SOME JURISDICTIONS DO NOT ALLOW THE LIMITATION OF LIABILITY OF INCIDENTAL OR CONSEQUENTIAL OR OTHER DAMAGES OF ANY KIND, SO THIS LIMITATION MAY NOT APPLY TO YOU. In no event shall Sybase's or any Contributor's total liability to You for all damages (other than as may be required by applicable law) under this License exceed the amount of five hundred dollars ($500.00).

Accepting warranty or additional liability

You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations and/or other rights consistent with this License ("Additional Terms") to one or more recipients of Covered Code. However, You may do so only on Your own behalf and as Your sole responsibility, and not on behalf of Sybase or any Contributor. You must obtain the recipient's agreement that any such Additional Terms are offered by You alone, and You hereby agree to indemnify, defend and hold Sybase and every Contributor harmless for any liability incurred by or claims asserted against Sybase or such Contributor by reason of any such Additional Terms.

Additional clauses

"Deploy" means to use, sublicense or distribute Covered Code other than for Your internal research and development (R&D) and/or Personal Use, and includes without limitation, any and all internal use or distribution of Covered Code within Your business or organization except for R&D use and/or Personal Use, as well as direct or indirect sublicensing or distribution of Covered Code by You to any third party in any form or manner.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://opensource.org/license/Watcom-1.0
Legal code: https://opensource.org/license/Watcom-1.0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Sybase, Inc.
SPDX identifier: Watcom-1.0 on the SPDX license list
DALICC identifier: Watcom-1.0

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/Watcom-1.0",
  "license-title": "Sybase Open Watcom Public License 1.0",
  "spdx-id": "Watcom-1.0",
  "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/Watcom-1.0> .

RDF, JSON-LD

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

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/Watcom-1.0" rel="license">Sybase Open Watcom Public License 1.0</a>.</p>

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

Badge

Markdown

[![License: Sybase Open Watcom Public License 1.0](https://dalicc.net/license-library/Watcom-1.0/badge.svg)](https://dalicc.net/license-library/Watcom-1.0)

HTML

<a href="https://dalicc.net/license-library/Watcom-1.0"><img src="https://dalicc.net/license-library/Watcom-1.0/badge.svg" alt="License: Sybase Open Watcom Public License 1.0"></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: 13 recorded, 4 applied to the record, 0 proposed

Models version 1.0 of the Sybase Open Watcom Public License, an Apple Public Source License descendant whose duties are triggered by Deployment, which the text defines to include internal use inside an organisation. The reciprocity binds the Source Code but not the object code, so cc:ShareAlike is a duty on modify and derive rather than a license-wide duty.

13 findings

info Rubric 1 spdx:licenseId none

File name, license id, SPDX id and IRI agree. The SPDX entry names one seeAlso, so cc:legalcode and dct:source are the same URL. dct:publisher is 'Sybase, Inc.'
info Rubric 2 odrl:target none

dcmitype:Software only: the licence applies to named compiler products.
major Rubric 3 odrl:permission applied

Section 2.1 and 2.2 grant the right to 'use, reproduce, display, perform, modify and Deploy Covered Code', to the extent of 'Sybase's Applicable Patent Rights and copyrights covering the Original Code', so the record carries reproduce, distribute, modify, derive, display, present, commercial use, derivative works, modified works and dalicc:patentGrant. No distribution-fee permission: the text allows a fee only for the additional terms of section 6, which is carried as dalicc:WarrantyOrLiabilityAcceptance.
major Rubric 4 odrl:prohibition applied

dalicc:promote for section 10, dalicc:addLimitation for 2.1(b), dalicc:patentRetaliationTermination for 12.1(c) and dalicc:ChangeLicense for the requirement that Deployed Modifications be published 'under the terms of this License'.
major Rubric 5 odrl:duty applied

cc:ShareAlike is a duty on odrl:modify and odrl:derive, not license-wide, because 2.2(e) lets the object code go out on other terms: 'the object code form of the Covered Code may be distributed under Your own license agreement, provided that such license agreement contains terms no less protective of Sybase and each Contributor than the terms of this License'. cc:SourceCode, cc:Attribution, cc:Notice and dalicc:addStatement (the Exhibit A notice and the click-wrap or acceptance statement of 2.1(c)) hang off distribute, modify and derive; dalicc:modificationNotice is added to modify and derive.
minor Rubric 6 dalicc:WarrantyOrLiabilityAcceptance applied

Sections 8 and 9 are quoted verbatim into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation, section 6 into dalicc:WarrantyOrLiabilityAcceptance. Seven further clauses are quoted in dalicc:additionalClauses, among them the Deploy definition, the twelve-month source duty, the object-code allowance, the termination grounds, the United States government end user clause and the governing law.
gap Rubric 8 dalicc:additionalClauses none

The licence is triggered by deployment or by serving the work over a network, not only by distribution. The vocabulary has no term for that trigger, so the definition is quoted in dalicc:additionalClauses and the source-code duty is attached to distribute, modify and derive. Proposed term: dalicc:networkUseTrigger. Text: '"Deploy" means to use, sublicense or distribute Covered Code other than for Your internal research and development (R&D) and/or Personal Use, and includes without limitation, any and all internal use or distribution of Covered Code within Your business or organization except for R&D use and/or Personal Use'.
gap Rubric 8 dalicc:additionalClauses none

The source-code duty carries a deadline and a minimum availability period. cc:SourceCode cannot hold a period, so the clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:sourcePublicationPeriod as a literal qualifier on a cc:SourceCode duty. Text: section 2.2(c), under which the source of Deployed Modifications must stay public 'for as long as you Deploy the Covered Code or twelve (12) months from the date of initial Deployment, whichever is longer'.
gap Rubric 7 cc:jurisdiction none

The grant itself is worldwide, so cc:jurisdiction stays dalicc:worldwide; only the governing law is national. The vocabulary has no property for a governing law that is separate from the territory of the grant, so the clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:governingLaw. Text: 'This License shall be governed by the laws of the United States and the State of California, except that body of California law concerning conflicts of law.' (section 13.7)
gap Rubric 8 dalicc:additionalClauses none

Automatic termination on breach has no property that a record can carry: dalicc:terminationOnBreach is a policy quality with no predicate. The clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:terminatesOnBreach as a boolean property on odrl:Set, with the cure period as a literal. Text: 'automatically without notice if You fail to comply with any term(s) of this License and fail to cure such breach within 30 days of becoming aware of such breach' (section 12.1(a)).
gap Rubric 8 dalicc:additionalClauses none

Section 13.1 limits the rights of United States government end users to those the licence gives everyone. The vocabulary has no term for a government-rights clause; it is quoted. Proposed term: dalicc:governmentRightsLimitation.
info Rubric 9 record none

The consistency check of app.services.composer, run with the 39 axioms of licensedata/dependencygraph/dg_default.ttl, returned no conflicts.
info Rubric 10 record none

Against RPSL-1.0 the record differs by the attachment level of cc:ShareAlike and by the object-code allowance of 2.2(e); the definitions, the additional terms, the warranty section and the termination grounds are shared text. Both belong with APSL-2.0, which the library already holds.

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
3 changes
- changed permission dalicc:ChangeLicense
  
  was permission dalicc:ChangeLicense
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "You must make Source Code of all Your Deployed Modifications publicly available under the terms of this License, including the license grants set forth in Section 3 below, for as long as you Deploy the Covered Code or twelve (12) months from the date of initial Deployment, whichever is longer."
- changed prohibition dalicc:promote
  
  was prohibition dalicc:promote
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "No Sybase Marks or Contributor Marks may be used to endorse or promote products derived from the Original Code or Covered Code other than with the prior written consent of Sybase or the Contributor, as applicable."
- 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 (Reciprocal and source-available).

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.