-
Notifications
You must be signed in to change notification settings - Fork 48
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
Shape validation fails related to 5 named individuals #936
Comments
So, the first is because we had said that It will be fixed when I merge the fix for spdx/spec-parser#160 |
Shall we have different issues for each error? The second one is the good ol' spdx/spec-parser#74 |
On yesterday's call, I suggested not lifting the restriction - based on this, I'll retract that recommendation - more important to get the validation to work. |
Agree. I will separate one issue per error type. |
I was able to I hand edited the model.ttl file to pass the validation. I had to make the following 3 types of changes:
Attached is the working model.ttl file. I'll add 3 issues to the spec parser for each of the above changes. |
Thank you @goneall. I agree with the analysis |
I forgot about one other change I made to the working model.ttl file: Changed This is covered in the existing spec parser issue spdx/spec-parser#160 |
The problem is that we are defining named individuals that are explicitly concrete instaniations of abstract classes (e.g. Element is abstract, but NoneElement is now a concrete instance of it). This will be a problem for any way that we validate abstract classes, so I don't think fixing it by reverting the spec parser change is a good idea. |
Oooops! You are absolutely correct, @JPEWdev . What is the way forward on this? We created the Maybe they should not be simple |
Thanks @JPEWdev - I was beating my head against the wall trying to figure out why this showed up now. For licensing, we have a class Perhaps for elements we need an |
I just tried implementing an Note that I'm also getting a constraint error on licensing individuals and on the Agent defined in the example file. |
I added a draft PR with the IndividualElement implementation: #937 |
Note that with spdx/spec-parser#169, the string type issues and BlankNode issues are now resolved (you may need to reload the https://spdx.github.io/spdx-spec/v3.0.1/rdf/spdx-model.ttl or rerun your workflow). |
Resolved with the above referenced merges |
These violations are all new and mostly related to the 5 new
creationInfo_*
:pyshacl produces
32 violations. Update 2024-12-10 09:24 UTC: 22 violations.For example:
BlankNode-- Fixed:Agent:
string-- Fixed:Abstract class:
spdx3-validate 0.0.5 also produce similar violations:
BlankNode-- Fixed:Agent:
string:-- Fixed:Abstract class:
Note
Prior to the merges of #933 and spdx/spec-parser#159, there were 5 violations.
All of them are about missing CreationInfo:
https://github.com/spdx/spdx-spec/actions/runs/11867207295/job/33074971508?pr=1134
Those 5 violations are now fixed.
The text was updated successfully, but these errors were encountered: