Features for ContainerRecipe

[vsoch]

A Container Recipe (Dockerfile, Singularity recipe, or similar build file) is described within each technology (but afaik not for OCI?) and we would want to discuss what attributes are important to have in the specification. @roscopecoltran is starting discussion of the extractor here

https://github.com/vsoch/dockerfiles/issues/4#issuecomment-423069695

And so far it's clear that we need brands and keywords, and I suspect some attributes of the recipe itself (higher level). Here is a list to get us started:

• commands
  • ContainerImage (e.g., Docker, Singularity)
  • entrypoint or runscript
  • command
  • labels
  • help section
  • keywords
  • brands (should brand be a type of keyword?) And then we would have different types of keywords? Cool super excited to get started on this! An update from me is that I'm still working on infrastructure for the specification that will describe the dataest - it will render nicely to here --> https://openschemas.github.io/

See links in the linked issue for different software to try, and I suggested using datalad as a mechanism to extract and put into schema.org spec.

[vsoch]

Once the specification gets feedback, we can create validation criteria (run during the extraction) almost verbatim based on OCI! The required / type sets are very clearly stated --> https://github.com/opencontainers/image-spec/blob/master/spec.md