Arthit Suriyawongkul

> I wonder if we should consolidate all the serialization information into the spec and remove the serialization folder from this repo. This would avoid any possibility of having conflicting...

Created a new issue https://github.com/spdx/spdx-spec/issues/1279 (on spdx-spec repo) for serialization information consolidation

> maybe we need to write best practices for writing descriptions. @VladimirAlexiev We will be very happy if you can help add bullets in https://github.com/spdx/spdx-3-model/blob/develop/docs/format.md#writing-style

Agree on not having specific property value as a requirement (for example, primaryPurpose) as there can be a case that an element is built for one thing but it is...

Fyi, please look at proposal for new fields related to AI agents at #1091

[SoftwareArtifact](https://spdx.github.io/spdx-spec/v3.0.1/model/Software/Classes/SoftwareArtifact/), a subclass of Agent, add properties more specific to software agent. But I think we may not have a thing that can cover `enabledByDefault`. The currently proposed `AutomationLevel` (see...

The Cdx* classes and properties are provided for compatibility with CycloneDX 'properties' where duplicated keys may be possible. It is for a direct mapping. From https://spdx.github.io/spdx-spec/v3.0.1/model/Extension/Classes/CdxPropertiesExtension/ > Unlike key-value stores,...

Similar discussion on "meaningful prefixes" in #1010.

If it is the same concept, it should use the same persistent IRI. While owl:sameAs, etc. can be used, it will complicated query over time (and owl-reasoning is computationally expensive)....

This is how SPDX 3 spec in the model part is currently written, based on Markdown format: - https://github.com/spdx/spdx-3-model/blob/develop/README.md#formats - https://github.com/spdx/spdx-3-model/blob/develop/docs/format.md The spec website is generated using this workflow: -...