Arthit Suriyawongkul

See a related case (similar mapping to property, but on a different direction) at https://github.com/codemeta/codemeta/issues/353#issuecomment-1950040604

Experiment notes: - Successfully Validated with all the tools (`ajv`, `check-jsonschema`, `pyshacl`) listed at https://github.com/spdx/spdx-3-model/blob/main/serialization/json_ld/validation.md - Warning messages of `ajv` and `check-jsonschema` sometimes are not very helpful - If there're...

This this how I put `AnyLicneseInfo` in this example, to please the SHACL validator -- as a workaround for the lacking of `ListedLicense` at this moment. (This will be removed...

@rgopikrishnan91 this PR please Gopi

@rgopikrishnan91 @bennetkl please kindly review. Thank you.

I'm thinking about creating a Standard class, based on properties proposed in #387 (particularly in https://github.com/spdx/spdx-3-model/issues/387#issuecomment-1925876552 ). And we may add few relationship types that can link between Artifact and...

Validation failed due to individual-related issue. Turn to draft for now.

The validation script can run and print results as expected. (But the validation result of the file being tested is failed)

@goneall the validation fail is from the known issue of missing CreationInfo for individuals. We need to add it when generating the ontology file, with this PR https://github.com/spdx/spec-parser/pull/154 or similar.

@goneall @zvr @ilans the CreationInfo issue is probably fixed now. But because of the assessedElement range update, the example failed. I will update the example and check again.