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
Per usnistgov/OSCAL#1255, the media types are not used in profiles and other example content with a vendored type format are not conformant with OSCAL guidance or the linked IANA specification strongly recommended for OSCAL usage. application/oscal.modelname+dataformat is invalid, while application/oscal+dataformat is acceptable.
/cc @volpet2014 and @Rene2mt, as this came up in model updates meeting (tracked in usnistgov/OSCAL#1066) and I took an action item to relay it back to FedRAMP, potentially assisting them with correcting this minor bug.
Describe the bug
Per usnistgov/OSCAL#1255, the media types are not used in profiles and other example content with a vendored type format are not conformant with OSCAL guidance or the linked IANA specification strongly recommended for OSCAL usage.
application/oscal.modelname+dataformat
is invalid, whileapplication/oscal+dataformat
is acceptable.Who is the bug affecting?
OSCAL tool developers
What version of OSCAL are you using? (Check our info on supported OSCAL versions)
v1.0.0
tov1.0.4
inclusiveWhat is affected by this bug?
Processing of OSCAL content with
back-matter
resource
s that havemedia-type
s defined for theirlink
s.When does this occur?
Consistently.
How do we replicate the issue?
media-type
usage in current FedRAMPprofile
s and how they definemedia-type
s, such as this link or another linkExpected behavior (i.e. solution)
These are modified to be
application/oscal+json
andapplication/oscal+yaml
respectively.Other Comments
N/A
The text was updated successfully, but these errors were encountered: