-
Notifications
You must be signed in to change notification settings - Fork 141
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
Setup RDF redirections in spdx.org (to fix failed validation) #1108
Comments
I wonder if I should go ahead and setup the 3.0.1 redirects now since they are live. We should probably wait for the 3.0 redirects until final release. @kestewart @bact @zvr - thoughts? |
Ideally, for 3.0.1 (Items 1-4) we should wait until the final release. For 3.0.0 (Items 5-8), they are broken* now and need to be fixed by modifying redirections at spdx.org (5a-8a) together with PR #1109 (5b-8b). *Broken here means the version in URL and the version in the content are not matched. This made, for example, our validator failed. |
Just saw a slack message on 3.0.0 being broken - so I'll go ahead and merge #1109 and setup the redirects. I'll leave the 3.0.1 and 3.0 redirects until after release. |
Redirects for 3.0.0 (Items 5-8) are in place and PR #1109 has been merged. It may take some time for the changes to propagate we may need to clear our browser caches for it to take effect. |
Thank you. I will try and report. |
Agree. |
Confirmed https://spdx.org/rdf/3.0.0/spdx-context.jsonld is now redirected to https://spdx.github.io/spdx-spec/v3.0.0/rdf/spdx-model.ttl Browser cached may needed. |
3.0.0 validation is good now. 3.0.1 validation is waiting for Items 1-4. |
@goneall I have changed my mind. We may need 3.0.1 redirects now to pass the validation. 3.0 can be wait until after 3.0.1 actually release. |
All the 3.0.1 redirects are now in place - we just have the 3.0 redirects which we can do after the release. |
Thank you Gary. |
Change redirects for 3.0 -> 3.0.1 version |
For 3.0.1:
--
For 3.0.0:
https://spdx.github.io/spdx-spec/v3.0/model/spdx-context.jsonld - which its content is now the latest of v3.0 (now v3.0.1) - and this made some validations fail, as they may expected 3.0.0 but received 3.0.1
(URL lists based on spdx/spdx-3-model#679 (comment) )
The text was updated successfully, but these errors were encountered: