Alexios Zavras (zvr)
Alexios Zavras (zvr)
The SPDX standard mentions these naming conventions, depending on the format used: | Format | Extension | | ----------- | ----------- | | Tag:Value | `*.spdx` | | RDF |...
No, not related to spec-parser. The current mkdocs.yml file includes an entry for `model/Software/Properties/isDirectory.md` which is not there any more. This is due to #916.
Closing this
I think the glossary is more about the model and I'm not sure it belongs in the spec.
As you write, we already have `DictionaryEntry` for exactly this reason and we have implemented "dictionaries" by having multiple instances of this type. I'm not sure exactly why there is...
If the whole purpose is to simply group the entries together, I don't think there is a need for a "dictionary" class. For example, when we record a build, it...
OK, let me try and write the alternative explicitly. So, in the current state where `environment` is a 0..* `DictionaryEntry`, it is serialized, as shown in the previous comment, this...
@VenkatTechnologist can we close this one?
In general we need to have ``` see https://spdx.org ``` and not ``` see [SPDX](https://spdx.org) ``` because I think it was a restriction of the ISO standard formatting (IIRC). But...
I'd say we pause this one till we know (and test) the exact production process, so that we know what the requirements will be. It makes no sense to make...