#Is 'adapted material' based on the Vulkan specification allowed?

7 messages · Page 1 of 1 (latest)

torn nexus
#

Hello, I'm new to Vulkan and decided to learn the API by writing a set of .NET bindings for it. May at some point in the future, I intend to publish the work under a permissive license (probably MIT). To my understanding, this is fine as the Vulkan API code is open-source; only proper attribution is required.

However: For the code / API bindings that I write I'm adding inline API documentation which contains a lot of copy & paste from the Vulkan Specification. The Vulkan Specification license is more restrictive in regards to modified material.

So the question is: Is it allowed to create/publish source code with inline documentation where fragments of the inline documentation are copied from the official Vulkan specification?

fiery pewter
#

the website files are either Apache-2.0 or Creative Commons Attribution 4.0 International (some others in there too)
the xml file is MIT or Apache 2.0
so you'd have to look up specifically what are you referencing
the tutorials have different licenses too

torn nexus
#

AFAIK, it should be ok to copy & paste fragments of the specification text, but I wanted to ask first.

GitHub

The Vulkan API Specification and related tools. Contribute to KhronosGroup/Vulkan-Docs development by creating an account on GitHub.

fiery pewter
#

for actual legal advice you'd have to talk to a lawyer, we can't give you that certainty

soft ocean
#

no lawyer, but I know for a fact both Vulkan Validation Layers and the Mesa drivers all quote the spec

fiery pewter
#

iirc vvl quotes the xml which is under apache 2/MIT

soft ocean
#

VVL quotes everything!