[x3d-public] SampleAsset Repo Licenses [was: Clarifications on "glTF Interactivity Extensions Approach Finalization: Your Feedback Needed!"]
Leonard Daly
Leonard.Daly at realism.com
Sat Jun 7 06:34:28 PDT 2025
Content in the repo is individually licensed. You need to look at the
README for each model to determine the license for that model (including
geometry and textures). The directory you pointed at contains the text
of each license. If there is a piece of content whose license is not
clear, check the
https://github.com/KhronosGroup/glTF-Sample-Assets/blob/main/.reuse/reuse.spdx
file. It has the license for each file in the repo.
If you find an issue with a license, please create a GitHub comment.
In many cases you can copy and modify the models as you see fit. That
applies to anything with a CC0 or CC-BY license. Some models have other
licenses that may (legally) prevent you from doing so. Most of the
licenses require proper attribution. That includes maintaining the
copyright and license info. You need to check the specific licenses. If
you use a model with an embedded logo, you MUST acknowledge proper
ownership of the logo AND keep to the usage terms. Some of the Khronos
logos allow use on models provided the usage adheres to the logo use
policy.
All of the license information is in the metadata.json file in each
model directory (e.g.,
https://github.com/KhronosGroup/glTF-Sample-Assets/blob/main/Models/PotOfCoals/metadata.json).
Leonard Daly
On 6/6/2025 9:10 PM, John Carlson wrote:
> Is there anyway someone can clarify licenses for data in this repository?
>
>
> https://github.com/KhronosGroup/glTF-Sample-Assets/tree/main/LICENSES
>
> I’m not really wanting to touch any assets in this repository, but
> where are the glTF viewer conformance models?
>
> What I want to do is convert these glTF assets to X3D JSON with
> create3000’s x3d-tidy, then validate with coderextreme’s x3dvalidate,
> which includes schema for X_ITE material extensions from glTF.
>
> What I need to know is, can I put the X3D JSON versions into a
> repository, without carrying all the above licenses over.
>
> John
>
> On Fri, Jun 6, 2025 at 3:56 PM Leonard Daly via x3d-public
> <x3d-public at web3d.org> wrote:
>
> I think a few of the statements are incorrect or not clear. My
> comments strictly address those items that discuss
> Khronos-developed material.
>
>
> On 6/6/2025 10:33 AM, Brutzman, Donald (Don) (CIV) via x3d-public
> wrote:
>> Strategic Review
>>
>> *
>> The work looks thorough and consistently high quality,
>> matching other Khronos specifications.
>>
> Thank you. I will pass on this praise.
>
>
>> *
>> The Khronos license terms appear to be unchanged since our
>> prior review.
>> o
>> Use of the extension requires either membership as an
>> Adopter of Khronos IPR policy, or else " express prior
>> written permission of Khronos."
>> o
>> Patented materials are included in the specification
>> (though not specifically identified).
>> o
>> https://github.com/KhronosGroup/glTF/blob/interactivity/extensions/2.0/Khronos/KHR_interactivity/Specification.adoc#foreword
>>
>
> There has been no change to the Khronos IP policy. The full first
> paragraph of statement in the draft specification is:
>
> This specification is protected by copyright laws and contains
> material proprietary to Khronos. Except as described by these
> terms, it or any components may not be reproduced,
> republished, distributed, transmitted, displayed, broadcast,
> or otherwise exploited in any manner without the express prior
> written permission of Khronos.
>
> Note the important clause at the beginning of the second sentence:
> "Except as described by these terms". The subsequent paragraphs
> provide the terms, specifically:
>
>
> Khronos grants a conditional copyright license to use and
> reproduce the unmodified specification for any purpose,
> without fee or royalty, EXCEPT no licenses to any patent,
> trademark or other intellectual property rights are granted
> under these terms. Parties desiring to implement the
> specification *and *make use of Khronos trademarks in relation
> to that implementation, *and *receive reciprocal patent
> license protection under the Khronos IP Policy must become
> Adopters... [bolding is mine - ld]
>
> If you have no interest in using Khronos trademarks or receiving
> reciprocal patent licenses, then you do not need to become an
> "Adopter".
>
>
> Note that the specification document is licensed as "CC-BY 4.0".
>
>
>>
>> Technical Review
>>
>> *
>> This extension is for JavaScript programmers who want to
>> animate glTF models.
>>
>
> There is no programming required for the Interactivity extension.
> glTF viewers that correctly implement the specification handle the
> data that is stored in the glTF file structure and act according
> to that data. The data is not code (JavaScript or anything else).
> Also not that "animate" means any kind of change to the model or
> environment.
>
>
> Leonard Daly
>
>
>
>> ...
>>
>> Sincerely, Don Brutzman and Dick Puk
>>
>>
>> all the best, Don
>>
>> --
>>
>> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman at nps.edu
>>
>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
>> +1.831.656.2149
>>
>> X3D graphics, virtual worlds, navy robotics
>> https://faculty.nps.edu/brutzman
>>
> --
> *Leonard Daly*
> 3D Systems Engineering
> President, Daly Realism - /Creating the Future/
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
--
*Leonard Daly*
3D Systems Engineering
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20250607/d37ea54e/attachment.html>
More information about the x3d-public
mailing list