Commit 9ac62ecd authored by Samuel Dionne-Riel's avatar Samuel Dionne-Riel
Browse files

doc/meta: Reword *logical values* for CPEs 

The original wording missed the *not meaningful* nuance, and adding an
`or` clause within the sentence would have made it hard to understand.

Instead, it is now split into a list, and ordered in the same order as
found in `5.3.1` in NISTIR 7695.

The logical name used by the specification (ANY/NA) was also added.
parent 68d8aa3d

doc/stdenv/meta.chapter.md

+4 −1
Original line number Diff line number Diff line
@@ -296,7 +296,10 @@ Some of them are as follows: 


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).



Any fields that don't have a value are set to either `-` if the value is not available or `*` when the field can match any value.

Any fields that don't have a value are set to either:



* `*` (ANY) when the field can match any value

* `-` (NA) when the value is not meaningful or not used in the description



For example, for glibc 2.40.1 CPE would be `cpe:2.3:a:gnu:glibc:2.40:1:*:*:*:*:*:*`.