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
In the profile resolution spec, the section about custom merges says,
<p>An
<src>insert-controls</src> with an
<src>include-all</src> child results in all included controls being selected and inserted. They are given in the same order as they appeared in the input control selection(s).
</p>
I wasn't sure whether "the input control selection(s)" referred to the order of with-id or similar specifiers in the profile document, the sequence of controls in the imported catalog, or something else. Similarly, I wasn't sure if the order="keep" attribute (using XML syntax here) referred to the order of with-id elements in the profile.
I heard from @david-waltermire-nist that the selection ordering doesn't matter. Can the spec's section about custom merges be clarified on this point? Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the profile resolution spec, the section about custom merges says,
I wasn't sure whether "the input control selection(s)" referred to the order of
with-id
or similar specifiers in the profile document, the sequence of controls in the imported catalog, or something else. Similarly, I wasn't sure if theorder="keep"
attribute (using XML syntax here) referred to the order ofwith-id
elements in the profile.I heard from @david-waltermire-nist that the selection ordering doesn't matter. Can the spec's section about custom merges be clarified on this point? Thank you!
Beta Was this translation helpful? Give feedback.
All reactions