commonkeySize and specifiedkeySize properties definition: improvements

[toscalix]

Background

• Comment done by @zvr to the Crypto Algorithms List Properties Description #15
• Discussion about the above comment during the meeting held on 2025-08-13
• The list is not planned to become a model but the Crypto Algorithms List Group expect some profiles to pick up or use some elements

Description

• Applying this agreement to commonkeySize property will require some adaptation of the current version of the list
• There is consensus on the group on describing this property so several commonkeySize are allowed, avoiding the usage of the operator "AND", as suggested by @zvr
• A discussion is required on extending this approach to specifiedkeySize when several values should be specified in the list.
• A discussion is required on how to adapt this policy to the case of ranges. In the current version of the list the operator "TO" is used

Actions

• Prioritize this discussion during September 2025 to improve the current version of the list in the line of the current agreement (commonkeySize).
• Provide an example on how to express several dicrete values on commonkeySize property
• Open a PR with the changes required in the corresponding algorithms (.yaml files) including the new way to express several discrete values on the commonkeySize property: Remove the AND operator for a yaml expression #23
• OPen an PR with the changes required in the List properties file to describe the new way to have several values in a property, in this case, commonkeySize property
• Provide an example on how to express ranges of values on specifiedkeySize property
• Reach a consensus on how to express ranges and apply ranges to specifiedkeySize
• Open a PR with the changes required in the List properties file and the affected elements of the list to express ranges in specifiedkeySize yaml compatible expression instead of operator TO #26

DoD

• Link to the PR corresponding to the commonkeySize property description changes expressing several discrete values fb6a53f
  • PR merged
• Link to the PR corresponding to the commonkeySize list elements changes expressing several discrete values Remove the AND operator for a yaml expression #23
  • PR merged
• Link to the PR corresponding to the specifiedkeySize property description changes expressing ranges of values fb6a53f
  • PR merged
• Link to the PR corresponding to the specifiedkeySize list element changes expressing ranges of values yaml compatible expression instead of operator TO #26
  • PR merged

[toscalix]

How to express a discrete amount of values in a property: example

This is an example of how we are going to avoid the usage of the operator AND when a discrete number of options are possible/appropriate for a specific property, in this case commonkeySize.

The values should be ordered in ascendant order

shax.yaml now

# SPDX-License-Identifier: CC0-1.0
id: shax
name: SHA-x (SHA-1, SHA-256, etc.)
cryptoClass: Cryptographic-Hash-Function/Hash-Function
commonkeySize: '128'AND'512
specifiedkeySize: '224'TO'512'

This is the current version of the list

shax.yaml then

# SPDX-License-Identifier: CC0-1.0
id: shax
name: SHA-x (SHA-1, SHA-256, etc.)
cryptoClass: Cryptographic-Hash-Function/Hash-Function
commonkeySize: '128'
commonkeySize: '512
specifiedkeySize: '224'TO'512'

This is is the proposal based on the discussion/agreement made at the meeting linked above

[zvr]

The YAML way of having multiple values for a single key is either:

commonKeySize: ['128', '512']

or

commonKeySize:
  - '128'
  - '512'

Why do you want to introduce another?

[toscalix]

No need to invent anything new. #23 follows your suggestion

[toscalix]

Proposal to express ranges

In the current version of the spdx crypto algorithms list we have the following way to express a range of values in a property

shax

# SPDX-License-Identifier: CC0-1.0

id: shax
name: SHA-x (SHA-1, SHA-256, etc.)
cryptoClass: Cryptographic-Hash-Function/Hash-Function
commonkeySize: ['128','512']
specifiedkeySize: '224'TO'512'

The proposal to consider is

shax

SPDX-License-Identifier: CC0-1.0

id: shax
name: SHA-x (SHA-1, SHA-256, etc.)
cryptoClass: Cryptographic-Hash-Function/Hash-Function
commonkeySize: ['128','512']
specifiedkeySize: {min: '224', max: '512'}

[toscalix]

How do we express two different ranges for the same property?

[toscalix]

This PR #26 removes the operator TO by a valid yaml expression to include a range in a property

[toscalix]

This commit fixes the properties list description fb6a53f