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

Request reserved namespace prefix "ibm" #34

Closed
mrutkows opened this issue Oct 28, 2022 · 3 comments
Closed

Request reserved namespace prefix "ibm" #34

mrutkows opened this issue Oct 28, 2022 · 3 comments

Comments

@mrutkows
Copy link

mrutkows commented Oct 28, 2022

On behalf of IBM, I kindly request to reserve the namespace 'ibm' for use in IBM produced public SBOMs.

Namespace to be reserved

Namespace Description URN equivalent
ibm Namespace for use in IBM SBOM's within property name field values urn:ibm:names

Planned usage

Currently, we plan to use this as an alias (short form) for our current URN (i.e., urn:ibm:names) to add/associate domain specific information such as:

  • IBM product and deliverable IDs to component properties
  • additional scan/internal tooling/classification information to component properties
  • risk and confidence scoring information to component properties
  • legal (usage, coverage) disclaimers to metadata properties for customers

Goal: Simplification

Reduction in length of property name value:

{
"name": "urn:ibm:names:identifier:product",
"value": "5737-I23"
} 

would be simplified to:

{
"name": "ibm:identifier:product",
"value": "5737-I23"
} 

Note It is my hope we support URN syntax as well (and update the ABNF for package names correspondingly). See issue: #9

@stevespringett
Copy link
Member

@coderpatros How do you want to handle urns?

IMO, the urn should be optional as to provide backward compatibility, but should be recommended. Thoughts?

stevespringett added a commit that referenced this issue Nov 2, 2022
@coderpatros
Copy link
Member

I think we should reserve the usage of the "urn" namespace for URNs. I can update the ABNF to support both.

@jkowalleck jkowalleck self-assigned this Mar 17, 2023
@jkowalleck
Copy link
Member

@coderpatros no need to update the ABNF, as long as the namespace is reserved, i guess. will open a PR soon.

regarding urn support in ABNF - this would be an own topic, right? see #9

@jkowalleck jkowalleck removed their assignment Mar 18, 2023
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

4 participants