Profile resolver: Interaction between inclusion/exclusion and mapping

[galtm]

Related to the profile resolver spec's Mapping Controls section, I'd like to know how the inclusion/exclusion process interacts with the mapping process. Is mapping done strictly after inclusion/exclusion?

For instance, would a control with ID ac-1 be included and then mapped to ID ac-2, or would it be mapped to ID ac-2 first and thus excluded? Would a control with ID xyz be omitted, or would it be mapped to ID ac-3 and thus included?

    - include-controls:
       - matching:
          - pattern: "ac*" 
    - exclude-controls:
       - with-ids:
          - ac-2
      mapping:
       - controls:
          - from: ac-1
            to: ac-2
          - from: xyz
            to: ac-3

[david-waltermire]

In my view, inclusion/selection happens first using the original control identities from the source catalog or resolved profile. Then mapping occurs on the result of this selection.

@stephenbanghart This will need to be made clear in the profile resolution spec.

[stephenbanghart]

Mapping would take place after both inclusion and exclusion. I'll spin this into an issue to add updated language to the specification.

Thanks for the feedback!

[galtm]

Thanks for your answer, @david-waltermire-nist and @stephenbanghart ! It sounds sensible to me.