Lapse in Profile Resolution spec? - including all referenced parameters

[wendellpiez]

A minor but significant lapse in the Profile Resolution specification I think, or at any rate a point for clarification/discussion.

In brief, consider the following outline:

catalog:
  Control A
    param A1
    text incl ref to A1
  Control B
    text incl ref to A1

profile (selects B alone)

I would expect as output:

catalog:
  param A1
  Control B
    text incl ref to A1

That is, B is complete, with its reference, and the target of its reference. However parameter A1 is now 'loose' (not enclosed in control A) since control A is not included.

Describe the bug

If this is intended, we need clarification. If not, discussion. Currently the spec is silent afaict.

This lapse has spinoffs, as well. For example, if a catalog is modified to include a reference to a parameter outside the ancestor hierarchy of the patch (placement), the same thing can happen - a parameter may need to be copied implicitly.

[david-waltermire]

This raises the greater question around what is a parameter's scope? One could argue that a parameter is scoped to it's current context (catalog, group, control) and any children of this context.