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

[PROPOSAL] Generic namespace for describing OCI images and layers #36

Open
prabhu opened this issue Dec 2, 2022 · 2 comments
Open

[PROPOSAL] Generic namespace for describing OCI images and layers #36

prabhu opened this issue Dec 2, 2022 · 2 comments
Labels
help wanted Extra attention is needed idea

Comments

@prabhu
Copy link

prabhu commented Dec 2, 2022

Information about the images and their layers via properties is useful while generating SBoM for oci images. Trivy uses the following names.

  • aquasecurity:trivy:LayerDigest
  • aquasecurity:trivy:LayerDiffID
  • aquasecurity:trivy:ImageID

Syft uses the following

  • syft:location:0:layerID
  • syft:location:1:layerID

Instead of requesting another one for cdxgen and other orgs, could we come up with something generic using "org.opencontainers" etc? Example:

  • org.opencontainers.image.layer.digest
  • org.opencontainers.image.layer.id
  • org.opencontainers.image.id
@jkowalleck jkowalleck changed the title Generic top level taxonomy to describe some oci images and layers [PROPOSAL] Generic namespace for describing OCI images and layers Jun 7, 2023
@jkowalleck jkowalleck added the idea label Jun 7, 2023
@jkowalleck
Copy link
Member

like the idea in general, but...
my thoughts:

  • who would own this OCI-related namespace, then? Is there any org or a general committee? did you get in touch with opencontainers(Open Container Initiative), maybe they have such a thing already?
  • where is the taxonomy for this namespace? just having it registered/reserved and having no FFA taxonomy, that serves no purpose. So as long as there is no peer-reviewed and general agreed taxonomy details, I'd veto this proposal.
  • I am concerned that this would create a non-standard nobody would use, so there should be consensus about the details of this taxonomy, first.

@jkowalleck
Copy link
Member

@stevespringett suggested:

one possibility is to put this under the cdx namespace in the same way we support maven, go, and npm today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed idea
Projects
None yet
Development

No branches or pull requests

2 participants