Checking if the profile-resolution files provided take into account the merge/custom function

[fmasson-oracle]

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.4

I 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.

[david-waltermire]

@fmasson-oracle Can you provide a small profile example that reproduces this bug?

[fmasson-oracle]

Here is what will get resolved, but still results in getting the controls in the sequence they appear in the imported catalog:

And this is the the code that gives me the error when I run the resolver transformation:

[david-waltermire]

@wendellpiez Can you look into this once you are done with the documentation. converter, and schema generation work?

[wendellpiez]

This needs to be accounted for in current unit testing see #1076 and #1087.

@fmasson-oracle sorry for delay (I am finding this picking up the resolver code). A possible mitigation occurred to me - would putting an id attribute (flag) on your group help?

In any case the usual cautions apply (ensure inputs are valid etc) and please feel free to raise again if this remains a problem.

todo: Build tests both with and without (optional?) ID on new groups in custom. Report a useful error when it is missing.