Checking if the profile-resolution files provided take into account the merge/custom function #897
Labels
Aged
A label for issues older than 2023-01-01
question
Scope: Tooling and APIs
Issues targeted at development of tooling and APIs to support OSCAL content creation and use.
I am checking if the resolver-pipeline transformation scenarios provided with OSCAL1.0.0 RC2 release should work with the sample code provided on the https://pages.nist.gov/OSCAL/documentation/processing/profile-resolution/ page where you describe how controls could be restructured using the Merge/Custom element?
The resolver-pipeline transformation does not work as I get this error while doing the transformation: An empty sequence is not allowed as the first argument of opr:catalog-identifier()
This happens if I use this structure:
s1.1.3 s1.1.1 s1.1.4I don't get the error if I don't use , but the new structure is not taken into account in the resolved-profile. I only get the controls in the order they appear from the imported catalog.
The text was updated successfully, but these errors were encountered: