Arthit Suriyawongkul

PR #1320 will publish content in "support/3.0" branch to https://spdx.github.io/spdx-spec/v3.0.2-dev/ (and eventually https://spdx.github.io/spdx-spec/v3.0.2/ )

Can understand where the SemBr comes from. The rationale to support a shorter line length is it made Git diff smaller and less noisy for human reviewers, at least on...

@goneall should we move this to spdx-spec repo and label it as "website improvement"? As it is related to HTTP redirection/resolution.

ref: Best Practice Recipes for Publishing RDF Vocabularies https://www.w3.org/TR/swbp-vocab-pub/

Agree on the approach to do it in spec-parser as it is where we have the knowledge of the actual model (no need to do heuristic guesswork by looking at...

Thank you. SPDX 3.1 will have QUDT. See: - https://github.com/spdx/spdx-3-model/blob/develop/model/Core/Classes/UnitOfMeasure.md - https://github.com/spdx/spdx-3-model/blob/develop/model/Core/Properties/quantity.md - https://github.com/spdx/spdx-3-model/blob/develop/model/Core/Properties/unitQUDT.md

@VladimirAlexiev I haven't read all your comments on every issue opened in details yet (I will), but in general thank you for your kind suggestions with the intention to improve...

> - why `quantity` is defined as string not decimal? > - will `unitQUDT` be the plain string "KiloW-HR" vs "MegaJ"? If so, you can use this in the context...

I can see the point of keeping the original quantity form as a string, as irrational numbers cannot be precisely represented with a number of finite digits. Apart from operationalization...

pyshacl failed. It can't handle external IDs. I have tried spdx3-validate the example, it is valid. If spdx3-validate can already handle SHACL validation, we may like to remove pyshacl from...