Gary O'Neall
Gary O'Neall
The differences are symptomatic of the `jsonld-annotations.ttl` file being ignored. The file does look in place and there are no errors or warnings in the CI output.
Looks like an inconsistency between the spec parser and the ttl file.
I ran shacl2code locally with an updated context file and context URL parameter. It passed validation. It matched the previous schema file with only a difference in the extension: ```...
l am going to upload the schema file I generated locally to spdx.org/rdf/3.0.1/spdx-json-schema.json. I'll leave the 3.0 version as is. We can leave this issue open to track getting things...
My understanding is the semantic meaning for at least some of the `Other` enum types is "I know that this is something other than what is on the list of...
The URL now appears to work - @bact - can you re-trigger the CI - perhaps by rebasing - and see if it passes?
> We don't yet have a clear path to republish `support/3.0` yet. > > As I understand, if we are still in 3.0.x and don't have 3.1 yet, do we...
@zvr - Is this something that can be fixed in the spec parser? @augelu-tng - Do you think this is a high enough priority for the 3.0.2 release or would...
Moved to 3.1 milestone to close before next release
@bact @zvr - can we close this and the related #1129 issues since we already submitted to ISO? If not, should we discuss on one of the tech calls?