Interop and c14n(x) != c14n(c14n(x))

> Yes, *and* when you do copy all the xml:* from the ancestors because of a
> missing parent element you go *all* the way up to the root, not just up
> to  the next ancestor element in the subset. Counter-intuitive but the
> spec is  clear once you get over your intuitions -- I had the same
> problem! [1]

First, here is my example on c14n and exclC14n. Maybe others can validate? 
Thanks. (secret key for hmac is six octets of "secret").


This weird behaviour of c14n of document subsets leads to a very strange 
result. Till today, my understanding of c14n was that given some input 'X', 
the c14n algorithm can be applied multiple times without changing the 
result. But now, I see that

1.) Given a document subset 'X' with a form that the above rule comes to 
play.

2.) Then we see that

        c14n(X) != c14n(c14n(x))

I included a sample for this (the last three references) in the interop.



Regards,
Christian