Apache License 1.0
Also known as Apache 1.0, Apache License 1.0, Apache License, Version 1.0, Apache-1.0.
- Commercial use
- allowed
- Share alike
- not required
- Attribution
- required (keep the copyright and license notices)
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.
Permissions
-
Change license by library convention Library convention: family rule 15: Permissive records permit relicensing. Replacing the license of the work, or of an adaptation, with another license, or changing its terms.
Duties
- Use a compliant license by library convention Library convention: family rule 15: Permissive records permit relicensing. Choosing a replacement license that stays compliant with the terms of the original license.
-
Charge distribution fee from the text Charging a fee for the act of providing a copy of the work to someone else.
-
Commercial use from the text Using the work to generate income, directly or indirectly, for example by selling it or by using it in advertising.
-
Derivative works from the text Distributing an adaptation of the work and making it available to the public.
-
Derive from the text The text says: "Products derived from this software may not be called "Apache" nor may "Apache" appear in their name, without prior written permission of the Apache Group." Creating a new work from the work, such as a translation, adaptation or arrangement of it or of a part of it.
Duties
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Rename from the text Giving a modified or derived work a name that tells it apart from the original.
-
Duties
- Add statement from the text Attaching terms, notices or statements of one's own to the work or to one's modifications when passing it on.
- Advertising acknowledgement from the text Displaying a prescribed acknowledgement, whose wording dalicc:PromotionSpecification carries, in every advertisement that mentions the work or its use.
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
-
Modified works from the text Distributing a modified version of the work that does not amount to a new, derivative work.
-
Modify from the text Altering the work, for example by updating it, without creating a new work; an alteration that creates a new work is Derive.
Duties
- Attribution from the text Giving credit to the copyright holders or authors of the work, in the form the licensor asks for.
- Notice from the text Notice: keeping the license and copyright notices with every copy.
- Rename from the text Giving a modified or derived work a name that tells it apart from the original.
-
Present from the text Performing the work in public, including by broadcast or other communication to the public.
Prohibitions
-
Promote from the text Not permitted: Promote. The text says: "The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission." Using the name or trademarks of the licensor or of contributors to endorse or promote a product.
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.
Clauses
Warranty disclaimer
THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
Limitation of liability
IN NO EVENT SHALL THE APACHE GROUP OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Additional clauses
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the Apache Group for use in the Apache HTTP server project (http://www.apache.org/)."
Promotion specification
This product includes software developed by the Apache Group for use in the Apache HTTP server project (http://www.apache.org/).
Info
- Target asset types
- Software
- Region / jurisdiction
- Worldwide
- Validity
- Perpetual
- Source
- https://spdx.org/licenses/Apache-1.0.html
- Legal code
- http://www.apache.org/licenses/LICENSE-1.0
- This description is published under
- Creative Commons Attribution 4.0 International
- Publisher
- The Apache Software Foundation
- Attribution name
- The Apache Group
- SPDX identifier
-
Apache-1.0on the SPDX license list - DALICC identifier
Apache-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/Apache-1.0",
"license-title": "Apache License 1.0",
"spdx-id": "Apache-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/Apache-1.0> .
RDF, JSON-LD
{
"@context": {
"cc": "http://creativecommons.org/ns#"
},
"@id": "https://example.org/my-work",
"cc:license": {
"@id": "https://dalicc.net/licenselibrary/Apache-1.0"
}
}
HTML attribution
<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/Apache-1.0" rel="license">Apache License 1.0</a>.</p>
This license asks for attribution, so the credit line is part of it.
Badge
Markdown
[](https://dalicc.net/license-library/Apache-1.0)
HTML
<a href="https://dalicc.net/license-library/Apache-1.0"><img src="https://dalicc.net/license-library/Apache-1.0/badge.svg" alt="License: Apache License 1.0"></a>
Review
- Written from the license text by
- Giray Havur
- Written on
- 2026-09-22
- Second review
- not yet done
- Record changed since this review
- yes (version 2, 2026-09-24)
- Findings
- 15 recorded, 12 applied to the record, 0 proposed
Models the first Apache licence, the six-clause BSD-style text the Apache Group used before version 1.1. It keeps the two retention clauses of BSD, adds the advertising acknowledgement, the endorsement bar and the bar on calling a derived product Apache, and adds a sixth clause that puts the acknowledgement on every redistribution of any form. The record follows Apache-1.1 for its clause texts and for dalicc:PromotionSpecification.
15 findings
-
info Rubric 1
spdx:licenseIdappliedFile name, record identifier, SPDX identifier and IRI local name are all Apache-1.0.
-
info Rubric 2
odrl:targetappliedOne odrl:AssetCollection of dct:type dcmitype:Software. The text licenses source and binary forms of a program.
-
major Rubric 3
odrl:permissionappliedThe grant reads "Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met". The record therefore permits reproduce, distribute, modify, derive, display, present, commercial use, derivative works, modified works and the distribution fee, the set Apache-1.1 carries.
-
major Rubric 3
odrl:permissionapplieddalicc:ChangeLicense is permitted and carries the dalicc:compliantLicense duty. The text keeps conditions that have to survive a relicensing, and it nowhere bars putting a copy under other terms, which is family rule 15.
-
major Rubric 4
odrl:prohibitionappliedClause 4 reads "The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission", so dalicc:promote is prohibited.
-
major Rubric 5
odrl:dutyappliedcc:Attribution and cc:Notice hang off odrl:distribute, odrl:modify and odrl:derive, because clauses 1 and 2 make the copyright notice, the list of conditions and the disclaimer travel with every source and every binary copy. dalicc:advertisingAcknowledgement carries clause 3 and dalicc:addStatement carries clause 6; both hang off odrl:distribute, since each is triggered by handing the work on rather than by changing it.
-
minor Rubric 5
odrl:dutyapplieddalicc:rename hangs off odrl:modify and odrl:derive for clause 5, "Products derived from this software may not be called "Apache" nor may "Apache" appear in their name". Apache-1.1 attaches the same duty for the same clause.
-
minor Rubric 5
odrl:dutyappliedNo dalicc:modificationNotice. The text asks nowhere for a record of the changes made, and the consolidation decision of 2026-09-15 is that a permissive record gets that duty only where its text asks for one. The Apache-1.1 record carries the duty although its text is silent in the same way; the divergence is reported rather than edited.
-
minor Rubric 6
dalicc:WarrantyDisclaimerappliedThe single disclaimer paragraph carries two clauses. The record splits it at the sentence boundary: the warranty sentence goes to dalicc:WarrantyDisclaimer and the liability sentence to dalicc:LiabilityLimitation, both verbatim. This follows BSD-1-Clause, which split the same paragraph on 2026-09-15.
-
info Rubric 6
dalicc:PromotionSpecificationapplieddalicc:PromotionSpecification carries the acknowledgement wording itself, following Apache-1.1, and clauses 3 and 6 are quoted in full in dalicc:additionalClauses so that a reader sees where the wording has to appear.
-
minor Rubric 6
dalicc:WarrantyDisclaimerappliedThe disclaimer uses the typewriter quotation marks of the original (``AS IS''), which are kept verbatim.
-
info Rubric 7
cc:jurisdictionappliedThe text names no legal system and sets no term, so cc:jurisdiction is dalicc:worldwide and dalicc:validityType is dalicc:perpetual.
-
info Rubric 8
dalicc:additionalClausesnoneEvery clause of the text is either modelled or quoted. No clause needed a term the vocabulary does not have.
-
info Rubric 9
recordnoneThe consistency check of app.services.composer against the dependency graph dg_default returned an empty conflict list.
-
info Rubric 10
recordnoneRead against licensedata/licenses/Apache-1.1.ttl, the differences are: the sixth clause, carried by the dalicc:addStatement duty; an explicit dalicc:advertisingAcknowledgement duty, which the Apache-1.1 record does not carry although its clause 3 is the same; no dalicc:modificationNotice duty; a warranty and a liability clause, which the Apache-1.1 record leaves out; and odrl:target dcmitype:Software alone.
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
4 changes
-
changed
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]was
permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]Manual edit The statement is marked as a library convention, family rule 15: Permissive records permit relicensing: the text does not state it in as many words. Its duty dalicc:compliantLicense is marked as a library convention, family rule 15: Permissive records permit relicensing.
-
changed
permission odrl:derive with duties [cc:Attribution, cc:Notice, dalicc:rename]was
permission odrl:derive with duties [cc:Attribution, cc:Notice, dalicc:rename]Manual edit The statement now quotes the sentence of the licence text it rests on: "Products derived from this software may not be called "Apache" nor may "Apache" appear in their name, without prior written permission of the Apache Group."
-
changed
prohibition dalicc:promotewas
prohibition dalicc:promoteManual edit The statement now quotes the sentence of the licence text it rests on: "The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission."
-
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-22 (Permissive variants).
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.