Consider extensible signature standards support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- json
- Domain
- backend-api-design
Research direction
Start with the proposed signatures schema in issue #943 and review the linked discussion from pull request #858. Work out a future-compatible representation for multiple signature standards while preserving the existing JSS approach. Done means the specification has a clear, technically valid design that supports additional signature types.
Written by the indexing model from the issue text.
Description
i am a bit concerned about possible changes in the future.
What if might transition from JSS to something else some day?
the way it is currently structured will block any path for this.
i'd rather go with something like
{
// ...
"signatures": {
"type": "array",
"minItems": 1,
"items": {
"oneOf": [
{
"type": "object",
"description": "description from cyclonedx-jss_X590_2023_10-2.0.schema.json#/$defs/signatureObject",
"properties": {
"type": { "const": "JSS_X590" },
"data": { "$ref": "cyclonedx-jss_X590_2023_10-2.0.schema.json#/$defs/signatureObject" }
},
"required": ["type", "data"],
"unevaluatedProperties": false
},
// any later type of signature we might add in the future
]
}
}
}
Originally posted by @jkowalleck in https://github.com/CycloneDX/specification/pull/858#discussion_r3334967070
While the recommended approach will not "technically" work, the desire to support multiple signature standards remains. Attempt to devise a way this can be supported in the future.
- Dominant language
- XSLT
- Stars
- 551
- Forks
- 93
- Avg merge
- 4h 51m
- Merged PRs (30d)
- 42
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CycloneDX/specification
-
Response vs Responce Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
CycloneDX/specification#1121 ·
-
defect documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CycloneDX/specification#1115 ·
-
cap: cryptography-registry
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CycloneDX/specification#1098 ·
-
defect
Difficulty 1/5 Under an hour Newbie friendliness 91/100
CycloneDX/specification#1045 · 2 comments ·
-
CDX 2.0 documentation ready for review
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CycloneDX/specification#1035 ·
All issues in CycloneDX/specification
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
microsoft/magentic-ui#588 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
alexgorbatchev/simple-ptt#3 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CorrelAid/formtransform#44 ·