Unique Product Identifier

[santosomar]

Originally, posted in the initial OpenEoX public repository:

OpenEoX/openeox#22

Defining the productId

The productId should ideally be globally unique to ensure consistency and avoid confusion across different documents or systems. The assignment of productIds can be managed by a central authority, similar to the supplierID, or follow a standardized naming convention established by the industry. By ensuring a globally unique productId, it becomes easier to track and manage EOL and EOS information for products across various sources and platforms. Getting consensus of this central authority will be one of the most challenging parts of all this. However, we can start the conversation with other industry leaders, CISA, and other participants.

[tschmidtb51]

IMHO, the solution of the Unique Product Identifier issue is out-of-scope. There are some ideas around, like the ones presented at FIRSTcon 2023

[kvandecr]

a URL (or hash thereof) could already fill some requirements, given the requirement that the vendor in question keeps their urls static. this is hard to guarantee given name changes, acquisitions, etc ...