Martin,
the canonicalizer cannot know, if the may
contain other elements only, or if mixed content is allowed.
So there is no way to tell the difference between significant
and non significant whitespace.
Else the canonicalization would remove non significant whitespace,
I would guess.
Just my
Peoples,
I have done some work to implement an algorithm mapper for the signature
and digest algorithms in the C++ library. As part of this, I have
implemented new methods that allow callers to create new signatures or
references using URIs rather than the current enumerated type. This is
> But does anyone feel they (the enum based creation calls) should be left
> in-perpetuity? (They won't be removed quickly, but they will eventually
> disappear.)
I'd expect them to be deprecated for one major release (1.3?) and then
potentially dropped afterward.
-- Scott
Hi Heiner,
Thanks for the response.
I've been giving this a little thought as I get up to speed with the whole
xmldsig thing and pretty much reached the same conclusion.
Fortunately my specific application pretty much has control over the xml
creation and modification processes so I will be abl
