From e52e23f041e6802d5695258d61eb184428dab1cc Mon Sep 17 00:00:00 2001 From: Samuel Dionne-Riel Date: Wed, 8 Apr 2026 13:48:37 -0400 Subject: [PATCH] doc/meta: Fix documentation for `edition` CPE field MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The field could have been simply removed from the list, as it is not used, but it should be present in that form at least for *some undefined* length of time to present as a correction for anyone using the `edition` field mistakenly. My claim comes from the literal source listed in the next paragraph (NISTIR 7695), the first few words of `5.3.3.6` are: > The edition attribute is considered deprecated Thus we consider it deprecated. Furthermore the section documents that it should be using the value `ANY`. It could be considered debatable as `NA` should be used “when there is no legal or meaningful value for that attribute, or when that attribute is not used as part of the description”... But the spec states that `ANY` should be used, so we state `ANY` should be used. --- doc/stdenv/meta.chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/stdenv/meta.chapter.md b/doc/stdenv/meta.chapter.md index 285211a401da..d1823717b4b8 100644 --- a/doc/stdenv/meta.chapter.md +++ b/doc/stdenv/meta.chapter.md @@ -292,7 +292,7 @@ Some of them are as follows: * *product* - name of the package * *version* - version of the package * *update* - name of the latest update, can be a patch version for semantically versioned packages -* *edition* - any additional specification about the version +* *edition* - deprecated and should be set to `*` You can find information about all of these attributes in the [official specification](https://csrc.nist.gov/projects/security-content-automation-protocol/specifications/cpe/naming) (heading 5.3.3, pages 11-13).