Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Hardware IDs #453

Open
prabhu opened this issue Apr 26, 2024 · 3 comments
Open

Support for Hardware IDs #453

prabhu opened this issue Apr 26, 2024 · 3 comments

Comments

@prabhu
Copy link
Contributor

prabhu commented Apr 26, 2024

Currently, there are no PURL equivalents for Hardware. The closest I could find were:

The proposal is to add hwid as an array attribute under component and let the user populate the same with array of strings.

@stevespringett
Copy link
Member

@prabhu
Copy link
Contributor Author

prabhu commented Apr 29, 2024

@stevespringett are you proposing to use properties instead of a top-level id? It might be alright

@stevespringett
Copy link
Member

There are many types of identifiers used in hardware devices. CycloneDX properties capture many of the common ones, but there are many industry-specific formats. For example UDI is required for medical devices in the U.S, but there are some challenges in terms of variants of the spec.

https://www.greenlight.guru/blog/udi-unique-device-identifiers-fda
https://www.greenlight.guru/blog/udi-101

I think in order to support hardware identifiers natively, we would need to a simple way to add initial support identifiers used in the most common industries along with the existing support for general identifiers in the property taxonomy, but also allow future identifers to easily be added, My initial thought on this is to use enumerations.

"components": [
  {
    "type": "device",
    "name": "my device",
    "hardwareProperties": {
      "identities": [
        { "type": "serialNumber", "value": "123456", "encoding": "TBD" },
        { "type": "gtin-14", "value": "12345678901234", "encoding": "TBD" }
      ]
    }
  }
]

Note, some hardware identifier schemes have optional or required encoding methods that should likely also be captured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants