Hmm, I don't quite understand how could I calculate the numeric matching distances between the matchedValue and the attribute values if I don't convert them both into numeric values (or use a custom Comparator which does this internally).

I could certainly get the attribute binding class form FeatureTypeInto, but I would still have to calculate the distance differently for Dates, Numbers and Strings, right?