-
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
Create an IndividualElement class #937
Conversation
This will allow individuals to be of a type that can be instantiated and could resolve the issue with SHACL validation failing spdx/spec-parser#165
See this conversation in #936 for context |
This might make it kinda hard to know how named individuals are supposed to be used; I think maybe we can deal with it if necessary but I need to do some testing before we go ahead and make this change |
Ah, you know what, I was think of enums. This should be fine |
We'll need this PR (or an alternative) if we continue to restrict instantiating abstract classes in SHACL, so changing this as ready for review. |
Co-authored-by: Arthit Suriyawongkul <[email protected]> Signed-off-by: Alexios Zavras (zvr) <[email protected]>
Approved, providing the suggested "for Core profile" by @zvr is added to the Description. |
Co-authored-by: Alexios Zavras (zvr) <[email protected]> Signed-off-by: Gary O'Neall <[email protected]>
@zvr - Accepted suggestion - if you could approve and merge everything should be working. |
This will allow individuals to be of a type that can be instantiated and could resolve the issue with SHACL validation failing spdx/spec-parser#165