Arthit Suriyawongkul

Just to documented issue/PRs and discussion points (resolved for 3.0.1) from spec-parser repo related to CreationInfo, which is related to https://github.com/spdx/spdx-3-model/issues/306 - https://github.com/spdx/spec-parser/issues/153 - https://github.com/spdx/spec-parser/pull/154 - https://github.com/spdx/spec-parser/pull/159

@aamedina @goneall @zvr with #867 already merged, does this issue considered fixed and can be closed?

Related: - #782

@ilans SHACL-related and maybe of your interest as well

Thanks Kate. I will try to provide some further information here so people can give more of their thoughts. - There is no comparable table like one from [EU General...

Discussed in [AI Profile WG meeting 2024-03-06](https://github.com/spdx/meetings/pull/649). No conclusion yet. But the meeting agree in that the AI Profile should be generic and if there's a need for jurisdiction-specific, a...

Agree. We can keep the 4 risk types (levels) as they are now. And probably rename the property to `generalRiskAssessment` for 3.0.

PR #675 is open to make it more explicit in the description of `safetyRiskAsssement` property that the current categorization is according to EU General Risk Assessment Methodology, and not the...

“high” in EU General Risk Assessment Methodology and “high” in EU AI Act mean different things. - From 2025-05-27 Tech Team call, it may be possible to use "DefinedType" from...

#653 may related to this issue (see "Relevant fields in 3.0" section)