-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Comments
@coderpatros How do you want to handle urns? IMO, the urn should be optional as to provide backward compatibility, but should be recommended. Thoughts? |
I think we should reserve the usage of the "urn" namespace for URNs. I can update the ABNF to support both. |
@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 |
On behalf of IBM, I kindly request to reserve the namespace 'ibm' for use in IBM produced public SBOMs.
Namespace to be reserved
ibm
name
field valuesurn: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:component
propertiescomponent
propertiescomponent
propertiesmetadata
properties for customersGoal: Simplification
Reduction in length of property name value:
would be simplified to:
Note It is my hope we support URN syntax as well (and update the ABNF for package names correspondingly). See issue: #9
The text was updated successfully, but these errors were encountered: