Atlas - openxr_license.txt
Home / ext / JunkDrawer / releases / pub / LWJGL / lwjgl-3.3.6 / lwjgl-openxr
Lines: 1 | Size: 5472 bytes
[Download] [Show on GitHub] [Search similar files] [Raw] [Raw (proxy)] 
[FILE BEGIN]
1= COPYING.adoc for the Khronos Group OpenXR projects
2
3// Copyright (c) 2020-2021, The Khronos Group Inc.
4//
5// SPDX-License-Identifier: CC-BY-4.0
6
7This document is shared across a number of OpenXR GitHub projects, as the
8set of files in those projects is partially overlapping.
9(There is a single "source of truth" internal Khronos GitLab repo these
10GitHub repositories interact with.)
11
12== Licenses
13
14The OpenXR GitHub projects use several licenses.
15In general, we work to maintain compliance with the
16https://reuse.software/spec/[REUSE 3.0 specification] with clear copyright
17holders and license identifier listed for each file, preferably in each
18file.
19Where this is not possible, or e.g. when we are using files unmodified from
20other open-source projects, license data is listed:
21
22* in an adjacent file of the same name, with the additional extension
23  "`.license`"
24* in the repository-wide "`.reuse/dep5`" copyright description
25  https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/["DEP5"
26  machine-readable copyright data] file.
27
28The https://github.com/fsfe/reuse-tool["`reuse`" command line tool] can be
29used to create a software bill of materials in SPDX format from this data.
30Note that this tool will typically exclude the generated files, so if the
31BOM is important to you, you may consider using the
32https://github.com/KhronosGroup/OpenXR-SDK[OpenXR-SDK] repository that
33contains the API headers and the loader source with all generated files
34pre-generated.
35
36The data in/adjacent to each file is the authoritative license and copyright
37data.
38However, for ease of understanding, the following general practices can be
39observed.
40(If in doubt, or if the following summary conflicts with the per-file data,
41the per-file data remains authoritative.)
42
43* The source files (in asciidoctor and other formats) for the OpenXR
44  Specification, reference pages, and supporting documentation are licensed
45  under the Creative Commons Attribution 4.0 International License (SPDX
46  license identifier "`CC-BY-4.0`").
47* Header files, scripts, programs, XML files, and other tooling used or
48  generated as part of the build process is licensed under the Apache
49  License, Version 2.0.
50* For compatibility with external developers working in GPLed projects who
51  have requested it, the main OpenXR headers, XML registry, and loader
52  source are licensed under a dual license with the SPDX license identifier
53  "`Apache-2.0 OR MIT`" .
54  Relevant files include:
55** "`specification/registry/xr.xml`"
56** "`include/openxr/openxr_platform_defines.h`"
57** The generated OpenXR headers "`openxr.h`", "`openxr_platform.h`", and
58   "`openxr_reflection.h`".
59** Source files in "`src/loader/`", and a few files in "`src/common/`".
60** Generated source files used by the loader (including pre-generated in
61   OpenXR-SDK): "`common_config.h`", "`xr_generated_loader.cpp`", and
62   "`xr_generated_loader.hpp`".
63* There are a few files adopted from other open source projects.
64  Such files continue under their original licenses, and appropriately
65  annotated in accordance with REUSE.
66* Some generated, transient files produced during the course of building the
67  specification, headers, or other targets may not have copyrights.
68  These are typically very short asciidoc fragments describing parts of the
69  OpenXR API, and are incorporated by reference into specification or
70  reference page builds.
71
72Users outside Khronos who create and post OpenXR Specifications, whether
73modified or not, should use the CC-BY-4.0 license on the output documents
74(HTML, PDF, etc.) they generate.
75
76
77== Frequently Asked Questions
78
79Q: Why are the HTML and PDF Specifications posted on Khronos' website under
80a license which is neither CC-BY-4.0 nor Apache 2.0?
81
82A: The Specifications posted by Khronos in the OpenXR Registry are licensed
83under the proprietary Khronos Specification License.
84Only these Specifications are Ratified by the Khronos Board of Promoters,
85and therefore they are the only Specifications covered by the Khronos
86Intellectual Property Rights Policy.
87
88
89Q: Does Khronos allow the creation and distribution of modified versions of
90the OpenXR Specification, such as translations to other languages?
91
92A: Yes.
93Such modified Specifications, since they are not created by Khronos, should
94be placed under the CC-BY-4.0 license.
95If you believe your modifications are of general interest, consider
96contributing them back by making a pull request (PR) on the OpenXR-Docs
97project.
98
99
100Q: Can I contribute changes to the OpenXR Specification?
101
102A: Yes, by opening an Issue or Pull Request (PR) on the
103link:https://github.com/KhronosGroup/OpenXR-Docs/[OpenXR-Docs] GitHub
104project.
105You must execute a click-through Contributor License Agreement, which brings
106your changes under the umbrella of the Khronos IP policy.
107
108
109Q: Can you change the license on your files so they're compatible with my
110license?
111
112A: We are using a dual license license on `xr.xml`, the main API headers,
113and the loader source files, to make them compatible with GPL-2.0- and
114LGPL-2.0/2.1-licensed projects.
115This replaces earlier approaches of an MIT-like license on the XML and
116Apache 2.0 on all headers, and allows use of the SPDX license identifier
117"`Apache-2.0 OR MIT`" to denote the license.
118
119If you *require* this same compatibility for use of other Apache-2.0
120licensed files in our repository, please raise an issue identifying the
121files and we will consider changing those specific files to the dual license
122as well.
123
124
[FILE END]
(C) 2025 0x4248
(C) 2025 4248 Media and 4248 Systems, All part of 0x4248
See LICENCE files for more information. Not all files are by 0x4248 always check Licencing.