Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please clarify the licensing of the SARIF schema files #583

Closed
davidmalcolm opened this issue May 25, 2023 · 3 comments
Closed

Please clarify the licensing of the SARIF schema files #583

davidmalcolm opened this issue May 25, 2023 · 3 comments

Comments

@davidmalcolm
Copy link

(as noted in #498 (comment) )

What's the license of the schema files? In particular, what permissions are granted (if any) to redistribute the schemata?

Note that there could be two sets of schemata:

Hopefully these are bit-for-bit identical, but they might not be.

I'm not a lawyer, but it appears to me that the LICENSE.md from this repo does implicitly grant licenses for the files below https://github.com/oasis-tcs/sarif-spec/tree/main/Schemata, and 10.1 RAND Mode TC Requirements seems to imply a grant of redistibutability.

Is it possible to add a LICENSE.md adjacent to the schema files in their canonical location? I believe that would make it clear that there is a license grant on these files. Alternatively, is there some common policy covering docs.oasis-open.org that I missed? Sorry if that's the case.

The specific use case I have is that I'm hoping to add validation against the SARIF schema to GCC's testsuite to test my SARIF creation code; this testsuite ideally to be runnable in a locked-down environment with no network access (so that we can bootstrap a toolchain repeatedly from a known bundle of bits). Hence I would like to add a copy of the SARIF schemata to GCC's source tree, but for this I need clarity that these files are redistributable.

@dmk42
Copy link
Contributor

dmk42 commented May 26, 2023

Good news. The following is an exact quote from OASIS.
"They are free to incorporate it into their implementation. No need for special permission or paperwork from OASIS."

@dmk42
Copy link
Contributor

dmk42 commented Jun 23, 2023

Just an update. OASIS says that although you do not need permission from them to incorporate the schema into your compiler, they understand that some companies are squeamish about such things, and OASIS will write a letter of permission if your company asks for it.

@dmk42
Copy link
Contributor

dmk42 commented Dec 19, 2023

I believe this issues is now addressed with my earlier comment above. Please feel free to reopen it if you disagree.

@dmk42 dmk42 closed this as completed Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants