I'm thinking about license info in #glTF because it may be more important in the metaverse era. For example, if a glTF asset under the license that doesn't allow redistribution is uploaded to a metaverse application the application shouldn't show the download button for the model
Conversation
The glTF core spec has asset.copyright field but it is free text so it may not be machine readable. registry.khronos.org/glTF/specs/2.0
1
2
The glTF KHR_xmp_json_ld extension allows XMP metadata in glTF. XMP Rights has Certificate field which takes license URL. But still hard for applications to know what is allowed for the asset from the license URL or its content. github.com/KhronosGroup/g github.com/adobe/xmp-docs
Replying to
It's helpful if there is a way for applications to quickly know what is allowed for assets/licenses. A few ideas.
1. A new glTF extension that allows to indicate what allows/disallows with predefined boolean flag sets eg. redistribution: true
2
1
2. A new library or web service that takes license URL and returns the flags what allows/disallows eg: lib.getAllowList(url) -> {redistribution: true}
Related:
1
1
1
I know VRM permission field but I feel it is a bit too complex and VRM/avatar specific. I think we need simpler, more generic, and standard machine readable permissions info in glTF. github.com/vrm-c/vrm-spec
1
2
And honestly I don't prefer fine grained custom permission controls. Assets should specify standard licenses instead.