GitCaddy/license-list-XML
2
0
Fork 0
Code Issues Releases

Merge branch 'main' into main

Browse Source
This commit is contained in:
Steve Winslow
2023-02-23 12:37:35 -05:00
committed by GitHub
parent e26bf1c2c8 8146c7190e
commit 01bd2aaca1
78 changed files with 3335 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
.gitignore vendored
View File

@@ -12,12 +12,6 @@
/resources
/licenseListPublisher-*.jar*
# Ignore test.log generated by using test-one-license command
test.log
# nodeJS
node_modules/
# vim backup/swap files
[._]*.s[a-w][a-z]
[._]s[a-w][a-z]

8
.travis.yml
View File

@@ -1,8 +0,0 @@
matrix:
include:
- language: java
script:
- if [[ "$TRAVIS_PULL_REQUEST" = "false" && ("master" = "$TRAVIS_BRANCH" || "$TRAVIS_TAG" = "$TRAVIS_BRANCH") ]]; then make deploy-license-data; else make validate-canonical-match; fi
- language: node_js
node_js:
- "9"

4
CONTRIBUTING.md
View File

@@ -21,11 +21,11 @@ Below are some ways you can get started participating and contributing!
* Make suggestions to improvement for documentation: Newcomers have a great perspective as to the effectiveness of documentation! You can make suggestions via an issue, if you want to discuss the changes or if there is something specific that could be updated, then create a PR
* Help prepare files for licenses approved to be added to the SPDX License List by following the [new license workflow](https://github.com/spdx/license-list-XML/blob/main/DOCS/new-license-workflow.md)
* Help prepare files for licenses approved to be added to the SPDX License List by following the [new license workflow](DOCS/new-license-workflow.md)
* Review PRs
* Request a new license be added to the SPDX License List by following the [request new license](https://github.com/spdx/license-list-XML/blob/main/DOCS/request-new-license.md) instructions
* Request a new license be added to the SPDX License List by following the [request new license](DOCS/request-new-license.md) instructions
* Email the [mailing list](https://lists.spdx.org/g/spdx-legal) about how you are using or questions about the SPDX License List
* Recommend additional markup for matching purposes

59
DOCS/faq.md
View File

@@ -1,24 +1,21 @@
Tip: use the table of contents icon in the upper left hand corner of this window to see a list of FAQs
The SPDX License List
=====================
# The SPDX License List
# What is the SPDX License List?
## What is the SPDX License List?
The SPDX License List is an integral part of the SPDX Specification. The
SPDX License List itself is a list of commonly found licenses and
exceptions used in free and open or collaborative software, data,
hardware, or documentation. The SPDX License List includes a
standardized short identifier, the full name, the license text, and a
hardware, or documentation. The SPDX License List includes [various fields](license-fields.md), notably:
a standardized short identifier, the full name, the license text, and a
canonical permanent URL for each license and exception.
It is more than just a list, though. The SPDX License List incorporates
* [license inclusion principles](https://github.com/spdx/license-list-XML/blob/main/DOCS/license-inclusion-principles.md)
It is more than just a list, though. The SPDX License List relies on:
* [license inclusion principles](license-inclusion-principles.md)
regarding what is eligible for inclusion on the SPDX License List
* [matching guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/)
provide parameters as to what constitutes a match to a license or exception on the SPDX License List
* an [explanation of the fields](https://github.com/spdx/license-list-XML/blob/main/DOCS/license-fields.md)
used in the SPDX License List
* [license expression syntax](LINK)
* [license expression syntax](https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/)
enable expressing composite licensing scenarios, such as when more than one license applies, there is a choice of license, or an exception or additional terms apply to the license
The authoritative files for the SPDX License List are stored in XML source files
@@ -30,7 +27,7 @@ There are also certain sections in the SPDX specification related to license inf
It is helpful to understand the fields and purpose of these sections, even if you
are not generating or consuming an SPDX document.
## Why does it exist?
### Why does it exist?
The purpose of the SPDX License List is to enable efficient and reliable
identification of licenses and exceptions in an SPDX document, in
source files, or elsewhere. In an SPDX document, being able to refer to licenses via the short
@@ -45,10 +42,10 @@ file. For more information on this use and examples, see [Annex E of
the SPDX
Specification](https://spdx.github.io/spdx-spec/v2.3/using-SPDX-short-identifiers-in-source-files/).
## What is an “exception”?
An “exception” on the SPDX License List is text that is not a stand-alone license, but grants an exception to a license condition or additional permissions beyond those granted in the license is modifies.
### What is an “exception”?
An “exception” on the SPDX License List is text that is not a stand-alone license, but grants an exception to a license condition or additional permissions beyond those granted in the license it modifies.
## Why are exceptions listed separately?
### Why are exceptions listed separately?
In 2015, SPDX 2.0 introduced the concept of license expressions and moved the license
exceptions to a sub-list, in order to accommodate a more realistic
combination of licenses and exceptions. For ease of finding, [license exceptions are listed on their own
@@ -57,63 +54,63 @@ the WITH operator. For more information about license expressions, see
[Annex D of the SPDX
Specification](https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/).
## What are these "matching guidelines" about?
### What are these "matching guidelines" about?
The SPDX License List also includes a set of [license matching
guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/)
that define what is a match and to ensure that the license identifiers are used in a consistent and
reliable way.
## Does the license text need to be the same to use an SPDX short identifier?
### Does the license text need to be the same to use an SPDX short identifier?
There are some non-substantive variations formally allowed, unique to each license. For example, capitalization, white space, and use of different bullets or numbering would not be considered a different license. Another example is if the license text includes the name of the author or a generic "author", this is not considered a legally substantive difference to the license terms themselves, and can be considered the same license. Such text is denoted with special tags in the XML file and denoted by red text on the webpages.
See the [matching guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/) for details.
See the [matching guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/) for details or the [XML file](https://github.com/spdx/license-list-XML/tree/main/src) for the specific license for particular details.
## What does the blue text and red text mean in the license list entry?
### What does the blue text and red text mean in the license list entry?
The license text on the HTML pages implement some easy-to-view aspects of the [matching guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/) by displaying omitable text in blue and replaceable text in red.
# What is the criteria for inclusion on the SPDX License List?
## What is the criteria for inclusion on the SPDX License List?
The [license inclusion principles](https://github.com/spdx/license-list-XML/blob/main/DOCS/license-inclusion-principles.md) include a list of factors, some of which are more important than others. You should read the guidelines in full, but some of the key factors include: use of the license on significant projects: the license free and open, or if not, does it make the source code available; the license text is understandable and stable (i.e., it is not in the midst of drafting). For more information on how inclusion guidelines for the SPDX License List have evolved over time, see https://github.com/spdx/license-list-XML/blob/main/DOCS/license-inclusion-principles.md#historical-background.
The [license inclusion principles](license-inclusion-principles.md) include a list of factors, some of which are more important than others. You should read the guidelines in full, but some of the key factors include: use of the license on significant projects: the license free and open, or if not, does it make the source code available; the license text is understandable and stable (i.e., it is not in the midst of drafting). For more information on how inclusion guidelines for the SPDX License List have evolved over time, see [DOCS/license-inclusion-principles.md#historical-background](license-inclusion-principles.md#historical-background).
## Who decides what is included on the SPDX License list?
The SPDX contributors who participate in the project as part of the SPDX-legal team apply a set of license inclusion guidelines when determining whether a license may be included in the SPDX License List. Anyone can weigh in as to whether they think a license or exception should be included, but factors that are not relevant to the license inclusion guidelines will not be persuasive.
### Who decides what is included on the SPDX License list?
The SPDX contributors who participate in the project as part of the SPDX-legal team apply the [license inclusion guidelines](license-inclusion-principles.md) when determining whether a license may be included in the SPDX License List. Anyone can weigh in as to whether they think a license or exception should be included, but factors that are not relevant to the license inclusion guidelines will not be persuasive.
## Who is SPDX-legal?
### Who is SPDX-legal?
The SPDX project is comprised of various teams who focus on different aspects of the overall project. The SPDX-legal team is comprised of lawyers, project managers, engineers, developers, and other people interested in licensing issues. Anyone is welcome and we aim to be a friendly group!
The SPDX-legal team leads are listed here: https://spdx.dev/about/governance/
## What does it mean when a license ID is "deprecated"?
### What does it mean when a license ID is "deprecated"?
A license identifier is "deprecated" when there is an updated license identifier and the deprecated license identifier. SPDX aims to not changes license identifiers, unless there is a compelling reason and is not a decision taken lightly. Deprecated license identifiers, while remaining valid, should no longer be used. The URL to each deprecated license is retained and those license pages are updated to note the deprecation.
# How do I request adding a license to the SPDX License List?
## How do I request adding a license to the SPDX License List?
Follow the instructions here:
https://github.com/spdx/license-list-XML/blob/main/DOCS/request-new-license.md
[DOCS/request-new-license.md](request-new-license.md)
## How does one handle licenses not found in the SPDX License List?
### How does one handle licenses not found in the SPDX License List?
When a license identified in the software package is not found in the
list of approved SPDX licenses, one can define a new license label, using `LicenseRef-<name>`..This is explained in [Clause 10 of the SPDX Specification](https://spdx.github.io/spdx-spec/v2.3/other-licensing-information-detected/).
# What are license expressions?
## What are license expressions?
Sometimes a single license can be used to represent the licensing terms of a package or file, but there are situations where a single license identifier is not sufficient. [SPDX License Expressions](https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/) provide a way to construct more complex licensing scenarios. expressions. A license expression could be a single license identifier found on the SPDX License List; a user defined license reference denoted by the `LicenseRef-<idString>`; a license identifier combined with an SPDX exception; or some combination of license identifiers, license references and exceptions constructed using a small set of defined operators: `AND`, `OR`, `WITH` and `+`)
## How does one represent a file or package that is licensed under a choice of two or more licenses?
### How does one represent a file or package that is licensed under a choice of two or more licenses?
A licensing choice can be represented by a license expression using
the `OR` operator. For example, a file that is disjunctively licensed
under either the GPL-2.0-only or MIT would be represented using the following
disjunctive expression: `GPL-2.0-only OR MIT`.
## How does one represent a file or package that is licensed under two or more licenses?
### How does one represent a file or package that is licensed under two or more licenses?
Conjunctive licensing can be represented via a license expression using
the 'AND' operator. For example, a file or package that is subject to the Apache-2.0,
MIT, and GPL-2.0-or-later would be represented using the following conjunctive
expression: `Apache-2.0 AND MIT AND GPL-2.0-or-later`
# How are license identifiers used in an SPDX Document?
## How are license identifiers used in an SPDX Document?
The SPDX specification includes fields to record license information at the [package](https://spdx.github.io/spdx-spec/v2.3/package-information/), [file](https://spdx.github.io/spdx-spec/v2.3/file-information/), and [snippet](https://spdx.github.io/spdx-spec/v2.3/snippet-information/) level.

32
DOCS/history.md Normal file
View File

@@ -0,0 +1,32 @@
# A historical timeline for the SPDX License List
## The beginning
* 2009: The concept of the SPDX project begins. [LWN](https://lwn.net/Articles/370308/) writes about it in Jan 2010.
* Aug 2010: Early discusions of the need for [a fixed list of licenses](https://wiki.spdx.org/view/General_Meeting/Minutes/2010-08-26) led to the arugment for decoupling that list from the spec itself. [Version 1.0 (beta)](https://web.archive.org/web/20110128200808/spdx.org/licenses) is posted on the SPDX website. The initial set of licenses was included based on informal discussion and consensus on the SPDX working group calls and email list.
* Sept 2010: [Special meeting](https://wiki.spdx.org/view/Legal_Team/Minutes/2010-09-24) to discuss the format and approach for the SPDX License List.
* Dec 2010: [SPDX legal workstream](https://wiki.spdx.org/view/Legal_Team/Minutes/2010-12-15) created and begins having dedicated meetings every other week
* Spring 2011: OSI adopts SPDX identifiers on website; [work begins](https://opensource.org/minutes20110608) between the two groups to align license text of OSI-approved licenses; emails exchanged over SPDX and OSI mailing lists relating to this project over the next couple years.
* Aug 2011: SPDX Specification 1.0 released
* April 2012: SPDX-legal establishs and publishes a process for requesting a new license be added to the SPDX License List via spdx-legal mailing list
* July 2012: blog post about [using SPDX identifers in source files](https://hakre.wordpress.com/2012/07/25/using-the-spdx-license-list-for-tagging-and-linking/)
* 2012/2013: [Initial license inclusion principles](https://wiki.spdx.org/view/Legal_Team/Decisions/Inclusion_Guidelines_(Background)) created and posted to SPDX website
* 2013: [U-Boot begins using SPDX identifiers](https://gitlab.denx.de/u-boot/u-boot/blob/6612ab33956ae09c5ba2fde9c1540b519625ba37/post/post.c) in source files
* Early 2014: origin files for SPDX License List move to Git repository (v1.19 / v1.20)
* Aug 2014: v1.20 released with ~80 new licenses from Fedora “good list”
## Version 2.0
* May 2015: [v2.0 of both the spec and license list are released](https://spdx.dev/milestone-day-spdx-release-version-2-0-release-great-step-forward-greatly-expands-utility-applicability-spec/), adding the license expression syntax (in the spec) and a distinct list of license exceptions (to the license list) to allow greater flexibility in representing licenses or license combinations. SPDX-legal implements a quarterly release cycle for the SPDX License List.
* July 2015: A [simple request](https://lists.spdx.org/g/Spdx-legal/message/1186) to clarify the application of the Matching Guidelines to Apache-2.0 kicks off a discussion of a better implementation of the matching guidelines and storage of SPDX License List data. SPDX legal and tech team start working on a [matching template project for SPDX license files](https://wiki.spdx.org/view/Legal_Team/Templatizing).
* Early 2016: Plan is finalized to convert SPDX License List from its original format of a spreadsheet and text files to XML files with specific markup to implement the matching guidelines. This requires human review of each auto-generated initial XML file for every license and exception on the SPDX License List.
* Spring 2016: v2.1 of the SPDX Spec adds an [Appendix on using license identifiers in source files](https://spdx.dev/spdx-specification-21-web-version/#h.twlc0ztnng3b)
* Mid 2017: [Linux kernel starts using SPDX identifiers](https://lwn.net/Articles/739183/) with work getting underway in earnest by Nov 2017
## Version 3.0
* May 2017: Free Software Foundation, by way of the Executive Director and Richard Stallman, reach out to Kate and Jilayne asking that SPDX change the GPL-2.0 identifier to be more clear that it is referring to GPL-2.0 "only". Discussions on this topic begin amongst the [SPDX legal and tech](https://wiki.spdx.org/view/Legal_Team/Minutes/2017-07-06) teams over the rest of the year as to how to accommodate this ask while maintaining backward compatibility. This also prompts a closer look at how other licenses deal with options to use any later version of the license. This is in the midst of the templatizing work to convert the SPDX License List to a different format.
* Jan 2018: [SPDX License List v3.0 release](https://spdx.dev/license-list-3-0-released/) converts original files to XML format implementing matching guidelines and revised GNU licenses identifiers. SPDX-legal evolves to full use of Github for maintaining the SPDX License List
* Summer 2018: GSoC project creates online license submission tool
* mid-2019: Start discussions to revisit and update license inclusion guidelines. Discussions occur in [Github issue](https://github.com/spdx/license-list-XML/issues/925), [legal calls](https://wiki.spdx.org/view/Legal_Team/Minutes/2019-10-17), and then a [pull request](https://github.com/spdx/license-list-XML/pull/985) into early 2020.
* Mar 2020: New license inclusion guidelines [finalized and published](license-inclusion-principles.md) in the DOCS section of the SPDX License List Github repo, instead of a page on the website, as they had been previously.
* Sept 2021: The SPDX specificaton is [recognized as an ISO standard](https://www.linuxfoundation.org/press/featured/spdx-becomes-internationally-recognized-standard-for-software-bill-of-materials)
* July 2022: [Fedora officially adopts the use of SPDX license identifiers](https://communityblog.fedoraproject.org/important-changes-to-software-license-information-in-fedora-packages-spdx-and-more/) in the license metadata of Fedora package spec files.

6
DOCS/new-license-workflow.md
View File

@@ -35,7 +35,7 @@
2. If it’s a case that additional markup would create match, then may want to discuss with legal team to ensure markup is non-substantive or differences in text do not alter legal meaning (if so, this cuts towards adding a new license). For more on this see the [Matching Guidelines](https://spdx.org/spdx-license-list/matching-guidelines), guideline #2 in particular.
3. If additional markup can accommodate the license, then the license does not need to be added: inform the requester, comment on the issue as such, then create a PR for the existing license with the additional markup, and close issue once the PR has been merged.
3. If the submitter is not the license author or steward, ask for that contact or try to find that person or organization to make them aware the license has been submitted.
4. Check the submission for any other missing information, e.g., working URL, examples of use, full text, standard header, etc. You can find the field definitions in the [DOCS/license-fields](https://github.com/spdx/license-list-XML/blob/main/DOCS/license-fields.md) document.
4. Check the submission for any other missing information, e.g., working URL, examples of use, full text, standard header, etc. You can find the field definitions in the [DOCS/license-fields](license-fields.md) document.
Ask the submitter for any additional info needed, preferably via the GitHub issue, if possible. Record any updates there.
1. The "standard header" or "official license header" is defined in section 1.1.1 of the [SPDX Matching Guidelines](https://spdx.github.io/spdx-spec/appendix-II-license-matching-guidelines-and-templates/) as "specific text specified within the license itself to be put in the header of files."
5. Review the following, bring any questions to legal team:
@@ -176,7 +176,7 @@ If you don't feel like a cup of tea right now, you can run the `make validate-ca
### Handling Duplicate Licenses
The CI/CD pipeline will fail if it detects an existing license with matching license text. If this occurs, manually review the duplicate license. If this is expected (e.g. if the duplicate license is a deprecated version of the same license), add the following to the [expected-warnings](https://github.com/spdx/license-list-XML/blob/main/expected-warnings) file:
The CI/CD pipeline will fail if it detects an existing license with matching license text. If this occurs, manually review the duplicate license. If this is expected (e.g. if the duplicate license is a deprecated version of the same license), add the following to the [expected-warnings](../expected-warnings) file:
```
,"Duplicates licenses: DUPLICATE_LICENSE_ID, MY_LICENSE_ID","Duplicates licenses: MY_LICENSE_ID, DUPLICATE_LICENSE_ID"
@@ -210,7 +210,7 @@ The [SPDX Online tools](https://tools.spdx.org/) are an option for editing the X
1. The current XML output does not implement some of XML tagging and may mark every new line with a paragraph tag depending on input. If this has happened, it may be more efficient to re-submit the license text, using a wrapped text version.
2. Make sure to include listVersionAdded= and the correct license list version number for the upcoming release
3. Check for a standard license header
4. Check if any notes should be added (see the field description in the [DOCS/license-fields](https://github.com/spdx/license-list-XML/blob/main/DOCS/license-fields.md) document for more information)
4. Check if any notes should be added (see the field description in the [DOCS/license-fields](license-fields.md) document for more information)
5. Check that we have a working URL for the license text in the wild. If using a link in GitHub, include a link to a specific commit
6. Check all the XML formatting: the current XML output does not insert the bullet or list tags. Use a previously submitted license as reference for how to format
7. If you have questions about text that could be optional or could be replaceable, add a comment to the PR, once made or add a reviewer to check it

4
DOCS/release-process.md
View File

@@ -26,7 +26,7 @@ Requesters may be uncertain as to whether they should use a newly-added license
### Draft release notes
* Add a new release text section to the top of [RELEASE-NOTES.md](https://github.com/spdx/license-list-XML/blob/main/RELEASE-NOTES.md)
* Add a new release text section to the top of [RELEASE-NOTES.md](../RELEASE-NOTES.md)
* Mimic the same pattern as the prior release notes, listing each license or exception added in this release, together with brief notes about any other significant changes in this release
* Create compare link by changing tag numbers in previous release
* The PR to add the release notes should be the last PR merged before the release is tagged
@@ -94,4 +94,4 @@ This also assumes that you have used the AWS S3 scripts to make a local copy of
### Notify the mailing list
* Send an email to the spdx-legal mailing list announcing the release, using content from [RELEASE-NOTES.md](https://github.com/spdx/license-list-XML/blob/main/RELEASE-NOTES.md), in a format similar to https://lists.spdx.org/g/Spdx-legal/message/3201
* Send an email to the spdx-legal mailing list announcing the release, using content from [RELEASE-NOTES.md](../RELEASE-NOTES.md), in a format similar to https://lists.spdx.org/g/Spdx-legal/message/3201

31
DOCS/request-new-license.md
View File

@@ -1,15 +1,15 @@
The SPDX Legal Team appreciates proposals for new free and open source licenses or exceptions to be added to the SPDX License List. Please make sure to stay engaged with your request and if it is accepted, then help prepare the files necessary to its inclusion on the SPDX License List.
# How to request a new license or exception be added to the SPDX License List
# How to request a new license or exception to the SPDX License List
1. Review the [license inclusion principles](license-inclusion-principles.md). Please refrain from submitting licenses that clearly do not meet these principles, for example, a license for which the text is not finalized or is a non-FOSS license only used for a small or personal project.
1. Check the [SPDX License List](https://spdx.org/licenses/), keeping in mind the [SPDX License List Matching Guidelines](https://spdx.github.io/spdx-spec/v2.3/license-matching-guidelines-and-templates/) and issues labeled [new license/exception request](https://github.com/spdx/license-list-XML/labels/new%20license%2Fexception%20request) to ensure your license or exception has not been previously requested.
2. If your license is not already on the SPDX License List, submit your request via the SPDX Online Tool [Submit New License](https://tools.spdx.org/app/submit_new_license/) using the guidance provided there. Also see the [explanation of the fields contained on the list](license-fields.md).
* Note: You must have a Github account in order to use this tool/process.
* Note: Whether you use the [Submit New License](https://tools.spdx.org/app/submit_new_license/) tool or submit manually via a new issue, you will need to provide *all* of the information as per the form in the tool. Incomplete submissions will delay the process.
* NOTE: You must have a Github account in order to use this tool/process.
* NOTE: Whether you use the [Submit New License](https://tools.spdx.org/app/submit_new_license/) tool or submit manually via a new issue, you will need to provide *all* of the information as per the form in the tool. Incomplete submissions will delay the process.
3. Submitters are expected to follow and participate in the discussion and answer any request for additional information via the issue and comments. Please note, if submitters are unresponsive for several months, the issue will be closed without making a final decision.
@@ -21,12 +21,27 @@ The SPDX Legal Team appreciates proposals for new free and open source licenses
2. Issues will be labeled either `new license/exception: Accepted` or `new license/exception: Not Accepted` as appropriate with an explanation and the Issue closed for the latter case.
3. If accepted, the new license or exception files will be need to be prepared via a Pull Request: a plain text test file should be UTF-8 encoded and match the text and formatting of the original license; and [an XML file](https://github.com/spdx/license-list-XML/blob/main/DOCS/xml-fields.md) with the appropriate specific tags.
1. It is expected that the Pull Request is prepared by the license submitter, with help from experienced members of the SPDX-legal team, as needed.
1. An SPDX-legal team member will review and merge the PR, unless changes are needed.
NOTE: If a license is *not* accepted for inclusion on the SPDX License List, you can use the 'LicenseRef-[idstring]' tag to identify your license, as per the [SPDX specification, clause 10](https://spdx.github.io/spdx-spec/v2.3/other-licensing-information-detected/)
# Accepted License Process
If accepted, two files will be need to be prepared for each license or exception: a plain text test file and an XML file, as explained below.
* NOTE: It is expected that the pull request is prepared by the license submitter, with help from experienced members of the SPDX-legal team, as needed.
* NOTE: Both files must use the licenseId (short identifier) as the filename. The XML and test .txt files must be named identically using that licenseId value. For instance, if you're adding the K-9 Robotic Dog Hardware License with a licenseId of K-9RDHL, you will have an XML file named K-9RDHL.xml and a test .txt file named K-9RDHL.txt. The licenseId value will be identified in the license decision issue summary.
1. __Create the XML file__: There are two ways to created the files for the new license. Either way, you will need to first ensure you have created a clone/fork of the license-list-XML repository (do not rename the fork).
* If the license was sumbitted via the [SPDX Online Tool](https://tools.spdx.org/app/license_requests/), you can use the `edit the XML` function for the license request in the SPDX Online Tool to create the XML file and a pull request, as described in [this video](https://drive.google.com/file/d/1EGyD1_hVrhMMeU2K7tsiaWlmCX7rJBbV/view?usp=share_link).
* Alternatively, you can use Git to clone (fork) the license-list-XML repository (repo), make the edits on your clone of the repo, then send a pull request, as described in [this document](git-usage.md) and [this video](https://drive.google.com/file/d/10deXLZWNvWl7zjKczf-DuJx3oooN_7CI/view?usp=share_link).
* Either way, [XML fields](xml-fields.md) is helpful for specific guidance on the implementing the XML tags.
1. __Create the text file__: In the same pull request where you created the XML file, create a new .txt file in the `test/simpleTestForGenerator/` directory of your clone or branch of the license-list-XML repo. This must be UTF-8 encoded. Special characters such as smart quotes should be avoided. Do try to keep formatting elements such as section indentation, _using spaces to make the indentation rather than using tabs_.
* Use the canonical text for the license. There should be a link to this in the submission issue.
* Copy the text of the license and add it to an appropriately named .txt file.
3. An SPDX-legal team member will review and merge the PR, unless changes are needed.
4. The new license/exception will be officially added and appear on the SPDX License List website for the next release of the SPDX License List.
Note: Once a license has been accepted and to be added to the SPDX License List and the associated files merged, it is fine to start using the SPDX identifier, even if the official release has not yet occurred.
NOTE: As per the [SPDX License List Release Process](release-process.md), when a new license or exception is accepted to add to the SPDX License List and its corresponding PR is merged, the text and ID will not immediately appear on the SPDX License List website until a release. In the interim, the new license will appear on the license list preview site at https://spdx.github.io/license-list-data/.
Note: If a license is *not* accepted for inclusion on the SPDX License List, you can use the 'LicenseRef-[idstring]' tag to identify your license, as per the [SPDX specification, clause 10](https://spdx.github.io/spdx-spec/v2.3/other-licensing-information-detected/)

8
DOCS/template-decision.md
View File

@@ -5,11 +5,11 @@
- [ ] approved
- [ ] not approved
## License full name
## Name
_record full name that will be used in the license list_
## Short ID
## License ID
_record final decision on short id to be used; **take care** as it is policy that this id never change_
@@ -17,6 +17,10 @@ _record final decision on short id to be used; **take care** as it is policy tha
_describe any markup for replaceable or omitable text needed in the XML for the license_
## Notes:
_add any information that is to be included in the Notes field_
## Additional rationale or notes on decision:
_add any additional information, including optionally a summary of what is recorded in the issue comments_

4
DOCS/xml-fields.md
View File

@@ -170,7 +170,7 @@ The **<alt>** tag includes two attributes:
Note that an example of actually-matching text should be included between the `<alt>` and `</alt>` tags, as the specified example is what will be rendered on the SPDX License List website page and in license text files provided by SPDX. To the extent a license has a "canonical" or "most commonly used" standard language, use that in the match between the `alt` tags.
Learning regular expressions is outside the scope of this document. However, here are a few of the most common patterns, taken from [BSD-3-Clause](https://github.com/spdx/license-list-XML/blob/main/src/BSD-3-Clause.xml) which is a good example of using several `<alt>` tags effectively:
Learning regular expressions is outside the scope of this document. However, here are a few of the most common patterns, taken from [BSD-3-Clause](../src/BSD-3-Clause.xml) which is a good example of using several `<alt>` tags effectively:
* `<alt match="are|is" name="tobe">are</alt>`: Matches if the text is either the word "are" or the word "is"
* `<alt match="EXPRESS(ED)?" name="express">EXPRESS</alt>`: Matches if the text is either the word "EXPRESS" or the word "EXPRESSED"
* `<alt match=".+" name="copyrightHolderAsIs">THE COPYRIGHT HOLDERS AND CONTRIBUTORS</alt>`: Matches anything as long as it consists of at least one or more characters
@@ -179,4 +179,4 @@ Learning regular expressions is outside the scope of this document. However, her
"Smart quotes" (the curly quotation mark characters) are a pain. Only "non-smart" quotes should be included in templates. In particular, if you are copying from a Word document, there's a good chance it will paste smart quotes, so check carefully.
Some characters (such as `<` and `>`, or double-quotes within an already-quoted attribute string) cannot be included as-is in license templates, because they will be interpreted as having a different meaning in XML. These would need to be replaced with special character codes. Again, [BSD-3-Clause](https://github.com/spdx/license-list-XML/blob/main/src/BSD-3-Clause.xml) is a good example of a couple of these.
Some characters (such as `<` and `>`, or double-quotes within an already-quoted attribute string) cannot be included as-is in license templates, because they will be interpreted as having a different meaning in XML. These would need to be replaced with special character codes. Again, [BSD-3-Clause](../src/BSD-3-Clause.xml) is a good example of a couple of these.

2
Makefile
View File

@@ -1,6 +1,6 @@
# SPDX-License-Identifier: CC0-1.0
TOOL_VERSION = 2.2.7
TOOL_VERSION = 2.2.8
TEST_DATA = test/simpleTestForGenerator
GIT_AUTHOR = License Publisher (maintained by Gary O'Neall) <gary@sourceauditor.com>
GIT_AUTHOR_EMAIL = gary@sourceauditor.com

6
README.md
View File

@@ -7,13 +7,13 @@ The [SPDX License List](https://spdx.org/licenses/) is an integral part of the S
The purpose of the SPDX License List is to enable efficient and reliable identification of such licenses and exceptions in an SPDX document, in source files or elsewhere. The SPDX short identifiers combined with the matching guidelines ensures that anyone can reliably know exactly what license text is being referred to for a given SPDX identifier.
## How
* For more about how SPDX license identifiers are used in an SPDX document, a software bill of materials, or other places that store license data, see [SPDX Specification](https://spdx.org/specifications), Sections 3, 4, and 6 and Appendices II, IV, and V.
* For more about how SPDX license identifiers are used in an SPDX document, a software bill of materials, or other places that store license data, see [SPDX Specification](https://spdx.org/specifications), Clauses 7, 8, and 10 and Annexes B, D, and E.
* For examples of use of SPDX license identifiers in source code, see https://spdx.org/ids.
Please note, a license not on the SPDX License List can be included in an SPDX document by using a 'LicenseRef-' as the license name’s prefix and including the full license text as per the specification.
## When
* SPDX License List releases are done on a quarterly basis (more or less) at the end of January, April, July, and October. We schedule our License List releases one month behind the usual quarterly calendar cadence to accommodate the reality that many people contributing have other commitments at quarter-end.
* See https://github.com/spdx/license-list-XML/blob/master/RELEASE-NOTES.md for a summary of each release
* See [RELEASE-NOTES.md](RELEASE-NOTES.md) for a summary of each release
* All PRs to be included as part of release must be merged 1 week prior to release date to allow time for actual release work
* Any new issues raised within the month of the next release will likely be tagged for the following release, unless it is an easy-to-resolve issue
@@ -26,7 +26,7 @@ We welcome participants and contributions! The SPDX License List is maintained b
* **calls**: We use conference calls to make decisions on topics and issues that may be difficult to discuss only via email or GitHub. These calls are on the second and fourth Thursday of each month at 12:00 US Eastern Time. Information, including a link to join online, is sent prior to the calls to the SPDX Legal Team mailing list. Meeting minutes for the calls are in the [SPDX meetings repo](https://github.com/spdx/meetings/tree/master/legal); minutes from meetings before March 2020 can be found at http://wiki.spdx.org/
* **this GitHub repo**: We use this repository for comments, issues and pull requests related to specific changes to the files that comprise the SPDX License List. This includes new licenses, updates to an existing license, improvements to documentation and other changes.
Please see [DOCS](https://github.com/spdx/license-list-XML/blob/master/DOCS) and [CONTRIBUTING.md](https://github.com/spdx/license-list-XML/blob/master/CONTRIBUTING.md) for more information. We also have an [FAQ](https://github.com/spdx/license-list-XML/blob/main/DOCS/faq.md) that you may find helpful!
Please see [DOCS](DOCS) and [CONTRIBUTING.md](CONTRIBUTING.md) for more information. We also have an [FAQ](DOCS/faq.md) that you may find helpful!
# Consuming License Data from this Repository
Output files in the [SPDX license-list-data repository](https://github.com/spdx/license-list-data) are generated from the XML source in this repository. These output files are stable and well-supported, and make the License List available in RDFa, HTML, text, and JSON formats. You can use [SPDX tools](https://github.com/spdx/tools) (or create your own) to consume the supported formats of the license list.

65
RELEASE-NOTES.md
View File

@@ -1,5 +1,66 @@
# Release Notes for SPDX License List
## version 3.20 - 2023-02-17
New licenses/exceptions added: 40
1. AdaCore-doc
2. Autoconf-exception-generic
3. BSD-4.3RENO
4. BSD-4.3TAHOE
5. BSD-Advertising-Acknowledgement
6. BSD-Attribution-HPND-disclaimer
7. Bitstream-Charter
8. Brian-Gladman-3-Clause
9. CC-BY-NC-SA-2.0-DE
10. CFITSIO
11. CMU-Mach
12. Clips
13. Cornell-Lossless-JPEG
14. GNAT-exception
15. Graphics-Gems
16. HP-1986
17. HPND-Markus-Kuhn
18. HPND-export-US
19. HPND-sell-variant-MIT-disclaimer
20. IEC-Code-Components-EULA
21. IJG-short
22. JPL-image
23. Kazlib
24. LOOP
25. MIT-Wu
26. Martin-Birgmeier
27. OFFIS
28. OpenPBS-2.3
29. QPL-1.0-INRIA-2004
30. QPL-1.0-INRIA-2004-exception
31. snprintf
32. SunPro
33. SWI-exception
34. Symlinks
35. TPDL
36. TPL-1.0
37. TTWL
38. UCAR
39. w3m
40. xlock
Added historical timeline for the license list.
Recorded and made available links to videos showing two different processes for creating license XML files, and improved related process documentation.
Added and improved markup for many licenses and many minor improvements to other documentation.
Adjusted ListedLicense XSD schema to remove directly-nested lists that had resulted in invalid HTML, and made corresponding fixes to XML for many licenses.
Fixed broken validate-schema CI check and simplified test-one-license script.
Updated to latest version of the License List Publisher.
See all PRs for 3.20 here: https://github.com/spdx/license-list-XML/pulls?page=1&q=is%3Apr+milestone%3A%223.20%22+is%3Aclosed
See comparision of changes from 3.19 to 3.20: https://github.com/spdx/license-list-XML/compare/v3.19...v3.20
## version 3.19 - 2022-11-30
New licenses/exceptions added: 5
@@ -84,7 +145,7 @@ Deprecated licenses/exceptions: 1
1. bzip2-1.0.5
Added documentation describing how to use the Git command line to create and test new license XML files. See https://github.com/spdx/license-list-XML/blob/master/DOCS/git-usage.md for more information.
Added documentation describing how to use the Git command line to create and test new license XML files. See [DOCS/git-usage.md](DOCS/git-usage.md) for more information.
Updates to various documentation, adjustments to markup for various licenses and other minor changes.
@@ -105,7 +166,7 @@ New licenses/exceptions added: 4
Note that "Linux-man-pages-copyleft" was initially merged as "Verbatim-man-pages", but at the community's request the ID was updated prior to inclusion in the release. See https://github.com/spdx/license-list-XML/issues/1310 for more details.
Added template for reviews of new license requests, to evaluate against the license inclusion principles. See https://github.com/spdx/license-list-XML/blob/master/DOCS/submission-response-template.md for the review template.
Added template for reviews of new license requests, to evaluate against the license inclusion principles. See [DOCS/template-license-review-checklist.md](DOCS/template-license-review-checklist.md) for the review template.
Updates to various documentation, adjustments to markup for various licenses and other minor changes.

1
equivalentwords.txt
View File

@@ -23,6 +23,7 @@ labeling,labelling
labor,labour
license,licence
maximize,maximise
merchantability,merchantibility
modeled,modelled
modeling,modelling
noncommercial,non-commercial

19
src/AdaCore-doc.xml Normal file
View File

@@ -0,0 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="AdaCore-doc"
name="AdaCore Doc License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/AdaCore/xmlada/blob/master/docs/index.rst</crossRef>
<crossRef>https://github.com/AdaCore/gnatcoll-core/blob/master/docs/index.rst</crossRef>
<crossRef>https://github.com/AdaCore/gnatcoll-db/blob/master/docs/index.rst</crossRef>
</crossRefs>
<text>
<p>
This document may be copied, in whole or in part, in any form
or by any means, as is or with alterations, provided that
(1) alterations are clearly marked as alterations and (2)
this copyright notice is included unmodified in any copy.
</p>
</text>
</license>
</SPDXLicenseCollection>

23
src/BSD-4.3RENO.xml Normal file
View File

@@ -0,0 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="BSD-4.3RENO"
name="BSD 4.3 RENO License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=libiberty/strcasecmp.c;h=131d81c2ce7881fa48c363dc5bf5fb302c61ce0b;hb=HEAD</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1987 Regents of the University
of California. All rights reserved.
</copyrightText>
<p>
Redistribution and use in source and binary forms are permitted
provided that this notice is preserved and that due credit is
given to the University of California at Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific written prior permission. This
software is provided ``as is'' without express or implied warranty.
</p>
</text>
</license>
</SPDXLicenseCollection>

30
src/BSD-4.3TAHOE.xml Normal file
View File

@@ -0,0 +1,30 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="BSD-4.3TAHOE"
name="BSD 4.3 TAHOE License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/389ds/389-ds-base/blob/main/ldap/include/sysexits-compat.h#L15</crossRef>
</crossRefs>
<notes>
</notes>
<text>
<copyrightText>
Copyright (c) 1987 Regents of the University
of California. All rights reserved.
</copyrightText>
<p>
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph
are duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
</p>
</text>
</license>
</SPDXLicenseCollection>

69
src/BSD-Advertising-Acknowledgement.xml Normal file
View File

@@ -0,0 +1,69 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="BSD-Advertising-Acknowledgement"
name="BSD Advertising Acknowledgement License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/python-excel/xlrd/blob/master/LICENSE#L33</crossRef>
</crossRefs>
<notes>
This appears to be similar BSD-4-Clause, but replaces the
"no endorsement" 4th clause with an attribution clause.
</notes>
<text>
<copyrightText>
Copyright (c) 2001 David Giffin. All rights reserved.
</copyrightText>
<p>
Redistribution and use in source and binary
forms, with or without modification, are permitted
provided that the following conditions are met:
</p>
<list>
<item>
<bullet>1.</bullet>
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
</item>
<item>
<bullet>2.</bullet>
Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or
other materials provided with the distribution.
</item>
<item>
<bullet>3.</bullet>
All advertising materials mentioning features or use of this
software must display the following acknowledgment: "This
product includes software developed by<alt name="nameClause3"
match=".+">David Giffin &lt;david@giffin.org&gt;</alt>
."
</item>
<item>
<bullet>4.</bullet>
Redistributions of any form whatsoever must retain
the following acknowledgment: "This product includes
software developed by<alt name="nameClause4"
match=".+">David Giffin &lt;david@giffin.org&gt;</alt>
."
</item>
</list>
<p>
THIS SOFTWARE IS PROVIDED BY<alt
name="nameDisclaimer" match=".+">DAVID GIFFIN</alt>
``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. IN NO EVENT
SHALL<alt name="nameDisclaimer2" match=".+">DAVID GIFFIN</alt>
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.
</p>
</text>
</license>
</SPDXLicenseCollection>

59
src/BSD-Attribution-HPND-disclaimer.xml Normal file
View File

@@ -0,0 +1,59 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="BSD-Attribution-HPND-disclaimer"
name="BSD with Attribution and HPND disclaimer" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/cyrusimap/cyrus-sasl/blob/master/COPYING</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1998-2003 Carnegie Mellon University. All rights reserved.
</copyrightText>
<p>
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
</p>
<list>
<item>
<bullet>1.</bullet> Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
</item>
<item>
<bullet>2.</bullet> Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
</item>
<item>
<bullet>3.</bullet> The name "Carnegie Mellon University" must not be used to
endorse or promote products derived from this software without
prior written permission. For permission or any other legal
details, please contact<br />
Office of Technology Transfer<br />
Carnegie Mellon University<br />
5000 Forbes Avenue<br />
Pittsburgh, PA 15213-3890<br />
(412) 268-4387, fax: (412) 268-7395<br />
tech-transfer@andrew.cmu.edu<br />
</item>
<item>
<bullet>4.</bullet> Redistributions of any form whatsoever must retain the following
acknowledgment:<br />
"This product includes software developed by Computing Services<br />
at Carnegie Mellon University (http://www.cmu.edu/computing/)."<br />
</item>
</list>
<p>
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
</p>
</text>
</license>
</SPDXLicenseCollection>

50
src/Brian-Gladman-3-Clause.xml Normal file
View File

@@ -0,0 +1,50 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="Brian-Gladman-3-Clause"
name="Brian Gladman 3-Clause License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/SWI-Prolog/packages-clib/blob/master/sha1/brg_endian.h</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 2003, Dr Brian Gladman, Worcester, UK. All rights reserved.
</copyrightText>
<p>
LICENSE TERMS
</p>
<p>
The free distribution and use of this software in both source and binary
form is allowed (with or without changes) provided that:
</p>
<list>
<item>
<bullet>1.</bullet> distributions of this source code include the above copyright
notice, this list of conditions and the following disclaimer;
</item>
<item>
<bullet>2.</bullet> distributions in binary form include the above copyright
notice, this list of conditions and the following disclaimer
in the documentation and/or other associated materials;
</item>
<item>
<bullet>3.</bullet> the copyright holder's name is not used to endorse products
built using this software without specific written permission.
</item>
</list>
<p>
ALTERNATIVELY, provided that this notice is retained in full, this product
may be distributed under the terms of the GNU General Public License (GPL),
in which case the provisions of the GPL apply INSTEAD OF those given above.
</p>
<p>
DISCLAIMER
</p>
<p>
This software is provided 'as is' with no explicit or implied warranties
in respect of its properties, including, but not limited to, correctness
and/or fitness for purpose.
</p>
</text>
</license>
</SPDXLicenseCollection>

46
src/CFITSIO.xml Normal file
View File

@@ -0,0 +1,46 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="CFITSIO"
name="CFITSIO License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://heasarc.gsfc.nasa.gov/docs/software/fitsio/c/f_user/node9.html</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (Unpublished-all rights reserved under the
copyright laws of the United States), U.S. Government
as represented by the Administrator of the National
Aeronautics and Space Administration. No copyright is
claimed in the United States under Title 17, U.S. Code.
</copyrightText>
<p>
Permission to freely use, copy, modify, and distribute
this software and its documentation without fee is
hereby granted, provided that this copyright notice
and disclaimer of warranty appears in all copies.
</p>
<p>
DISCLAIMER:
</p>
<p>
THE SOFTWARE IS PROVIDED 'AS IS' WITHOUT ANY WARRANTY OF ANY KIND,
EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED
TO, ANY WARRANTY THAT THE SOFTWARE WILL CONFORM TO SPECIFICATIONS,
ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND FREEDOM FROM INFRINGEMENT, AND ANY WARRANTY THAT THE
DOCUMENTATION WILL CONFORM TO THE SOFTWARE, OR ANY WARRANTY THAT
THE SOFTWARE WILL BE ERROR FREE. IN NO EVENT SHALL NASA BE LIABLE
FOR ANY DAMAGES, INCLUDING, BUT NOT LIMITED TO, DIRECT, INDIRECT,
SPECIAL OR CONSEQUENTIAL DAMAGES, ARISING OUT OF, RESULTING
FROM, OR IN ANY WAY CONNECTED WITH THIS SOFTWARE, WHETHER OR NOT
BASED UPON WARRANTY, CONTRACT, TORT , OR OTHERWISE, WHETHER OR
NOT INJURY WAS SUSTAINED BY PERSONS OR PROPERTY OR OTHERWISE,
AND WHETHER OR NOT LOSS WAS SUSTAINED FROM, OR AROSE OUT OF THE
RESULTS OF, OR USE OF, THE SOFTWARE OR SERVICES PROVIDED HEREUNDER.
<optional>
"
</optional>
</p>
</text>
</license>
</SPDXLicenseCollection>

41
src/CMU-Mach.xml Normal file
View File

@@ -0,0 +1,41 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="CMU-Mach"
name="CMU Mach License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://www.cs.cmu.edu/~410/licenses.html</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1991,1990,1989 Carnegie
Mellon University All Rights Reserved.
</copyrightText>
<p>
Permission to use, copy, modify and distribute this software and its
documentation is hereby granted, provided that both the copyright
notice and this permission notice appear in all copies of the
software, derivative works or modified versions, and any portions
thereof, and that both notices appear in supporting documentation.
</p>
<p>
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
</p>
<optional>
<p>
Carnegie Mellon requests users of this software to return to
</p>
<p>
Software Distribution Coordinator or
Software.Distribution@CS.CMU.EDU School of Computer
Science Carnegie Mellon University Pittsburgh PA 15213-3890
</p>
<p>
any improvements or extensions that they make and grant
Carnegie Mellon the rights to redistribute these changes.
</p>
</optional>
</text>
</license>
</SPDXLicenseCollection>

27
src/Clips.xml Normal file
View File

@@ -0,0 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="Clips" name="Clips License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/DrItanium/maya/blob/master/LICENSE.CLIPS</crossRef>
</crossRefs>
<text>
<p>
Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT
SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR
CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
</p>
</text>
</license>
</SPDXLicenseCollection>

36
src/Cornell-Lossless-JPEG.xml Normal file
View File

@@ -0,0 +1,36 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="Cornell-Lossless-JPEG"
name="Cornell Lossless JPEG License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://android.googlesource.com/platform/external/dng_sdk/+/refs/heads/master/source/dng_lossless_jpeg.cpp#16</crossRef>
<crossRef>https://www.mssl.ucl.ac.uk/~mcrw/src/20050920/proto.h</crossRef>
<crossRef>https://gitlab.freedesktop.org/libopenraw/libopenraw/blob/master/lib/ljpegdecompressor.cpp#L32</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1993 Cornell University, Kongji Huang<br />
All rights reserved.
</copyrightText>
<p>Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without written
agreement is hereby granted, provided that the above copyright notice
and the following two paragraphs appear in all copies of this
software.</p>
<p>IN NO EVENT SHALL <alt match=".+" name="disclaimer1">THE CORNELL UNIVERSITY</alt> BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF <alt match=".+" name="disclaimer2">CORNELL
UNIVERSITY</alt> HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p>
<p><alt match=".+" name="disclaimer3">THE CORNELL UNIVERSITY</alt> SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND <alt match=".+" name="disclaimer4">CORNELL UNIVERSITY</alt> HAS
NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,
OR MODIFICATIONS.</p>
</text>
</license>
</SPDXLicenseCollection>

25
src/HP-1986.xml Normal file
View File

@@ -0,0 +1,25 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="HP-1986"
name="Hewlett-Packard 1986 License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/machine/hppa/memchr.S;h=1cca3e5e8867aa4bffef1f75a5c1bba25c0c441e;hb=HEAD#l2</crossRef>
</crossRefs>
<text>
<copyrightText>
(c) Copyright 1986 HEWLETT-PACKARD COMPANY
</copyrightText>
<p>
To anyone who acknowledges that this file is provided "AS IS"
without any express or implied warranty: permission to use, copy,
modify, and distribute this file for any purpose is hereby granted
without fee, provided that the above copyright notice and this
notice appears in all copies, and that the name of Hewlett-Packard
Company not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission. Hewlett-Packard Company makes no representations
about the suitability of this software for any purpose.
</p>
</text>
</license>
</SPDXLicenseCollection>

17
src/HPND-Markus-Kuhn.xml Normal file
View File

@@ -0,0 +1,17 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="HPND-Markus-Kuhn"
name="Historical Permission Notice and Disclaimer - Markus Kuhn variant" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c</crossRef>
<crossRef>https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=readline/readline/support/wcwidth.c;h=0f5ec995796f4813abbcf4972aec0378ab74722a;hb=HEAD#l55</crossRef>
</crossRefs>
<text>
<p>
Permission to use, copy, modify, and distribute this software
for any purpose and without fee is hereby granted. The author
disclaims all warranties with regard to this software.
</p>
</text>
</license>
</SPDXLicenseCollection>

38
src/HPND-sell-variant-MIT-disclaimer.xml Normal file
View File

@@ -0,0 +1,38 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="HPND-sell-variant-MIT-disclaimer"
name="HPND sell variant with MIT disclaimer" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/sigmavirus24/x11-ssh-askpass/blob/master/README</crossRef>
</crossRefs>
<notes>
This license is comprised of parts of the permission
language from HPND-sell-variant and the disclaimer from MIT.
</notes>
<text>
<copyrightText>
by Jim Knoble &lt;jmknoble@pobox.com&gt;
Copyright (C) 1999,2000,2001 Jim Knoble
</copyrightText>
<p>
Permission to use, copy, modify, distribute, and sell this
software and its documentation for any purpose is hereby
granted without fee, provided that the above copyright notice
appear in all copies and that both that copyright notice and
this permission notice appear in supporting documentation.
</p>
<p>
+------------+ | Disclaimer | +------------+
</p>
<p>
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
express or implied, including but not limited to the warranties
of merchantability, fitness for a particular purpose and
noninfringement. In no event shall the author(s) be liable for
any claim, damages or other liability, whether in an action of
contract, tort or otherwise, arising from, out of or in connection
with the software or the use or other dealings in the software.
</p>
</text>
</license>
</SPDXLicenseCollection>

89
src/IEC-Code-Components-EULA.xml Normal file
View File

@@ -0,0 +1,89 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="IEC-Code-Components-EULA" name="IEC
Code Components End-user licence agreement" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://www.iec.ch/webstore/custserv/pdf/CC-EULA.pdf</crossRef>
<crossRef>https://www.iec.ch/CCv1</crossRef>
<crossRef>https://www.iec.ch/copyright</crossRef>
</crossRefs>
<text>
<titleText>IEC Code Components End-user licence
agreement</titleText>
<p>
Code Components in IEC standards (International Standards,
Technical Specifications or Technical Reports) which
have been identified and approved for licensing,
are licensed subject to the following conditions:
</p>
<list>
<item>
<bullet>-</bullet>
<p>
Redistributions of software must retain the
Copyright Notice, this list of conditions
and the disclaimer below (“Disclaimer”).
</p>
</item>
<item>
<bullet>-</bullet>
<p>
The software license extends to modifications
permitted under the relevant IEC standard.
</p>
</item>
<item>
<bullet>-</bullet>
<p>
The software license extends to clarifications
and corrections approved by IEC.
</p>
</item>
<item>
<bullet>-</bullet>
<p>
Neither the name of IEC, nor the names of specific
contributors, may be used to endorse or promote products
derived from this software without specific prior written
permission. The relevant IEC standard may be referenced
when claiming compliance with the relevant IEC standard.
</p>
</item>
<item>
<bullet>-</bullet>
<p>
The user of Code Components shall attribute each such Code
Component to IEC and identify the IEC standard from which
it is taken. Such attribution (e.g., “This code was derived
from IEC [insert standard reference number:publication
year] within modifications permitted in the relevant IEC
standard. Please reproduce this note if possible.”), may be
placed in the code itself or any other reasonable location.
</p>
</item>
</list>
<p>
Code Components means components included in IEC standards
that are intended to be directly processed by a computer
and also includes any text found between the markers
&lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt;, or otherwise
clearly labeled in this standard as a Code Component.
</p>
<p>
The Disclaimer is: EACH OF THE CODE COMPONENTS IS PROVIDED BY
THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR 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 THE CODE
COMPONENTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
</p>
</text>
</license>
</SPDXLicenseCollection>

114
src/JPL-image.xml Normal file
View File

@@ -0,0 +1,114 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="JPL-image"
name="JPL Image Use Policy" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://www.jpl.nasa.gov/jpl-image-use-policy</crossRef>
</crossRefs>
<text>
<titleText>
JPL Image Use Policy
</titleText>
<p>
Unless otherwise noted, images and video on JPL public web sites
(public sites ending with a jpl.nasa.gov address) may be used
for any purpose without prior permission, subject to the special
cases noted below. Publishers who wish to have authorization
may print this page and retain it for their records; JPL
does not issue image permissions on an image by image basis.
</p>
<p>
By electing to download the material
from this web site the user agrees:
</p>
<list>
<item>
<bullet>1.</bullet>
that Caltech makes no representations or warranties with respect
to ownership of copyrights in the images, and does not represent
others who may claim to be authors or owners of copyright of any
of the images, and makes no warranties as to the quality of the
images. Caltech shall not be responsible for any loss or expenses
resulting from the use of the images, and you release and hold
Caltech harmless from all liability arising from such use.
</item>
<item>
<bullet>2.</bullet>
to use a credit line in connection with images. Unless
otherwise noted in the caption information for an image,
the credit line should be "Courtesy NASA/JPL-Caltech."
</item>
<item>
<bullet>3.</bullet>
that the endorsement of any product or service by
Caltech, JPL or NASA must not be claimed or implied.
</item>
</list>
<p>
Special Cases:
</p>
<list>
<item>
<bullet>*</bullet>
<p>
Prior written approval must be obtained to use the NASA
insignia logo (the blue "meatball" insignia), the NASA
logotype (the red "worm" logo) and the NASA seal. These
images may not be used by persons who are not NASA employees
or on products (including Web pages) that are not NASA
sponsored. In addition, no image may be used to explicitly
or implicitly suggest endorsement by NASA, JPL or Caltech of
commercial goods or services. Requests to use NASA logos may
be directed to Bert Ulrich, Public Services Division, NASA
Headquarters, Code POS, Washington, DC 20546, telephone (202)
358-1713, fax (202) 358-4331, email bert.ulrich@hq.nasa.gov.
</p>
</item>
<item>
<bullet>*</bullet>
<p>
Prior written approval must be obtained to use the JPL logo
(stylized JPL letters in red or other colors). Requests
to use the JPL logo may be directed to the Institutional
Communications Office, email instcomm@jpl.nasa.gov.
</p>
</item>
<item>
<bullet>*</bullet>
<p>
If an image includes an identifiable person, using the
image for commercial purposes may infringe that person's
right of privacy or publicity, and permission should
be obtained from the person. NASA and JPL generally do
not permit likenesses of current employees to appear
on commercial products. For more information, consult
the NASA and JPL points of contact listed above.
</p>
</item>
<item>
<bullet>*</bullet>
<p>
JPL/Caltech contractors and vendors who wish to
use JPL images in advertising or public relation
materials should direct requests to the Institutional
Communications Office, email instcomm@jpl.nasa.gov.
</p>
</item>
<item>
<bullet>*</bullet>
<p>
Some image and video materials on JPL public web sites
are owned by organizations other than JPL or NASA.
These owners have agreed to make their images and video
available for journalistic, educational and personal
uses, but restrictions are placed on commercial uses.
To obtain permission for commercial use, contact the
copyright owner listed in each image caption. Ownership
of images and video by parties other than JPL and
NASA is noted in the caption material with each image.
</p>
</item>
</list>
</text>
</license>
</SPDXLicenseCollection>

29
src/Kazlib.xml Normal file
View File

@@ -0,0 +1,29 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="Kazlib"
name="Kazlib License" listVersionAdded="3.20">
<crossRefs>
<crossRef>http://git.savannah.gnu.org/cgit/kazlib.git/tree/except.c?id=0062df360c2d17d57f6af19b0e444c51feb99036</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (C) 1999 Kaz Kylheku &lt;kaz@ashi.footprints.net&gt;
</copyrightText>
<p>
Free Software License:
</p>
<p>
All rights are reserved by the author, with the following
exceptions: Permission is granted to freely reproduce and distribute
this software, possibly in exchange for a fee, provided that
this copyright notice appears intact. Permission is also granted
to adapt this software to produce derivative works, as long as
the modified versions carry this copyright notice and additional
notices stating that the work has been modified. This source
code may be translated into executable form and incorporated
into proprietary software; there is no requirement for such
software to contain a copyright notice related to this source.
</p>
</text>
</license>
</SPDXLicenseCollection>

24
src/Martin-Birgmeier.xml Normal file
View File

@@ -0,0 +1,24 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="Martin-Birgmeier"
name="Martin Birgmeier License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/Perl/perl5/blob/blead/util.c#L6136</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1993 Martin Birgmeier All rights reserved.
</copyrightText>
<p>
You may redistribute unmodified or modified versions of
this source code provided that the above copyright notice
and this and the following conditions are retained.
</p>
<p>
This software is provided ``as is'', and comes with no warranties
of any kind. I shall in no event be liable for anything
that happens to anyone/anything when using this software.
</p>
</text>
</license>
</SPDXLicenseCollection>

33
src/OFFIS.xml Normal file
View File

@@ -0,0 +1,33 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="OFFIS"
name="OFFIS License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://sourceforge.net/p/xmedcon/code/ci/master/tree/libs/dicom/README</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (C) 1994-2001, OFFIS
</copyrightText>
This software and supporting documentation were developed
by <br/>Kuratorium OFFIS e.V. Healthcare Information and
Communication Systems <br/>Escherweg 2 <br/>D-26121 Oldenburg, Germany
<p>
THIS SOFTWARE IS MADE AVAILABLE, AS IS, AND OFFIS MAKES NO WARRANTY
REGARDING THE SOFTWARE, ITS PERFORMANCE, ITS MERCHANTABILITY
OR FITNESS FOR ANY PARTICULAR USE, FREEDOM FROM ANY COMPUTER
DISEASES OR ITS CONFORMITY TO ANY SPECIFICATION. THE ENTIRE RISK
AS TO QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH THE USER.
</p>
<p>
Copyright of the software and supporting documentation is, unless
otherwise stated, owned by OFFIS, and free access is hereby granted
as a license to use this software, copy this software and prepare
derivative works based upon this software. However, any distribution
of this software source code or supporting documentation or
derivative works (source code and supporting documentation)
must include the three paragraphs of this copyright notice.
</p>
</text>
</license>
</SPDXLicenseCollection>

137
src/OpenPBS-2.3.xml Normal file
View File

@@ -0,0 +1,137 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="OpenPBS-2.3"
name="OpenPBS v2.3 Software License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/adaptivecomputing/torque/blob/master/PBS_License.txt</crossRef>
<crossRef>https://www.mcs.anl.gov/research/projects/openpbs/PBS_License.txt</crossRef>
</crossRefs>
<text>
<titleText>
OpenPBS (Portable Batch System) v2.3 Software License
</titleText>
<copyrightText>
Copyright (c) 1999-2000 Veridian Information
Solutions, Inc. All rights reserved.
</copyrightText>
<optional>
---------------------------------------------------------------------------
<p>
For a license to use or redistribute the OpenPBS software
under conditions other than those described below, or
to purchase support for this software, please contact
Veridian Systems, PBS Products Department ("Licensor") at:
</p>
<p>
www.OpenPBS.org +1 650 967-4675
sales@OpenPBS.org 877 902-4PBS (US toll-free)
</p>
---------------------------------------------------------------------------
</optional>
<p>
This license covers use of the OpenPBS v2.3 software (the
"Software") at your site or location, and, for certain
users, redistribution of the Software to other sites and
locations. Use and redistribution of OpenPBS v2.3 in source
and binary forms, with or without modification, are permitted
provided that all of the following conditions are met.
After December 31, 2001, only conditions 3-6 must be met:
</p>
<list>
<item>
<bullet>1.</bullet>
<p>
Commercial and/or non-commercial use of the Software
is permitted provided a current software registration
is on file at www.OpenPBS.org. If use of this software
contributes to a publication, product, or service, proper
attribution must be given; see www.OpenPBS.org/credit.html
</p>
</item>
<item>
<bullet>2.</bullet>
<p>
Redistribution in any form is only permitted for
non-commercial, non-profit purposes. There can be no
charge for the Software or any software incorporating the
Software. Further, there can be no expectation of revenue
generated as a consequence of redistributing the Software.
</p>
</item>
<item>
<bullet>3.</bullet>
<p>
Any Redistribution of source code must retain
the above copyright notice and the acknowledgment
contained in paragraph 6, this list of conditions
and the disclaimer contained in paragraph 7.
</p>
</item>
<item>
<bullet>4.</bullet>
<p>
Any Redistribution in binary form must reproduce the
above copyright notice and the acknowledgment contained
in paragraph 6, this list of conditions and the
disclaimer contained in paragraph 7 in the documentation
and/or other materials provided with the distribution.
</p>
</item>
<item>
<bullet>5.</bullet>
<p>
Redistributions in any form must be accompanied by information
on how to obtain complete source code for the OpenPBS
software and any modifications and/or additions to the
OpenPBS software. The source code must either be included in
the distribution or be available for no more than the cost
of distribution plus a nominal fee, and all modifications
and additions to the Software must be freely redistributable
by any party (including Licensor) without restriction.
</p>
</item>
<item>
<bullet>6.</bullet>
<p>
All advertising materials mentioning features or use of
the Software must display the following acknowledgment:
</p>
<p>
"This product includes software developed by NASA Ames
Research Center, Lawrence Livermore National Laboratory, and
Veridian Information Solutions, Inc. Visit www.OpenPBS.org
for OpenPBS software support, products, and information."
</p>
</item>
<item>
<bullet>7.</bullet>
<p>
DISCLAIMER OF WARRANTY
</p>
<p>
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NON-INFRINGEMENT ARE EXPRESSLY DISCLAIMED.
</p>
</item>
</list>
<p>
IN NO EVENT SHALL VERIDIAN CORPORATION, ITS AFFILIATED COMPANIES,
OR THE U.S. GOVERNMENT OR ANY OF ITS AGENCIES BE LIABLE FOR
ANY DIRECT OR 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.
</p>
<p>
This license will be governed by the laws of the Commonwealth
of Virginia, without reference to its choice of law rules.
</p>
</text>
</license>
</SPDXLicenseCollection>

40
src/PSF-2.0.xml
View File

@@ -15,43 +15,41 @@
<list>
<item>
<bullet>1.</bullet>
This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the
Individual or Organization ("Licensee") accessing and otherwise using this software
("Python") in source or binary form and its associated documentation.
This LICENSE AGREEMENT is between the <alt match=".*" name="copyrightHolder0">Python Software Foundation ("PSF"),</alt> and the
Individual or Organization ("Licensee") accessing and otherwise using <alt match=".*" name="software0">this software
("Python")</alt> in source or binary form and its associated documentation.
</item>
<item>
<bullet>2.</bullet>
Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee
Subject to the terms and conditions of this License Agreement, <alt match=".*" name="copyrightHolder1">PSF</alt> hereby <alt match="grant|grants" name="grantPlural">grants</alt> Licensee
a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform
and/or display publicly, prepare derivative works, distribute, and otherwise use Python
alone or in any derivative version, provided, however, that PSF's License Agreement and
PSF's notice of copyright, i.e., "Copyright (c)
<alt match="([0-9]{4},\s)*[0-9]{4}" name="exampleCopyrightYears">
2001, 2002, 2003, 2004, 2005, 2006
</alt>
Python Software Foundation; All Rights Reserved" are retained in Python alone or in any
and/or display publicly, prepare derivative works, distribute, and otherwise use <alt match=".*" name="software1">Python</alt>
alone or in any derivative version, provided, however, that <alt match=".*" name="copyrightHolder2">PSF's</alt> License Agreement and
<alt match=".*" name="copyrightHolder3">PSF's</alt> notice of copyright<alt match=".*" name="copyrightHolder4">, i.e., "Copyright (c)
2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation All Rights Reserved"</alt> are retained in <alt match=".*" name="software2">Python</alt> alone or in any
derivative version prepared by Licensee.
</item>
<item>
<bullet>3.</bullet>
In the event Licensee prepares a derivative work that is based on or incorporates Python
In the event Licensee prepares a derivative work that is based on or incorporates <alt match=".*" name="software3">Python</alt>
or any part thereof, and wants to make the derivative work available to others as provided
herein, then Licensee hereby agrees to include in any such work a brief summary of the
changes made to Python.
changes made to <alt match=".*" name="software4">Python</alt>.
</item>
<item>
<bullet>4.</bullet>
PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO
<alt match=".*" name="copyrightHolder5">PSF is</alt> making <alt match=".*" name="software5">Python</alt>
available to Licensee on an "AS IS" basis. <alt match=".*" name="copyrightHolder6">PSF</alt> <alt match="MAKE|MAKES" name="makePlural1">MAKES</alt> NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION,
PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY
<alt match=".*" name="copyrightHolder7">PSF</alt> <alt match="MAKE|MAKES" name="makePlural2">MAKES</alt> NO AND <alt match="DISCLAIM|DISCLAIMS" name="disclaimPlural">DISCLAIMS</alt> ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF <alt match=".*" name="software6">PYTHON</alt> WILL NOT INFRINGE ANY THIRD PARTY
RIGHTS.
</item>
<item>
<bullet>5.</bullet>
PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL,
<alt match=".*" name="copyrightHolder8">PSF</alt> SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF <alt match=".*" name="software7">PYTHON</alt> FOR ANY INCIDENTAL,
SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR
OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY
OTHERWISE USING <alt match=".*" name="software8">PYTHON</alt>, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY
THEREOF.
</item>
<item>
@@ -62,13 +60,13 @@
<item>
<bullet>7.</bullet>
Nothing in this License Agreement shall be deemed to create any relationship of agency,
partnership, or joint venture between PSF and Licensee. This License Agreement does not
grant permission to use PSF trademarks or trade name in a trademark sense to endorse or
partnership, or joint venture between <alt match=".*" name="copyrightHolder9">PSF</alt> and Licensee. This License Agreement does not
grant permission to use <alt match=".*" name="copyrightHolder10">PSF</alt> trademarks or trade name in a trademark sense to endorse or
promote products or services of Licensee, or any third party.
</item>
<item>
<bullet>8.</bullet>
By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms
By copying, installing or otherwise using <alt match=".*" name="software9">Python</alt>, Licensee agrees to be bound by the terms
and conditions of this License Agreement.
</item>
</list>

129
src/QPL-1.0-INRIA-2004.xml Normal file
View File

@@ -0,0 +1,129 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="QPL-1.0-INRIA-2004"
name="Q Public License 1.0 - INRIA 2004 variant" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/maranget/hevea/blob/master/LICENSE</crossRef>
</crossRefs>
<notes>
This license is a variant of QPL-1.0 with the choice of law changed to France. This variant
appears to be generally used together with QPL-1.0-INRIA-2004-exception.
</notes>
<text>
<titleText>
<p>THE Q PUBLIC LICENSE version 1.0</p>
</titleText>
<copyrightText>
<p>Copyright (C) 1999 Troll Tech AS, Norway.</p>
</copyrightText>
<p>Everyone is permitted to copy and distribute this license document.</p>
<p>The intent of this license is to establish freedom to share and change the software regulated by this
license under the open source model.</p>
<p>This license applies to any software containing a notice placed by the copyright holder saying that it
may be distributed under the terms of the Q Public License version 1.0. Such software is herein
referred to as the Software. This license covers modification and distribution of the Software, use of
third-party application programs based on the Software, and development of free software which uses
the Software.</p>
<p>Granted Rights</p>
<list>
<item>
<bullet>1.</bullet>
You are granted the non-exclusive rights set forth in this license provided you agree to and
comply with any and all conditions in this license. Whole or partial distribution of the
Software, or software items that link with the Software, in any form signifies acceptance of
this license.
</item>
<item>
<bullet>2.</bullet>
You may copy and distribute the Software in unmodified form provided that the entire package,
including - but not restricted to - copyright, trademark notices and disclaimers, as released
by the initial developer of the Software, is distributed.
</item>
<item>
<bullet>3.</bullet>
You may make modifications to the Software and distribute your modifications, in a form that is
separate from the Software, such as patches. The following restrictions apply to
modifications:
<list>
<item>
<bullet>a.</bullet>
Modifications must not alter or remove any copyright notices in the Software.
</item>
<item>
<bullet>b.</bullet>
When modifications to the Software are released under this license, a non-exclusive royalty-free
right is granted to the initial developer of the Software to distribute your modification in
future versions of the Software provided such versions remain available under these terms in
addition to any other license(s) of the initial developer.
</item>
</list>
</item>
<item>
<bullet>4.</bullet>
You may distribute machine-executable forms of the Software or machine-executable forms of
modified versions of the Software, provided that you meet these restrictions:
<list>
<item>
<bullet>a.</bullet>
You must include this license document in the distribution.
</item>
<item>
<bullet>b.</bullet>
You must ensure that all recipients of the machine-executable forms are also able to receive the
complete machine-readable source code to the distributed Software, including all
modifications, without any charge beyond the costs of data transfer, and place prominent
notices in the distribution explaining this.
</item>
<item>
<bullet>c.</bullet>
You must ensure that all modifications included in the machine-executable forms are available
under the terms of this license.
</item>
</list>
</item>
<item>
<bullet>5.</bullet>
You may use the original or modified versions of the Software to compile, link and run
application programs legally developed by you or by others.
</item>
<item>
<bullet>6.</bullet>
You may develop application programs, reusable components and other software items that link with
the original or modified versions of the Software. These items, when distributed, are subject
to the following requirements:
<list>
<item>
<bullet>a.</bullet>
You must ensure that all recipients of machine-executable forms of these items are also able to
receive and use the complete machine-readable source code to the items without any charge
beyond the costs of data transfer.
</item>
<item>
<bullet>b.</bullet>
You must explicitly license all recipients of your items to use and re-distribute original and
modified versions of the items in both machine-executable and source code forms. The
recipients must be able to do so without any charges whatsoever, and they must be able to
re-distribute to anyone they choose.
</item>
<item>
<bullet>c.</bullet>
If the items are not available to the general public, and the initial developer of the Software
requests a copy of the items, then you must supply one.
</item>
</list>
</item>
</list>
<p>Limitations of Liability</p>
<p>In no event shall the initial developers or copyright holders be liable for any damages whatsoever,
including - but not restricted to - lost revenue or profits or other direct, indirect, special,
incidental or consequential damages, even if they have been advised of the possibility of such
damages, except to the extent invariable law, if any, provides otherwise.</p>
<p>No Warranty</p>
<p>The Software and this license document are provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.</p>
<p>Choice of Law</p>
<p>This license is governed by the Laws of France.</p>
</text>
</license>
</SPDXLicenseCollection>

18
src/Saxpath.xml
View File

@@ -27,22 +27,26 @@
</item>
<item>
<bullet>3.</bullet>
The name "SAXPath" must not be used to endorse or promote products derived from this software
The name <alt match=".+" name="nameClause3">"SAXPath"</alt> must not be used
to endorse or promote products derived from this software
without prior written permission. For written permission, please contact
license@saxpath.org.
<alt match=".+" name="contactClause3">license@saxpath.org</alt>.
</item>
<item>
<bullet>4.</bullet>
Products derived from this software may not be called "SAXPath", nor may "SAXPath" appear in
their name, without prior written permission from the SAXPath Project Management
(pm@saxpath.org).
Products derived from this software may not be called <alt match=".+" name="nameClause4">"SAXPath"</alt>,
nor may <alt match=".+" name="nameClause42">"SAXPath"</alt> appear in
their name, without prior written permission from the <alt match=".+" name="contactClause4">SAXPath Project Management
(pm@saxpath.org)</alt>.
</item>
</list>
<p>In addition, we request (but do not require) that you include in the end-user documentation provided with
the redistribution and/or in the software itself an acknowledgement equivalent to the following:
<br/>"This product includes software developed by the SAXPath Project (http://www.saxpath.org/)."
<br/>"This product includes software developed by
<alt match=".+" name="acknowledgement">the SAXPath Project (http://www.saxpath.org/)</alt>."
</p>
<p>Alternatively, the acknowledgment may be graphical using the logos available at http://www.saxpath.org/</p>
<p>Alternatively, the acknowledgment may be graphical using the logos available at
<alt match=".+" name="logos">http://www.saxpath.org/</alt></p>
<p>THIS SOFTWARE IS PROVIDED ``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. IN
NO EVENT SHALL THE SAXPath AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,

27
src/SunPro.xml Normal file
View File

@@ -0,0 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="SunPro"
name="SunPro License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/freebsd/freebsd-src/blob/main/lib/msun/src/e_acosh.c</crossRef>
<crossRef>https://github.com/freebsd/freebsd-src/blob/main/lib/msun/src/e_lgammal.c</crossRef>
</crossRefs>
<standardLicenseHeader>
</standardLicenseHeader>
<notes>
</notes>
<text>
<copyrightText>
Copyright (C) 1993 by Sun Microsystems, Inc. All rights reserved.
</copyrightText>
<p>
Developed at<alt name="SunOrg" match="SunPro|SunSoft">SunPro</alt>
, a Sun Microsystems, Inc. business.
</p>
<p>
Permission to use, copy, modify, and distribute this software
is freely granted, provided that this notice is preserved.
</p>
</text>
</license>
</SPDXLicenseCollection>

768
src/TPL-1.0.xml Normal file
View File

@@ -0,0 +1,768 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="TPL-1.0"
name="THOR Public License 1.0" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://fedoraproject.org/wiki/Licensing:ThorPublicLicense</crossRef>
</crossRefs>
<notes>
This license is the same as MPL-1.1 (and CUA-OPL-1.0) except for
the name and the choice of law (Germany, instead of California)
</notes>
<text>
<titleText>
THOR Public Licence (TPL)
</titleText>
<list>
<item>
<bullet>0.</bullet>
<p>
Notes of Origin
</p>
</item>
<item>
<bullet>0.1</bullet>
<p>
As required by paragraph 6.3 of the "Mozilla Public
Licence", "MPL" in the following, it is hereby stated
that this Licence condition ("TPL") differs in the
following items from the original "Mozilla Public Licence"
as provided by "Netscape Communications Corporation":
</p>
</item>
<item>
<bullet>a)</bullet>
<p>
Paragraphs 6.2 and 6.3 of the MPL has been
modified to bind licence modifications to
the Author of this Licence, Thomas Richter.
</p>
</item>
<item>
<bullet>b)</bullet>
<p>
Paragraph 11 has been modified to gover this
Licence by German law rather than Californian Law.
</p>
</item>
<item>
<bullet>c)</bullet>
<p>
The licence has been renamed to "TPL" and "THOR Public
Licence". All references towards "MPL" have been removed
except in section 0 to indicate the difference from "MPL".
</p>
<p>
No other modifications have been made.
</p>
</item>
<item>
<bullet>1.</bullet>
<p>
Definitions.
</p>
<p>
1.0.1. "Commercial Use" means distribution or otherwise
making the Covered Code available to a third party.
</p>
</item>
<item>
<bullet>1.1.</bullet>
<p>
"Contributor" means each entity that creates or
contributes to the creation of Modifications.
</p>
</item>
<item>
<bullet>1.2.</bullet>
<p>
"Contributor Version" means the combination of the Original
Code, prior Modifications used by a Contributor, and
the Modifications made by that particular Contributor.
</p>
</item>
<item>
<bullet>1.3.</bullet>
<p>
"Covered Code" means the Original Code or Modifications
or the combination of the Original Code and
Modifications, in each case including portions thereof.
</p>
</item>
<item>
<bullet>1.4.</bullet>
<p>
"Electronic Distribution Mechanism" means a mechanism
generally accepted in the software development
community for the electronic transfer of data.
</p>
</item>
<item>
<bullet>1.5.</bullet>
<p>
"Executable" means Covered Code in
any form other than Source Code.
</p>
</item>
<item>
<bullet>1.6.</bullet>
<p>
"Initial Developer" means the individual or
entity identified as the Initial Developer in
the Source Code notice required by Exhibit A.
</p>
</item>
<item>
<bullet>1.7.</bullet>
<p>
"Larger Work" means a work which combines
Covered Code or portions thereof with code
not governed by the terms of this License.
</p>
</item>
<item>
<bullet>1.8.</bullet>
<p>
"License" means this document.
</p>
<p>
1.8.1. "Licensable" means having the right to
grant, to the maximum extent possible, whether
at the time of the initial grant or subsequently
acquired, any and all of the rights conveyed herein.
</p>
</item>
<item>
<bullet>1.9.</bullet>
<p>
"Modifications" means any addition to or deletion from
the substance or structure of either the Original Code
or any previous Modifications. When Covered Code is
released as a series of files, a Modification is: A.
Any addition to or deletion from the contents of a file
containing Original Code or previous Modifications.
</p>
</item>
<item>
<bullet>B.</bullet>
<p>
Any new file that contains any part of the Original Code or
previous Modifications. 1.10. "Original Code" means Source
Code of computer software code which is described in the
Source Code notice required by Exhibit A as Original Code,
and which, at the time of its release under this License
is not already Covered Code governed by this License.
</p>
<p>
1.10.1. "Patent Claims" means any patent claim(s),
now owned or hereafter acquired, including
without limitation, method, process, and apparatus
claims, in any patent Licensable by grantor.
</p>
</item>
<item>
<bullet>1.11.</bullet>
<p>
"Source Code" means the preferred form of the Covered
Code for making modifications to it, including all
modules it contains, plus any associated interface
definition files, scripts used to control compilation and
installation of an Executable, or source code differential
comparisons against either the Original Code or another
well known, available Covered Code of the Contributor's
choice. The Source Code can be in a compressed or
archival form, provided the appropriate decompression or
de-archiving software is widely available for no charge.
</p>
</item>
<item>
<bullet>1.12.</bullet>
<p>
"You" (or "Your") means an individual or a legal entity
exercising rights under, and complying with all of
the terms of, this License or a future version of this
License issued under Section 6.1. For legal entities,
"You" includes any entity which controls, is controlled
by, or is under common control with You. For purposes
of this definition, "control" means (a) the power,
direct or indirect, to cause the direction or management
of such entity, whether by contract or otherwise, or
(b) ownership of more than fifty percent (50%) of the
outstanding shares or beneficial ownership of such entity.
</p>
</item>
<item>
<bullet>2.</bullet>
<p>
Source Code License.
</p>
</item>
<item>
<bullet>2.1.</bullet>
<p>
The Initial Developer Grant. The Initial Developer hereby
grants You a world-wide, royalty-free, non-exclusive
license, subject to third party intellectual property
claims: (a) 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
</p>
</item>
<item>
<bullet>(b)</bullet>
<p>
under Patents Claims infringed by the making, using
or selling of Original Code, to make, have made, use,
practice, sell, and offer for sale, and/or otherwise
dispose of the Original Code (or portions thereof).
</p>
</item>
<item>
<bullet>(c)</bullet>
<p>
the licenses granted in this Section 2.1(a) and (b)
are effective on the date Initial Developer first
distributes Original Code under the terms of this License.
</p>
</item>
<item>
<bullet>(d)</bullet>
<p>
Notwithstanding Section 2.1(b) above, no patent license
is granted: 1) for code that You delete from the Original
Code; 2) separate from the Original Code; or 3) for
infringements caused by: i) the modification of the
Original Code or ii) the combination of the Original Code
with other software or devices. 2.2. Contributor Grant.
Subject to third party intellectual property claims, each
Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license (a) under intellectual property
rights (other than patent or trademark) Licensable
by Contributor, to use, reproduce, modify, display,
perform, sublicense and distribute the Modifications
created by such Contributor (or portions thereof)
either on an unmodified basis, with other Modifications,
as Covered Code and/or as part of a Larger Work; and
</p>
</item>
<item>
<bullet>(b)</bullet>
<p>
under Patent Claims infringed by the making, using, or selling
of Modifications made by that Contributor either alone and/or
in combination with its Contributor Version (or portions
of such combination), to make, use, sell, offer for sale,
have made, and/or otherwise dispose of: 1) Modifications
made by that Contributor (or portions thereof); and 2) the
combination of Modifications made by that Contributor with
its Contributor Version (or portions of such combination).
</p>
</item>
<item>
<bullet>(c)</bullet>
<p>
the licenses granted in Sections 2.2(a) and
2.2(b) are effective on the date Contributor
first makes Commercial Use of the Covered Code.
</p>
</item>
<item>
<bullet>(d)</bullet>
<p>
Notwithstanding Section 2.2(b) above, no patent license is
granted: 1) for any code that Contributor has deleted from
the Contributor Version; 2) separate from the Contributor
Version; 3) for infringements caused by: i) third party
modifications of Contributor Version or ii) the combination
of Modifications made by that Contributor with other
software (except as part of the Contributor Version) or other
devices; or 4) under Patent Claims infringed by Covered Code
in the absence of Modifications made by that Contributor.
</p>
</item>
<item>
<bullet>3.</bullet>
<p>
Distribution Obligations.
</p>
</item>
<item>
<bullet>3.1.</bullet>
<p>
Application of License. The Modifications which You create
or to which You contribute are governed by the terms of
this License, including without limitation Section 2.2.
The Source Code version of Covered 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. However, You may include an additional document
offering the additional rights described in Section 3.5.
</p>
</item>
<item>
<bullet>3.2.</bullet>
<p>
Availability of Source Code. Any Modification which You
create or to which You contribute must be made available
in Source Code form under the terms of this License
either on the same media as an Executable version or via
an accepted Electronic Distribution Mechanism to anyone
to whom you made an Executable version available; and
if made available via Electronic Distribution Mechanism,
must remain available for at least twelve (12) months
after the date it initially became available, or at
least six (6) months after a subsequent version of that
particular Modification has been made available to such
recipients. You are responsible for ensuring that the
Source Code version remains available even if the Electronic
Distribution Mechanism is maintained by a third party.
</p>
</item>
<item>
<bullet>3.3.</bullet>
<p>
Description of Modifications. You must cause all Covered
Code to which You contribute to contain a file documenting
the changes You made to create that Covered Code and
the date of any change. You must include a prominent
statement that the Modification is derived, directly or
indirectly, from Original Code provided by the Initial
Developer and including the name of the Initial Developer
in (a) the Source Code, and (b) in any notice in an
Executable version or related documentation in which You
describe the origin or ownership of the Covered Code.
</p>
</item>
<item>
<bullet>3.4.</bullet>
<p>
Intellectual Property Matters (a) Third Party Claims. If
Contributor has knowledge that a license under a third
party's intellectual property rights is required to exercise
the rights granted by such Contributor under Sections
2.1 or 2.2, Contributor must include a text file with the
Source Code distribution titled "LEGAL" which describes the
claim and the party making the claim in sufficient detail
that a recipient will know whom to contact. If Contributor
obtains such knowledge after the Modification is made
available as described in Section 3.2, Contributor shall
promptly modify the LEGAL file in all copies Contributor
makes available thereafter and shall take other steps
(such as notifying appropriate mailing lists or newsgroups)
reasonably calculated to inform those who received
the Covered Code that new knowledge has been obtained.
</p>
</item>
<item>
<bullet>(b)</bullet>
<p>
Contributor APIs. If Contributor's Modifications include
an application programming interface and Contributor
has knowledge of patent licenses which are reasonably
necessary to implement that API, Contributor must
also include this information in the LEGAL file. (c)
Representations. Contributor represents that, except as
disclosed pursuant to Section 3.4(a) above, Contributor
believes that Contributor's Modifications are Contributor's
original creation(s) and/or Contributor has sufficient
rights to grant the rights conveyed by this License.
</p>
</item>
<item>
<bullet>3.5.</bullet>
<p>
Required Notices. You must duplicate the notice in Exhibit
A in each file of the Source Code. If it is not possible
to put such notice in a particular Source Code file due
to its structure, then You must include such notice in a
location (such as a relevant directory) where a user would
be likely to look for such a notice. If You created one or
more Modification(s) You may add your name as a Contributor
to the notice described in Exhibit A. You must also
duplicate this License in any documentation for the Source
Code where You describe recipients' rights or ownership
rights relating to Covered Code. You may choose to offer,
and to charge a fee for, warranty, support, indemnity or
liability obligations to one or more recipients of Covered
Code. However, You may do so only on Your own behalf, and
not on behalf of the Initial Developer or any Contributor.
You must make it absolutely clear than any such warranty,
support, indemnity or liability obligation is offered by
You alone, and You hereby agree to indemnify the Initial
Developer and every Contributor for any liability incurred
by the Initial Developer or such Contributor as a result of
warranty, support, indemnity or liability terms You offer.
</p>
</item>
<item>
<bullet>3.6.</bullet>
<p>
Distribution of Executable Versions. You may distribute
Covered Code in Executable form only if the requirements of
Section 3.1-3.5 have been met for that Covered Code, and if
You include a notice stating that the Source Code version
of the Covered Code is available under the terms of this
License, including a description of how and where You have
fulfilled the obligations of Section 3.2. The notice must
be conspicuously included in any notice in an Executable
version, related documentation or collateral in which You
describe recipients' rights relating to the Covered Code.
You may distribute the Executable version of Covered 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 and that
the license for the Executable version does not attempt to
limit or alter the recipient's rights in the Source Code
version from the rights set forth in this License. If You
distribute the Executable version 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 or any Contributor. You hereby agree
to indemnify the Initial Developer and every Contributor
for any liability incurred by the Initial Developer or
such Contributor as a result of any such terms You offer.
</p>
</item>
<item>
<bullet>3.7.</bullet>
<p>
Larger Works. You may create a Larger Work by combining
Covered Code with other code not governed by the terms of
this License and distribute the Larger Work as a single
product. In such a case, You must make sure the requirements
of this License are fulfilled for the Covered Code.
</p>
</item>
<item>
<bullet>4.</bullet>
<p>
Inability to Comply Due to Statute or Regulation.
</p>
<p>
If it is impossible for You to comply with any of the
terms of this License with respect to some or all of the
Covered Code due to statute, judicial order, or regulation
then You must: (a) comply with the terms of this License
to the maximum extent possible; and (b) describe the
limitations and the code they affect. Such description must
be included in the LEGAL file described in Section 3.4 and
must be included with all distributions of the Source Code.
Except to the extent prohibited by statute or regulation,
such description must be sufficiently detailed for a
recipient of ordinary skill to be able to understand it.
</p>
</item>
<item>
<bullet>5.</bullet>
<p>
Application of this License.
</p>
<p>
This License applies to code to which the
Initial Developer has attached the notice
in Exhibit A and to related Covered Code.
</p>
</item>
<item>
<bullet>6.</bullet>
<p>
Versions of the License.
</p>
</item>
<item>
<bullet>6.1.</bullet>
<p>
New Versions. Thomas Richter may publish revised and/or
new versions of the License from time to time. Each
version will be given a distinguishing version number.
</p>
</item>
<item>
<bullet>6.2.</bullet>
<p>
Effect of New Versions. Once Covered Code has been published
under a particular version of the License, You may always
continue to use it under the terms of that version. You may
also choose to use such Covered Code under the terms of any
subsequent version of the License published by Thomas Richter.
No one other than Thomas Richter has the right to modify the
terms applicable to Covered Code created under this License.
</p>
</item>
<item>
<bullet>6.3.</bullet>
<p>
Derivative Works. If You create or use a modified version
of this License (which you may only do in order to apply it
to code which is not already Covered Code governed by this
License), You must (a) rename Your license so that the phrases
"TPL", "THOR Software", "Thomas Richter" or any confusingly
similar phrase do not appear in your license (except to
note that your license differs from this License) and (b)
otherwise make it clear that Your version of the license
contains terms which differ from the THOR Public License.
(Filling in the name of the Initial Developer, Original Code
or Contributor in the notice described in Exhibit A shall not
of themselves be deemed to be modifications of this License.)
</p>
</item>
<item>
<bullet>7.</bullet>
<p>
DISCLAIMER OF WARRANTY.
</p>
<p>
COVERED 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 COVERED 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 COVERED CODE
IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN
ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) 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 COVERED
CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
</p>
</item>
<item>
<bullet>8.</bullet>
<p>
TERMINATION.
</p>
</item>
<item>
<bullet>8.1.</bullet>
<p>
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 Covered 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.
</p>
</item>
<item>
<bullet>8.2.</bullet>
<p>
If You initiate litigation by asserting a patent
infringement claim (excluding declatory judgment actions)
against Initial Developer or a Contributor (the Initial
Developer or Contributor against whom You file such
action is referred to as "Participant") alleging that:
</p>
</item>
<item>
<bullet>(a)</bullet>
<p>
such Participant's Contributor Version directly or indirectly
infringes any patent, then any and all rights granted by
such Participant to You under Sections 2.1 and/or 2.2 of this
License shall, upon 60 days notice from Participant terminate
prospectively, unless if within 60 days after receipt of
notice You either: (i) agree in writing to pay Participant
a mutually agreeable reasonable royalty for Your past and
future use of Modifications made by such Participant, or (ii)
withdraw Your litigation claim with respect to the Contributor
Version against such Participant. If within 60 days of notice,
a reasonable royalty and payment arrangement are not mutually
agreed upon in writing by the parties or the litigation claim
is not withdrawn, the rights granted by Participant to You
under Sections 2.1 and/or 2.2 automatically terminate at
the expiration of the 60 day notice period specified above.
</p>
</item>
<item>
<bullet>(b)</bullet>
<p>
any software, hardware, or device, other than such
Participant's Contributor Version, directly or indirectly
infringes any patent, then any rights granted to You by such
Participant under Sections 2.1(b) and 2.2(b) are revoked effective
as of the date You first made, used, sold, distributed,
or had made, Modifications made by that Participant.
</p>
</item>
<item>
<bullet>8.3.</bullet>
<p>
If You assert a patent infringement claim against Participant
alleging that such Participant's Contributor Version directly
or indirectly infringes any patent where such claim is
resolved (such as by license or settlement) prior to the
initiation of patent infringement litigation, then the
reasonable value of the licenses granted by such Participant
under Sections 2.1 or 2.2 shall be taken into account in
determining the amount or value of any payment or license.
</p>
</item>
<item>
<bullet>8.4.</bullet>
<p>
In the event of termination under Sections 8.1
or 8.2 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.
</p>
</item>
<item>
<bullet>9.</bullet>
<p>
LIMITATION OF LIABILITY.
</p>
<p>
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 COVERED 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.
</p>
</item>
<item>
<bullet>10.</bullet>
<p>
U.S. GOVERNMENT END USERS.
</p>
<p>
The Covered Code is a "commercial item," as that term
is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of
"commercial computer software" and "commercial computer
software documentation," as such terms are used in 48
C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R.
12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4
(June 1995), all U.S. Government End Users acquire
Covered Code with only those rights set forth herein.
</p>
</item>
<item>
<bullet>11.</bullet>
<p>
MISCELLANEOUS.
</p>
<p>
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 German 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 Federal Republic of Germany, any litigation relating
to this License shall be subject to the jurisdiction of
the Federal Courts of the Federal Republic of Germany,
with the losing party responsible for costs, including
without limitation, court costs and reasonable attorneys'
fees and expenses. Any law or regulation which provides
that the language of a contract shall be construed
against the drafter shall not apply to this License.
</p>
</item>
<item>
<bullet>12.</bullet>
<p>
RESPONSIBILITY FOR CLAIMS.
</p>
<p>
As between Initial Developer and the Contributors, each
party is responsible for claims and damages arising,
directly or indirectly, out of its utilization of rights
under this License and You agree to work with Initial
Developer and Contributors to distribute such responsibility
on an equitable basis. Nothing herein is intended or
shall be deemed to constitute any admission of liability.
</p>
</item>
<item>
<bullet>13.</bullet>
<p>
MULTIPLE-LICENSED CODE.
</p>
<p>
Initial Developer may designate portions of the Covered
Code as Multiple-Licensed. Multiple-Licensed means that
the Initial Developer permits you to utilize portions
of the Covered Code under Your choice of the TPL or
the alternative licenses, if any, specified by the
Initial Developer in the file described in Exhibit A.
</p>
</item>
</list>
<optional>
<p>
EXHIBIT A - THOR Public License.
</p>
<standardLicenseHeader>
<p>
The contents of this file are subject to the THOR
Public License Version 1.0 (the "License"); you may not
use this file except in compliance with the License.
</p>
<p>
Software distributed under the License is distributed on
an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the License for the specificlanguage
governing rights and limitations under the License.
</p>
<p>
The Original Code is ______________________________________.
</p>
<p>
The Initial Developer of the Original Code is _____________.
</p>
<p>
Portions created by ______________________ are
Copyright (C) ______ _______________________.
</p>
<p>
All Rights Reserved.
</p>
<p>
Contributor(s): ______________________________________.
</p>
<p>
Alternatively, the contents of this file may be used under
the terms of the _____ license (the [___] License), in
which case the provisions of [______] License are applicable
instead of those above. If you wish to allow use of your
version of this file only under the terms of the [____]
License and not to allow others to use your version of this
file under the TPL, indicate your decision by deleting the
provisions above and replace them with the notice and other
provisions required by the [___] License. If you do not
delete the provisions above, a recipient may use your version
of this file under either the TPL or the [___] License."
</p>
</standardLicenseHeader>
<p>
[NOTE: The text of this Exhibit A may differ slightly
from the text of the notices in the Source Code
files of the Original Code. You should use the text
of this Exhibit A rather than the text found in the
Original Code Source Code for Your Modifications.]
</p>
</optional>
</text>
</license>
</SPDXLicenseCollection>

66
src/UCAR.xml Normal file
View File

@@ -0,0 +1,66 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="UCAR"
name="UCAR License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/Unidata/UDUNITS-2/blob/master/COPYRIGHT</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright 2014 University Corporation for Atmospheric
Research and contributors. All rights reserved.
</copyrightText>
<p>
This software was developed by the Unidata Program
Center of the University Corporation for Atmospheric
Research (UCAR) &lt;http://www.unidata.ucar.edu&gt;.
</p>
<p>
Redistribution and use in source and binary
forms, with or without modification, are permitted
provided that the following conditions are met:
</p>
<list>
<item>
<bullet>1)</bullet>
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
</item>
<item>
<bullet>2)</bullet>
Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or
other materials provided with the distribution.
</item>
<item>
<bullet>3)</bullet>
Neither the names of the development group, the copyright
holders, nor the names of contributors may be used to endorse
or promote products derived from this software without specific
prior written permission.
</item>
<item>
<bullet>4)</bullet> This license shall terminate
automatically and you may no longer exercise any of the rights
granted to you by this license as of the date you commence
an action, including a cross-claim or counterclaim, against
the copyright holders or any contributor alleging that this
software infringes a patent. This termination provision
shall not apply for an action alleging patent infringement by
combinations of this software with other software or hardware.
</item>
</list>
<p>
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE CONTRIBUTORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE.
</p>
</text>
</license>
</SPDXLicenseCollection>

18
src/exceptions/Autoconf-exception-generic.xml Normal file
View File

@@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<exception licenseId="Autoconf-exception-generic" name="Autoconf generic exception" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://launchpad.net/ubuntu/precise/+source/xmltooling/+copyright</crossRef>
<crossRef>https://tracker.debian.org/media/packages/s/sipwitch/copyright-1.9.15-3</crossRef>
<crossRef>https://opensource.apple.com/source/launchd/launchd-258.1/launchd/compile.auto.html</crossRef>
</crossRefs>
<text>
<p>
As a special exception to the GNU General Public License, if you
distribute this file as part of a program that contains a configuration
script generated by Autoconf, you may include it under the same
distribution terms that you use for the rest of that program.
</p>
</text>
</exception>
</SPDXLicenseCollection>

27
src/exceptions/Autoconf-exception-macro.xml Normal file
View File

@@ -0,0 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<exception licenseId="Autoconf-exception-macro" name="Autoconf macro exception" listVersionAdded="3.21">
<crossRefs>
<crossRef>https://github.com/freedesktop/xorg-macros/blob/39f07f7db58ebbf3dcb64a2bf9098ed5cf3d1223/xorg-macros.m4.in</crossRef>
<crossRef>https://www.gnu.org/software/autoconf-archive/ax_pthread.html</crossRef>
<crossRef>https://launchpad.net/ubuntu/precise/+source/xmltooling/+copyright</crossRef>
</crossRefs>
<text>
<p>
As a special exception, the respective Autoconf Macro's copyright owner
gives unlimited permission to copy, distribute and modify the configure
scripts that are the output of Autoconf when processing the Macro. You
need not follow the terms of the GNU General Public License when using
or distributing such scripts, even though portions of the text of the
Macro appear in them. The GNU General Public License (GPL) does govern
all other use of the material that constitutes the Autoconf Macro.
</p>
<p>
This special exception to the GPL applies to versions of the Autoconf
Macro released by the Autoconf Archive. When you make and distribute a
modified version of the Autoconf Macro, you may extend this special
exception to the GPL to apply to your modified version as well.
</p>
</text>
</exception>
</SPDXLicenseCollection>

22
src/exceptions/GNAT-exception.xml Normal file
View File

@@ -0,0 +1,22 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<exception licenseId="GNAT-exception"
name="GNAT exception" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/AdaCore/florist/blob/master/libsrc/posix-configurable_file_limits.adb</crossRef>
</crossRefs>
<notes>
This exception has been used with both versions 2.0 and 3.0 of the GPL.
</notes>
<text>
<p>
As a special exception, if other files instantiate generics from this
unit, or you link this unit with other files to produce an executable,
this unit does not by itself cause the resulting executable to be
covered by the GNU General Public License. This exception does not
however invalidate any other reasons why the executable file might be
covered by the GNU Public License.
</p>
</text>
</exception>
</SPDXLicenseCollection>

23
src/exceptions/QPL-1.0-INRIA-2004-exception.xml Normal file
View File

@@ -0,0 +1,23 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<exception licenseId="QPL-1.0-INRIA-2004-exception"
name="INRIA QPL 1.0 2004 variant exception" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://git.frama-c.com/pub/frama-c/-/blob/master/licenses/Q_MODIFIED_LICENSE</crossRef>
<crossRef>https://github.com/maranget/hevea/blob/master/LICENSE</crossRef>
</crossRefs>
<notes>
This exception is primarily used with QPL-1.0-INRIA-2004
</notes>
<text>
<p>
As a special exception to the Q Public License, you may develop
application programs, reusable components and other software items
that link with the original or modified versions of the
<alt match="Software|Generator" name="softwareGenerator">Software</alt>
and are not made available to the general public, without any of the
additional requirements listed in clause 6c of the Q Public license.
</p>
</text>
</exception>
</SPDXLicenseCollection>

18
src/exceptions/SWI-exception.xml Normal file
View File

@@ -0,0 +1,18 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<exception licenseId="SWI-exception" name="SWI exception" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/SWI-Prolog/packages-clpqr/blob/bfa80b9270274f0800120d5b8e6fef42ac2dc6a5/clpqr/class.pl</crossRef>
</crossRefs>
<text>
<p>
As a special exception, if you link this library with other
files, compiled with a Free Software compiler, to produce an
executable, this library does not by itself cause the resulting
executable to be covered by the GNU General Public License. This
exception does not however invalidate any other reasons why the
executable file might be covered by the GNU General Public License.
</p>
</text>
</exception>
</SPDXLicenseCollection>

19
src/snprintf.xml Normal file
View File

@@ -0,0 +1,19 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="snprintf"
name="snprintf License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/openssh/openssh-portable/blob/master/openbsd-compat/bsd-snprintf.c#L2</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright Patrick Powell 1995
</copyrightText>
<p>
This code is based on code written by Patrick Powell
(papowell@astart.com) It may be used for any purpose as long
as this notice remains intact on all source code distributions
</p>
</text>
</license>
</SPDXLicenseCollection>

28
src/w3m.xml Normal file
View File

@@ -0,0 +1,28 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="w3m"
name="w3m License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://github.com/tats/w3m/blob/master/COPYING</crossRef>
</crossRefs>
<text>
<copyrightText>
(C) Copyright 1994-2002 by Akinori Ito<br></br>
(C) Copyright 2002-2011 by Akinori
Ito, Hironori Sakamoto, Fumitoshi Ukai
</copyrightText>
<p>
Use, modification and redistribution of this
software is hereby granted, provided that this entire
copyright notice is included on any copies of this
software and applications and derivations thereof.
</p>
<p>
This software is provided on an "as is" basis, without warranty
of any kind, either expressed or implied, as to any matter
including, but not limited to warranty of fitness of purpose, or
merchantability, or results obtained from use of this software.
</p>
</text>
</license>
</SPDXLicenseCollection>

27
src/xlock.xml Normal file
View File

@@ -0,0 +1,27 @@
<?xml version="1.0" encoding="UTF-8"?>
<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
<license isOsiApproved="false" licenseId="xlock"
name="xlock License" listVersionAdded="3.20">
<crossRefs>
<crossRef>https://fossies.org/linux/tiff/contrib/ras/ras2tif.c</crossRef>
</crossRefs>
<text>
<copyrightText>
Copyright (c) 1990 by Sun Microsystems, Inc.
Author: Patrick J. Naughton naughton@wind.sun.com
</copyrightText>
<p>
Permission to use, copy, modify, and distribute this software
and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all
copies and that both that copyright notice and this permission
notice appear in supporting documentation. This file is provided
AS IS with no warranties of any kind. The author shall have
no liability with respect to the infringement of copyrights,
trade secrets or any patents by this file or any part thereof.
In no event will the author be liable for any lost revenue or
profits or other special, indirect and consequential damages.
</p>
</text>
</license>
</SPDXLicenseCollection>

1
test/simpleTestForGenerator/AdaCore-doc.txt Normal file
View File

@@ -0,0 +1 @@
This document may be copied, in whole or in part, in any form or by any means, as is or with alterations, provided that (1) alterations are clearly marked as alterations and (2) this copyright notice is included unmodified in any copy.

4
test/simpleTestForGenerator/Autoconf-exception-generic.txt Normal file
View File

@@ -0,0 +1,4 @@
As a special exception to the GNU General Public License,
if you distribute this file as part of a program that contains
a configuration script generated by Autoconf, you may include
it under the same distribution terms that you use for the rest of that program.

12
test/simpleTestForGenerator/Autoconf-exception-macro.txt Normal file
View File

@@ -0,0 +1,12 @@
As a special exception, the respective Autoconf Macro's copyright owner
gives unlimited permission to copy, distribute and modify the configure
scripts that are the output of Autoconf when processing the Macro. You
need not follow the terms of the GNU General Public License when using
or distributing such scripts, even though portions of the text of the
Macro appear in them. The GNU General Public License (GPL) does govern
all other use of the material that constitutes the Autoconf Macro.
This special exception to the GPL applies to versions of the Autoconf
Macro released by the Autoconf Archive. When you make and distribute a
modified version of the Autoconf Macro, you may extend this special
exception to the GPL to apply to your modified version as well.

9
test/simpleTestForGenerator/BSD-4.3RENO.txt Normal file
View File

@@ -0,0 +1,9 @@
Copyright (c) 1987 Regents of the University of California.
All rights reserved.
Redistribution and use in source and binary forms are permitted
provided that this notice is preserved and that due credit is given
to the University of California at Berkeley. The name of the University
may not be used to endorse or promote products derived from this
software without specific written prior permission. This software
is provided ``as is'' without express or implied warranty.

11
test/simpleTestForGenerator/BSD-4.3TAHOE.txt Normal file
View File

@@ -0,0 +1,11 @@
Copyright (c) 1987 Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided
that the above copyright notice and this paragraph are duplicated in all
such forms and that any documentation, advertising materials, and other
materials related to such distribution and use acknowledge that the software
was developed by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived from this
software without specific prior written permission. THIS SOFTWARE IS PROVIDED
``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT
LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.

37
test/simpleTestForGenerator/BSD-Advertising-Acknowledgement.txt Normal file
View File

@@ -0,0 +1,37 @@
Copyright (c) 2001 David Giffin.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this
software must display the following acknowledgment:
"This product includes software developed by
David Giffin <david@giffin.org>."
4. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by
David Giffin <david@giffin.org>."
THIS SOFTWARE IS PROVIDED BY DAVID GIFFIN ``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. IN NO EVENT SHALL DAVID GIFFIN 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.

37
test/simpleTestForGenerator/BSD-Attribution-HPND-disclaimer.txt Normal file
View File

@@ -0,0 +1,37 @@
Copyright (c) 1998-2003 Carnegie Mellon University. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
3. The name "Carnegie Mellon University" must not be used to
endorse or promote products derived from this software without
prior written permission. For permission or any other legal
details, please contact
Office of Technology Transfer
Carnegie Mellon University
5000 Forbes Avenue
Pittsburgh, PA 15213-3890
(412) 268-4387, fax: (412) 268-7395
tech-transfer@andrew.cmu.edu
4. Redistributions of any form whatsoever must retain the following
acknowledgment:
"This product includes software developed by Computing Services
at Carnegie Mellon University (http://www.cmu.edu/computing/)."
CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

26
test/simpleTestForGenerator/Brian-Gladman-3-Clause.txt Normal file
View File

@@ -0,0 +1,26 @@
Copyright (c) 2003, Dr Brian Gladman, Worcester, UK. All rights reserved.
LICENSE TERMS
The free distribution and use of this software in both source and binary
form is allowed (with or without changes) provided that:
1. distributions of this source code include the above copyright
notice, this list of conditions and the following disclaimer;
2. distributions in binary form include the above copyright
notice, this list of conditions and the following disclaimer
in the documentation and/or other associated materials;
3. the copyright holder's name is not used to endorse products
built using this software without specific written permission.
ALTERNATIVELY, provided that this notice is retained in full, this product
may be distributed under the terms of the GNU General Public License (GPL),
in which case the provisions of the GPL apply INSTEAD OF those given above.
DISCLAIMER
This software is provided 'as is' with no explicit or implied warranties
in respect of its properties, including, but not limited to, correctness
and/or fitness for purpose.

7
test/simpleTestForGenerator/CFITSIO.txt Normal file
View File

@@ -0,0 +1,7 @@
Copyright (Unpublished-all rights reserved under the copyright laws of the United States), U.S. Government as represented by the Administrator of the National Aeronautics and Space Administration. No copyright is claimed in the United States under Title 17, U.S. Code.
Permission to freely use, copy, modify, and distribute this software and its documentation without fee is hereby granted, provided that this copyright notice and disclaimer of warranty appears in all copies.
DISCLAIMER:
THE SOFTWARE IS PROVIDED 'AS IS' WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THE SOFTWARE WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND FREEDOM FROM INFRINGEMENT, AND ANY WARRANTY THAT THE DOCUMENTATION WILL CONFORM TO THE SOFTWARE, OR ANY WARRANTY THAT THE SOFTWARE WILL BE ERROR FREE. IN NO EVENT SHALL NASA BE LIABLE FOR ANY DAMAGES, INCLUDING, BUT NOT LIMITED TO, DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES, ARISING OUT OF, RESULTING FROM, OR IN ANY WAY CONNECTED WITH THIS SOFTWARE, WHETHER OR NOT BASED UPON WARRANTY, CONTRACT, TORT , OR OTHERWISE, WHETHER OR NOT INJURY WAS SUSTAINED BY PERSONS OR PROPERTY OR OTHERWISE, AND WHETHER OR NOT LOSS WAS SUSTAINED FROM, OR AROSE OUT OF THE RESULTS OF, OR USE OF, THE SOFTWARE OR SERVICES PROVIDED HEREUNDER."

22
test/simpleTestForGenerator/CMU-Mach.txt Normal file
View File

@@ -0,0 +1,22 @@
Copyright (c) 1991,1990,1989 Carnegie Mellon University
All Rights Reserved.
Permission to use, copy, modify and distribute this software and its
documentation is hereby granted, provided that both the copyright
notice and this permission notice appear in all copies of the
software, derivative works or modified versions, and any portions
thereof, and that both notices appear in supporting documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Carnegie Mellon requests users of this software to return to
Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
School of Computer Science
Carnegie Mellon University
Pittsburgh PA 15213-3890
any improvements or extensions that they make and grant Carnegie Mellon
the rights to redistribute these changes.

15
test/simpleTestForGenerator/Clips.txt Normal file
View File

@@ -0,0 +1,15 @@
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY
CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

20
test/simpleTestForGenerator/Cornell-Lossless-JPEG.txt Normal file
View File

@@ -0,0 +1,20 @@
Copyright (c) 1993 Cornell University, Kongji Huang
All rights reserved.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose, without fee, and without written
agreement is hereby granted, provided that the above copyright notice
and the following two paragraphs appear in all copies of this
software.
IN NO EVENT SHALL THE CORNELL UNIVERSITY BE LIABLE TO ANY PARTY FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF CORNELL
UNIVERSITY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE CORNELL UNIVERSITY SPECIFICALLY DISCLAIMS ANY WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE SOFTWARE
PROVIDED HEREUNDER IS ON AN "AS IS" BASIS, AND CORNELL UNIVERSITY HAS
NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,
OR MODIFICATIONS.

6
test/simpleTestForGenerator/GNAT-exception.txt Normal file
View File

@@ -0,0 +1,6 @@
As a special exception, if other files instantiate generics from this
unit, or you link this unit with other files to produce an executable,
this unit does not by itself cause the resulting executable to be
covered by the GNU General Public License. This exception does not
however invalidate any other reasons why the executable file might be
covered by the GNU Public License.

10
test/simpleTestForGenerator/HP-1986.txt Normal file
View File

@@ -0,0 +1,10 @@
(c) Copyright 1986 HEWLETT-PACKARD COMPANY
To anyone who acknowledges that this file is provided "AS IS"
without any express or implied warranty: permission to use, copy,
modify, and distribute this file for any purpose is hereby granted
without fee, provided that the above copyright notice and this notice
appears in all copies, and that the name of Hewlett-Packard Company
not be used in advertising or publicity pertaining to distribution
of the software without specific, written prior permission. Hewlett-Packard
Company makes no representations about the suitability of this software for any purpose.

3
test/simpleTestForGenerator/HPND-Markus-Kuhn.txt Normal file
View File

@@ -0,0 +1,3 @@
Permission to use, copy, modify, and distribute this software
for any purpose and without fee is hereby granted. The author
disclaims all warranties with regard to this software.

20
test/simpleTestForGenerator/HPND-sell-variant-MIT-disclaimer.txt Normal file
View File

@@ -0,0 +1,20 @@
by Jim Knoble <jmknoble@pobox.com>
Copyright (C) 1999,2000,2001 Jim Knoble
Permission to use, copy, modify, distribute, and sell this software
and its documentation for any purpose is hereby granted without fee,
provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear in
supporting documentation.
+------------+
| Disclaimer |
+------------+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
express or implied, including but not limited to the warranties of
merchantability, fitness for a particular purpose and
noninfringement. In no event shall the author(s) be liable for any
claim, damages or other liability, whether in an action of contract,
tort or otherwise, arising from, out of or in connection with the
software or the use or other dealings in the software.

37
test/simpleTestForGenerator/IEC-Code-Components-EULA.txt Normal file
View File

@@ -0,0 +1,37 @@
IEC Code Components End-user licence agreement
Code Components in IEC standards (International Standards, Technical Specifications or
Technical Reports) which have been identified and approved for licensing, are licensed subject to
the following conditions:
- Redistributions of software must retain the Copyright Notice, this list of conditions and the
disclaimer below (“Disclaimer”).
- The software license extends to modifications permitted under the relevant IEC standard.
- The software license extends to clarifications and corrections approved by IEC.
- Neither the name of IEC, nor the names of specific contributors, may be used to endorse or
promote products derived from this software without specific prior written permission. The
relevant IEC standard may be referenced when claiming compliance with the relevant IEC
standard.
- The user of Code Components shall attribute each such Code Component to IEC and identify
the IEC standard from which it is taken. Such attribution (e.g., “This code was derived from IEC
[insert standard reference number:publication year] within modifications permitted in the
relevant IEC standard. Please reproduce this note if possible.”), may be placed in the code itself
or any other reasonable location.
Code Components means components included in IEC standards that are intended to be directly
processed by a computer and also includes any text found between the markers <CODE
BEGINS> and <CODE ENDS>, or otherwise clearly labeled in this standard as a Code
Component.
The Disclaimer is:
EACH OF THE CODE COMPONENTS IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR 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 THE CODE
COMPONENTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

21
test/simpleTestForGenerator/JPL-image.txt Normal file
View File

@@ -0,0 +1,21 @@
JPL Image Use Policy
Unless otherwise noted, images and video on JPL public web sites (public sites ending with a jpl.nasa.gov address) may be used for any purpose without prior permission, subject to the special cases noted below. Publishers who wish to have authorization may print this page and retain it for their records; JPL does not issue image permissions on an image by image basis.
By electing to download the material from this web site the user agrees:
1. that Caltech makes no representations or warranties with respect to ownership of copyrights in the images, and does not represent others who may claim to be authors or owners of copyright of any of the images, and makes no warranties as to the quality of the images. Caltech shall not be responsible for any loss or expenses resulting from the use of the images, and you release and hold Caltech harmless from all liability arising from such use.
2. to use a credit line in connection with images. Unless otherwise noted in the caption information for an image, the credit line should be "Courtesy NASA/JPL-Caltech."
3. that the endorsement of any product or service by Caltech, JPL or NASA must not be claimed or implied.
Special Cases:
* Prior written approval must be obtained to use the NASA insignia logo (the blue "meatball" insignia), the NASA logotype (the red "worm" logo) and the NASA seal. These images may not be used by persons who are not NASA employees or on products (including Web pages) that are not NASA sponsored. In addition, no image may be used to explicitly or implicitly suggest endorsement by NASA, JPL or Caltech of commercial goods or services. Requests to use NASA logos may be directed to Bert Ulrich, Public Services Division, NASA Headquarters, Code POS, Washington, DC 20546, telephone (202) 358-1713, fax (202) 358-4331, email bert.ulrich@hq.nasa.gov.
* Prior written approval must be obtained to use the JPL logo (stylized JPL letters in red or other colors). Requests to use the JPL logo may be directed to the Institutional Communications Office, email instcomm@jpl.nasa.gov.
* If an image includes an identifiable person, using the image for commercial purposes may infringe that person's right of privacy or publicity, and permission should be obtained from the person. NASA and JPL generally do not permit likenesses of current employees to appear on commercial products. For more information, consult the NASA and JPL points of contact listed above.
* JPL/Caltech contractors and vendors who wish to use JPL images in advertising or public relation materials should direct requests to the Institutional Communications Office, email instcomm@jpl.nasa.gov.
* Some image and video materials on JPL public web sites are owned by organizations other than JPL or NASA. These owners have agreed to make their images and video available for journalistic, educational and personal uses, but restrictions are placed on commercial uses. To obtain permission for commercial use, contact the copyright owner listed in each image caption. Ownership of images and video by parties other than JPL and NASA is noted in the caption material with each image.

4
test/simpleTestForGenerator/Kazlib.txt Normal file
View File

@@ -0,0 +1,4 @@
Copyright (C) 1999 Kaz Kylheku
Free Software License:
All rights are reserved by the author, with the following exceptions: Permission is granted to freely reproduce and distribute this software, possibly in exchange for a fee, provided that this copyright notice appears intact. Permission is also granted to adapt this software to produce derivative works, as long as the modified versions carry this copyright notice and additional notices stating that the work has been modified. This source code may be translated into executable form and incorporated into proprietary software; there is no requirement for such software to contain a copyright notice related to this source.

5
test/simpleTestForGenerator/Martin-Birgmeier.txt Normal file
View File

@@ -0,0 +1,5 @@
Copyright (c) 1993 Martin Birgmeier All rights reserved.
You may redistribute unmodified or modified versions of this source code provided that the above copyright notice and this and the following conditions are retained.
This software is provided ``as is'', and comes with no warranties of any kind. I shall in no event be liable for anything that happens to anyone/anything when using this software.

22
test/simpleTestForGenerator/OFFIS.txt Normal file
View File

@@ -0,0 +1,22 @@
Copyright (C) 1994-2001, OFFIS
This software and supporting documentation were developed by
Kuratorium OFFIS e.V.
Healthcare Information and Communication Systems
Escherweg 2
D-26121 Oldenburg, Germany
THIS SOFTWARE IS MADE AVAILABLE, AS IS, AND OFFIS MAKES NO WARRANTY
REGARDING THE SOFTWARE, ITS PERFORMANCE, ITS MERCHANTABILITY OR
FITNESS FOR ANY PARTICULAR USE, FREEDOM FROM ANY COMPUTER DISEASES OR
ITS CONFORMITY TO ANY SPECIFICATION. THE ENTIRE RISK AS TO QUALITY AND
PERFORMANCE OF THE SOFTWARE IS WITH THE USER.
Copyright of the software and supporting documentation is, unless
otherwise stated, owned by OFFIS, and free access is hereby granted as
a license to use this software, copy this software and prepare
derivative works based upon this software. However, any distribution
of this software source code or supporting documentation or derivative
works (source code and supporting documentation) must include the
three paragraphs of this copyright notice.

77
test/simpleTestForGenerator/OpenPBS-2.3.txt Normal file
View File

@@ -0,0 +1,77 @@
OpenPBS (Portable Batch System) v2.3 Software License
Copyright (c) 1999-2000 Veridian Information Solutions, Inc.
All rights reserved.
---------------------------------------------------------------------------
For a license to use or redistribute the OpenPBS software under conditions
other than those described below, or to purchase support for this software,
please contact Veridian Systems, PBS Products Department ("Licensor") at:
www.OpenPBS.org +1 650 967-4675 sales@OpenPBS.org
877 902-4PBS (US toll-free)
---------------------------------------------------------------------------
This license covers use of the OpenPBS v2.3 software (the "Software") at
your site or location, and, for certain users, redistribution of the
Software to other sites and locations. Use and redistribution of
OpenPBS v2.3 in source and binary forms, with or without modification,
are permitted provided that all of the following conditions are met.
After December 31, 2001, only conditions 3-6 must be met:
1. Commercial and/or non-commercial use of the Software is permitted
provided a current software registration is on file at www.OpenPBS.org.
If use of this software contributes to a publication, product, or
service, proper attribution must be given; see www.OpenPBS.org/credit.html
2. Redistribution in any form is only permitted for non-commercial,
non-profit purposes. There can be no charge for the Software or any
software incorporating the Software. Further, there can be no
expectation of revenue generated as a consequence of redistributing
the Software.
3. Any Redistribution of source code must retain the above copyright notice
and the acknowledgment contained in paragraph 6, this list of conditions
and the disclaimer contained in paragraph 7.
4. Any Redistribution in binary form must reproduce the above copyright
notice and the acknowledgment contained in paragraph 6, this list of
conditions and the disclaimer contained in paragraph 7 in the
documentation and/or other materials provided with the distribution.
5. Redistributions in any form must be accompanied by information on how to
obtain complete source code for the OpenPBS software and any
modifications and/or additions to the OpenPBS software. The source code
must either be included in the distribution or be available for no more
than the cost of distribution plus a nominal fee, and all modifications
and additions to the Software must be freely redistributable by any party
(including Licensor) without restriction.
6. All advertising materials mentioning features or use of the Software must
display the following acknowledgment:
"This product includes software developed by NASA Ames Research Center,
Lawrence Livermore National Laboratory, and Veridian Information Solutions,
Inc. Visit www.OpenPBS.org for OpenPBS software support,
products, and information."
7. DISCLAIMER OF WARRANTY
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT
ARE EXPRESSLY DISCLAIMED.
IN NO EVENT SHALL VERIDIAN CORPORATION, ITS AFFILIATED COMPANIES, OR THE
U.S. GOVERNMENT OR ANY OF ITS AGENCIES BE LIABLE FOR ANY DIRECT OR 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.
This license will be governed by the laws of the Commonwealth of Virginia,
without reference to its choice of law rules.

5
test/simpleTestForGenerator/QPL-1.0-INRIA-2004-exception.txt Normal file
View File

@@ -0,0 +1,5 @@
As a special exception to the Q Public Licence, you may develop
application programs, reusable components and other software items
that link with the original or modified versions of the Software
and are not made available to the general public, without any of the
additional requirements listed in clause 6c of the Q Public licence.

102
test/simpleTestForGenerator/QPL-1.0-INRIA-2004.txt Normal file
View File

@@ -0,0 +1,102 @@
THE Q PUBLIC LICENSE version 1.0
Copyright (C) 1999 Troll Tech AS, Norway.
Everyone is permitted to copy and
distribute this license document.
The intent of this license is to establish freedom to share and change
the software regulated by this license under the open source model.
This license applies to any software containing a notice placed by the
copyright holder saying that it may be distributed under the terms of
the Q Public License version 1.0. Such software is herein referred to
as the Software. This license covers modification and distribution of
the Software, use of third-party application programs based on the
Software, and development of free software which uses the Software.
Granted Rights
1. You are granted the non-exclusive rights set forth in this license
provided you agree to and comply with any and all conditions in this
license. Whole or partial distribution of the Software, or software
items that link with the Software, in any form signifies acceptance of
this license.
2. You may copy and distribute the Software in unmodified form
provided that the entire package, including - but not restricted to -
copyright, trademark notices and disclaimers, as released by the
initial developer of the Software, is distributed.
3. You may make modifications to the Software and distribute your
modifications, in a form that is separate from the Software, such as
patches. The following restrictions apply to modifications:
a. Modifications must not alter or remove any copyright notices
in the Software.
b. When modifications to the Software are released under this
license, a non-exclusive royalty-free right is granted to the
initial developer of the Software to distribute your
modification in future versions of the Software provided such
versions remain available under these terms in addition to any
other license(s) of the initial developer.
4. You may distribute machine-executable forms of the Software or
machine-executable forms of modified versions of the Software,
provided that you meet these restrictions:
a. You must include this license document in the distribution.
b. You must ensure that all recipients of the machine-executable
forms are also able to receive the complete machine-readable
source code to the distributed Software, including all
modifications, without any charge beyond the costs of data
transfer, and place prominent notices in the distribution
explaining this.
c. You must ensure that all modifications included in the
machine-executable forms are available under the terms of this
license.
5. You may use the original or modified versions of the Software to
compile, link and run application programs legally developed by you or
by others.
6. You may develop application programs, reusable components and other
software items that link with the original or modified versions of the
Software. These items, when distributed, are subject to the following
requirements:
a. You must ensure that all recipients of machine-executable
forms of these items are also able to receive and use the
complete machine-readable source code to the items without any
charge beyond the costs of data transfer.
b. You must explicitly license all recipients of your items to
use and re-distribute original and modified versions of the
items in both machine-executable and source code forms. The
recipients must be able to do so without any charges whatsoever,
and they must be able to re-distribute to anyone they choose.
c. If the items are not available to the general public, and the
initial developer of the Software requests a copy of the items,
then you must supply one.
Limitations of Liability
In no event shall the initial developers or copyright holders be
liable for any damages whatsoever, including - but not restricted to -
lost revenue or profits or other direct, indirect, special, incidental
or consequential damages, even if they have been advised of the
possibility of such damages, except to the extent invariable law, if
any, provides otherwise.
No Warranty
The Software and this license document are provided AS IS with NO
WARRANTY OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN,
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Choice of Law
This license is governed by the Laws of France.

7
test/simpleTestForGenerator/SWI-exception.txt Normal file
View File

@@ -0,0 +1,7 @@
As a special exception, if you link this library with other files,
compiled with a Free Software compiler, to produce an executable, this
library does not by itself cause the resulting executable to be covered
by the GNU General Public License. This exception does not however
invalidate any other reasons why the executable file might be covered by
the GNU General Public License.

6
test/simpleTestForGenerator/SunPro.txt Normal file
View File

@@ -0,0 +1,6 @@
Copyright (C) 1993 by Sun Microsystems, Inc. All rights reserved.
Developed at SunSoft, a Sun Microsystems, Inc. business.
Permission to use, copy, modify, and distribute this
software is freely granted, provided that this notice
is preserved.

475
test/simpleTestForGenerator/TPL-1.0.txt Normal file
View File

@@ -0,0 +1,475 @@
THOR Public Licence (TPL)
0. Notes of Origin
0.1 As required by paragraph 6.3 of the "Mozilla Public Licence",
"MPL" in the following, it is hereby stated that this Licence
condition ("TPL") differs in the following items from the original
"Mozilla Public Licence" as provided by "Netscape Communications
Corporation":
a) Paragraphs 6.2 and 6.3 of the MPL has been modified to bind licence
modifications to the Author of this Licence, Thomas Richter.
b) Paragraph 11 has been modified to gover this Licence by German
law rather than Californian Law.
c) The licence has been renamed to "TPL" and "THOR Public
Licence". All references towards "MPL" have been removed except in
section 0 to indicate the difference from "MPL".
No other modifications have been made.
1. Definitions.
1.0.1. "Commercial Use" means distribution or otherwise making the
Covered Code available to a third party.
1.1. "Contributor" means each entity that creates or contributes to
the creation of Modifications.
1.2. "Contributor Version" means the combination of the Original Code,
prior Modifications used by a Contributor, and the Modifications made
by that particular Contributor.
1.3. "Covered Code" means the Original Code or Modifications or the
combination of the Original Code and Modifications, in each case
including portions thereof.
1.4. "Electronic Distribution Mechanism" means a mechanism generally
accepted in the software development community for the electronic
transfer of data.
1.5. "Executable" means Covered Code in any form other than Source
Code.
1.6. "Initial Developer" means the individual or entity identified as
the Initial Developer in the Source Code notice required by Exhibit A.
1.7. "Larger Work" means a work which combines Covered Code or
portions thereof with code not governed by the terms of this License.
1.8. "License" means this document.
1.8.1. "Licensable" means having the right to grant, to the maximum
extent possible, whether at the time of the initial grant or
subsequently acquired, any and all of the rights conveyed herein.
1.9. "Modifications" means any addition to or deletion from the
substance or structure of either the Original Code or any previous
Modifications. When Covered Code is released as a series of files, a
Modification is: A. Any addition to or deletion from the contents of a
file containing Original Code or previous Modifications.
B. Any new file that contains any part of the Original Code or
previous Modifications.
1.10. "Original Code" means Source Code of computer software code
which is described in the Source Code notice required by Exhibit A as
Original Code, and which, at the time of its release under this
License is not already Covered Code governed by this License.
1.10.1. "Patent Claims" means any patent claim(s), now owned or
hereafter acquired, including without limitation, method, process, and
apparatus claims, in any patent Licensable by grantor.
1.11. "Source Code" means the preferred form of the Covered Code for
making modifications to it, including all modules it contains, plus
any associated interface definition files, scripts used to control
compilation and installation of an Executable, or source code
differential comparisons against either the Original Code or another
well known, available Covered Code of the Contributor's choice. The
Source Code can be in a compressed or archival form, provided the
appropriate decompression or de-archiving software is widely available
for no charge.
1.12. "You" (or "Your") means an individual or a legal entity
exercising rights under, and complying with all of the terms of, this
License or a future version of this License issued under Section
6.1. For legal entities, "You" includes any entity which controls, is
controlled by, or is under common control with You. For purposes of
this definition, "control" means (a) the power, direct or indirect, to
cause the direction or management of such entity, whether by contract
or otherwise, or (b) ownership of more than fifty percent (50%) of the
outstanding shares or beneficial ownership of such entity.
2. Source Code License.
2.1. The Initial Developer Grant. The Initial Developer hereby grants
You a world-wide, royalty-free, non-exclusive license, subject to
third party intellectual property claims: (a) 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
(b) under Patents Claims infringed by the making, using or selling of
Original Code, to make, have made, use, practice, sell, and offer for
sale, and/or otherwise dispose of the Original Code (or portions
thereof).
(c) the licenses granted in this Section 2.1(a) and (b) are effective
on the date Initial Developer first distributes Original Code under
the terms of this License.
(d) Notwithstanding Section 2.1(b) above, no patent license is
granted: 1) for code that You delete from the Original Code; 2)
separate from the Original Code; or 3) for infringements caused by: i)
the modification of the Original Code or ii) the combination of the
Original Code with other software or devices.
2.2. Contributor Grant. Subject to third party intellectual property
claims, each Contributor hereby grants You a world-wide, royalty-free,
non-exclusive license
(a) under intellectual property rights (other than patent or
trademark) Licensable by Contributor, to use, reproduce, modify,
display, perform, sublicense and distribute the Modifications created
by such Contributor (or portions thereof) either on an unmodified
basis, with other Modifications, as Covered Code and/or as part of a
Larger Work; and
(b) under Patent Claims infringed by the making, using, or selling of
Modifications made by that Contributor either alone and/or in
combination with its Contributor Version (or portions of such
combination), to make, use, sell, offer for sale, have made, and/or
otherwise dispose of: 1) Modifications made by that Contributor (or
portions thereof); and 2) the combination of Modifications made by
that Contributor with its Contributor Version (or portions of such
combination).
(c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective
on the date Contributor first makes Commercial Use of the Covered
Code.
(d) Notwithstanding Section 2.2(b) above, no patent license is
granted: 1) for any code that Contributor has deleted from the
Contributor Version; 2) separate from the Contributor Version; 3) for
infringements caused by: i) third party modifications of Contributor
Version or ii) the combination of Modifications made by that
Contributor with other software (except as part of the Contributor
Version) or other devices; or 4) under Patent Claims infringed by
Covered Code in the absence of Modifications made by that Contributor.
3. Distribution Obligations.
3.1. Application of License. The Modifications which You create or to
which You contribute are governed by the terms of this License,
including without limitation Section 2.2. The Source Code version of
Covered 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. However, You may
include an additional document offering the additional rights
described in Section 3.5.
3.2. Availability of Source Code. Any Modification which You create
or to which You contribute must be made available in Source Code form
under the terms of this License either on the same media as an
Executable version or via an accepted Electronic Distribution
Mechanism to anyone to whom you made an Executable version available;
and if made available via Electronic Distribution Mechanism, must
remain available for at least twelve (12) months after the date it
initially became available, or at least six (6) months after a
subsequent version of that particular Modification has been made
available to such recipients. You are responsible for ensuring that
the Source Code version remains available even if the Electronic
Distribution Mechanism is maintained by a third party.
3.3. Description of Modifications. You must cause all Covered Code to
which You contribute to contain a file documenting the changes You
made to create that Covered Code and the date of any change. You must
include a prominent statement that the Modification is derived,
directly or indirectly, from Original Code provided by the Initial
Developer and including the name of the Initial Developer in (a) the
Source Code, and (b) in any notice in an Executable version or related
documentation in which You describe the origin or ownership of the
Covered Code.
3.4. Intellectual Property Matters (a) Third Party Claims. If
Contributor has knowledge that a license under a third party's
intellectual property rights is required to exercise the rights
granted by such Contributor under Sections 2.1 or 2.2, Contributor
must include a text file with the Source Code distribution titled
"LEGAL" which describes the claim and the party making the claim in
sufficient detail that a recipient will know whom to contact. If
Contributor obtains such knowledge after the Modification is made
available as described in Section 3.2, Contributor shall promptly
modify the LEGAL file in all copies Contributor makes available
thereafter and shall take other steps (such as notifying appropriate
mailing lists or newsgroups) reasonably calculated to inform those who
received the Covered Code that new knowledge has been obtained.
(b) Contributor APIs. If Contributor's Modifications include an
application programming interface and Contributor has knowledge of
patent licenses which are reasonably necessary to implement that API,
Contributor must also include this information in the LEGAL file.
(c) Representations. Contributor represents that, except as disclosed
pursuant to Section 3.4(a) above, Contributor believes that
Contributor's Modifications are Contributor's original creation(s)
and/or Contributor has sufficient rights to grant the rights conveyed
by this License.
3.5. Required Notices. You must duplicate the notice in Exhibit A in
each file of the Source Code. If it is not possible to put such
notice in a particular Source Code file due to its structure, then You
must include such notice in a location (such as a relevant directory)
where a user would be likely to look for such a notice. If You
created one or more Modification(s) You may add your name as a
Contributor to the notice described in Exhibit A. You must also
duplicate this License in any documentation for the Source Code where
You describe recipients' rights or ownership rights relating to
Covered Code. You may choose to offer, and to charge a fee for,
warranty, support, indemnity or liability obligations to one or more
recipients of Covered Code. However, You may do so only on Your own
behalf, and not on behalf of the Initial Developer or any
Contributor. You must make it absolutely clear than any such warranty,
support, indemnity or liability obligation is offered by You alone,
and You hereby agree to indemnify the Initial Developer and every
Contributor for any liability incurred by the Initial Developer or
such Contributor as a result of warranty, support, indemnity or
liability terms You offer.
3.6. Distribution of Executable Versions. You may distribute Covered
Code in Executable form only if the requirements of Section 3.1-3.5
have been met for that Covered Code, and if You include a notice
stating that the Source Code version of the Covered Code is available
under the terms of this License, including a description of how and
where You have fulfilled the obligations of Section 3.2. The notice
must be conspicuously included in any notice in an Executable version,
related documentation or collateral in which You describe recipients'
rights relating to the Covered Code. You may distribute the Executable
version of Covered 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 and that the
license for the Executable version does not attempt to limit or alter
the recipient's rights in the Source Code version from the rights set
forth in this License. If You distribute the Executable version 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 or any Contributor. You hereby agree to indemnify
the Initial Developer and every Contributor for any liability incurred
by the Initial Developer or such Contributor as a result of any such
terms You offer.
3.7. Larger Works. You may create a Larger Work by combining Covered
Code with other code not governed by the terms of this License and
distribute the Larger Work as a single product. In such a case, You
must make sure the requirements of this License are fulfilled for the
Covered Code.
4. Inability to Comply Due to Statute or Regulation.
If it is impossible for You to comply with any of the terms of this
License with respect to some or all of the Covered Code due to
statute, judicial order, or regulation then You must: (a) comply with
the terms of this License to the maximum extent possible; and (b)
describe the limitations and the code they affect. Such description
must be included in the LEGAL file described in Section 3.4 and must
be included with all distributions of the Source Code. Except to the
extent prohibited by statute or regulation, such description must be
sufficiently detailed for a recipient of ordinary skill to be able to
understand it.
5. Application of this License.
This License applies to code to which the Initial Developer has
attached the notice in Exhibit A and to related Covered Code.
6. Versions of the License.
6.1. New Versions. Thomas Richter may publish revised and/or new
versions of the License from time to time. Each version will be given
a distinguishing version number.
6.2. Effect of New Versions. Once Covered Code has been published
under a particular version of the License, You may always continue to
use it under the terms of that version. You may also choose to use
such Covered Code under the terms of any subsequent version of the
License published by Thomas Richter. No one other than Thomas Richter
has the right to modify the terms applicable to Covered Code created
under this License.
6.3. Derivative Works. If You create or use a modified version of
this License (which you may only do in order to apply it to code which
is not already Covered Code governed by this License), You must (a)
rename Your license so that the phrases "TPL", "THOR Software",
"Thomas Richter" or any confusingly similar phrase do not appear in
your license (except to note that your license differs from this
License) and (b) otherwise make it clear that Your version of the
license contains terms which differ from the THOR Public
License. (Filling in the name of the Initial Developer, Original Code
or Contributor in the notice described in Exhibit A shall not of
themselves be deemed to be modifications of this License.)
7. DISCLAIMER OF WARRANTY.
COVERED 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 COVERED 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 COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE
IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER
CONTRIBUTOR) 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 COVERED CODE IS AUTHORIZED HEREUNDER
EXCEPT UNDER THIS DISCLAIMER.
8. 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 Covered 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. If You initiate litigation by asserting a patent infringement
claim (excluding declatory judgment actions) against Initial Developer
or a Contributor (the Initial Developer or Contributor against whom
You file such action is referred to as "Participant") alleging that:
(a) such Participant's Contributor Version directly or indirectly
infringes any patent, then any and all rights granted by such
Participant to You under Sections 2.1 and/or 2.2 of this License
shall, upon 60 days notice from Participant terminate prospectively,
unless if within 60 days after receipt of notice You either: (i) agree
in writing to pay Participant a mutually agreeable reasonable royalty
for Your past and future use of Modifications made by such
Participant, or (ii) withdraw Your litigation claim with respect to
the Contributor Version against such Participant. If within 60 days
of notice, a reasonable royalty and payment arrangement are not
mutually agreed upon in writing by the parties or the litigation claim
is not withdrawn, the rights granted by Participant to You under
Sections 2.1 and/or 2.2 automatically terminate at the expiration of
the 60 day notice period specified above.
(b) any software, hardware, or device, other than such Participant's
Contributor Version, directly or indirectly infringes any patent, then
any rights granted to You by such Participant under Sections 2.1(b)
and 2.2(b) are revoked effective as of the date You first made, used,
sold, distributed, or had made, Modifications made by that
Participant.
8.3. If You assert a patent infringement claim against Participant
alleging that such Participant's Contributor Version directly or
indirectly infringes any patent where such claim is resolved (such as
by license or settlement) prior to the initiation of patent
infringement litigation, then the reasonable value of the licenses
granted by such Participant under Sections 2.1 or 2.2 shall be taken
into account in determining the amount or value of any payment or
license.
8.4. In the event of termination under Sections 8.1 or 8.2 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.
9. 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 COVERED 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.
10. U.S. GOVERNMENT END USERS.
The Covered Code is a "commercial item," as that term is defined in 48
C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software"
and "commercial computer software documentation," as such terms are
used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48
C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995),
all U.S. Government End Users acquire Covered Code with only those
rights set forth herein.
11. 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
German 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 Federal Republic of
Germany, any litigation relating to this License shall be subject to
the jurisdiction of the Federal Courts of the Federal Republic of
Germany, with the losing party responsible for costs, including
without limitation, court costs and reasonable attorneys' fees and
expenses. Any law or regulation which provides that the language of a
contract shall be construed against the drafter shall not apply to
this License.
12. RESPONSIBILITY FOR CLAIMS.
As between Initial Developer and the Contributors, each party is
responsible for claims and damages arising, directly or indirectly,
out of its utilization of rights under this License and You agree to
work with Initial Developer and Contributors to distribute such
responsibility on an equitable basis. Nothing herein is intended or
shall be deemed to constitute any admission of liability.
13. MULTIPLE-LICENSED CODE.
Initial Developer may designate portions of the Covered Code as
Multiple-Licensed. Multiple-Licensed means that the Initial Developer
permits you to utilize portions of the Covered Code under Your choice
of the TPL or the alternative licenses, if any, specified by the
Initial Developer in the file described in Exhibit A.
EXHIBIT A - THOR Public License.
The contents of this file are subject to the THOR Public License
Version 1.0 (the "License"); you may not use this file except in
compliance with the License.
Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
the License for the specificlanguage governing rights and limitations
under the License.
The Original Code is ______________________________________.
The Initial Developer of the Original Code is _____________.
Portions created by ______________________ are
Copyright (C) ______ _______________________.
All Rights Reserved.
Contributor(s): ______________________________________.
Alternatively, the contents of this file may be used under the terms
of the _____ license (the [___] License), in which case the provisions
of [______] License are applicable instead of those above. If you
wish to allow use of your version of this file only under the terms of
the [____] License and not to allow others to use your version of this
file under the TPL, indicate your decision by deleting the provisions
above and replace them with the notice and other provisions required
by the [___] License. If you do not delete the provisions above, a
recipient may use your version of this file under either the TPL or
the [___] License."
[NOTE: The text of this Exhibit A may differ slightly from the text of
the notices in the Source Code files of the Original Code. You should
use the text of this Exhibit A rather than the text found in the
Original Code Source Code for Your Modifications.]

32
test/simpleTestForGenerator/UCAR.txt Normal file
View File

@@ -0,0 +1,32 @@
Copyright 2014 University Corporation for Atmospheric Research and contributors.
All rights reserved.
This software was developed by the Unidata Program Center of the
University Corporation for Atmospheric Research (UCAR)
<http://www.unidata.ucar.edu>.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
1) Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2) Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
3) Neither the names of the development group, the copyright holders, nor the
names of contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
4) This license shall terminate automatically and you may no longer exercise
any of the rights granted to you by this license as of the date you
commence an action, including a cross-claim or counterclaim, against
the copyright holders or any contributor alleging that this software
infringes a patent. This termination provision shall not apply for an
action alleging patent infringement by combinations of this software with
other software or hardware.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE CONTRIBUTORS
OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE.

3
test/simpleTestForGenerator/snprintf.txt Normal file
View File

@@ -0,0 +1,3 @@
Copyright Patrick Powell 1995
This code is based on code written by Patrick Powell (papowell@astart.com) It may be used for any purpose as long as this notice remains intact on all source code distributions

11
test/simpleTestForGenerator/w3m.txt Normal file
View File

@@ -0,0 +1,11 @@
(C) Copyright 1994-2002 by Akinori Ito
(C) Copyright 2002-2011 by Akinori Ito, Hironori Sakamoto, Fumitoshi Ukai
Use, modification and redistribution of this software is hereby granted,
provided that this entire copyright notice is included on any copies of
this software and applications and derivations thereof.
This software is provided on an "as is" basis, without warranty of any
kind, either expressed or implied, as to any matter including, but not
limited to warranty of fitness of purpose, or merchantability, or
results obtained from use of this software.

14
test/simpleTestForGenerator/xlock.txt Normal file
View File

@@ -0,0 +1,14 @@
Copyright (c) 1990 by Sun Microsystems, Inc.
Author: Patrick J. Naughton naughton@wind.sun.com
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and
that both that copyright notice and this permission notice appear in
supporting documentation.
This file is provided AS IS with no warranties of any kind. The author
shall have no liability with respect to the infringement of copyrights,
trade secrets or any patents by this file or any part thereof. In no event
will the author be liable for any lost revenue or profits or other special,
indirect and consequential damages.