Automatic transformation of XML namespaces/History
completeness, stability, preference
editIt was a wrong idea to use three numbers: completeness, stability, preference and sum their products to determine transformation path for the following reason:
Consider transformation like HTML -> plain text -> HTML (stripping tags). This transformation may win even if it has low priority, having a long chain of other (better) transformations as a competitor.
So we should use only "quality: 0.0..0.1" instead of the three and not sum them, but rather get the minimum of all qualities in the chain.
Hm, we can use old "triple" values to choose between several paths with equal quality.
Proposed solution: take among the path with maximum preference the path of maximum product of preferences. (Are the first "preference" and the second one the same parameter?)