You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
Shouldn't there be a specification version be included in the corim-map so that parsers written to a particular version of the spec can differentiate from RIMs that are compliant with a different specification version?
The text was updated successfully, but these errors were encountered:
Could be addressed using mime types? But could be stripped off if using a conveyance payload. Version encoded inside is safer. Would likely make sense at the comid level and corim level. Coswid doesn't have specification version. New trend is to not specify versions. Allow evolutionary change and support backwards compatibility. Profile can declare which semantics to apply. Profile can encode a version. Having an option version in two places is OK.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Shouldn't there be a specification version be included in the corim-map so that parsers written to a particular version of the spec can differentiate from RIMs that are compliant with a different specification version?
The text was updated successfully, but these errors were encountered: