-
Notifications
You must be signed in to change notification settings - Fork 41
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
The media type used doesn't meet the OCI artifact spec #100
Comments
The organization that owns CNAB-to-OCI is the CNAB Foundation, which is an official foundation from JDF. (For those keeping track... LF has both CNCF and JDF under it, and CNAB Foundation is under JDF, but CNAB itself is not under CNCF.) I suppose we could make it |
The |
I like @technosophos's suggestion. CNAB is the spec/foundation, and bundle is one of the artifacts in the spec (for example another artifact would be a claim). The double cnab would be confusing. 😀 |
Just to clarify something that came up in Slack: CNAB Foundation is the foundation that maintains the CNAB specification. JDF is NOT the foundation that maintains the spec. So |
I'm +1 to @technosophos's proposal |
The media type of CNAB config artifact is
application/vnd.cnab.config.v1+json
which doesn't meet the OCI artifact spec standard for the unique type:application/vnd.[org|company].[objectType].[optionalSubType].config.[version]+json
How about add a
cncf
section:application/vnd.cncf.cnab.config.v1+json
?The text was updated successfully, but these errors were encountered: