Many thanks. Does the cascading down HAVE to happen ? Or can it be avoided ?
If it cannot be avoided, is there a way to "uncascade" it after signing, or at verification time ?
Unfortunately, the code from "the code below" was missing in your mail. Could you send it to me ?
Many thanks in advance.
Jozef
Jozef Aerts Computer Chemistry Consultancy Singen, Germany
From: Berin Lautenbach <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: going from signing xml file with DTD to signing xml file with Schema
Date: Sat, 21 Feb 2004 13:24:21 +1100
Jozef Aerts - Comp.Chem.Cons. - XML4Pharma wrote:
My application signs the file (enveloped, full document is signed), but in the signed document every element now gets an extra namespace reference, e.g. <Study OID="123-456-789"> is transformed into: <Study OID="123-456-789" xmlns="http://www.cdisc.org/ns/odm/v1.2"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
The library cascades *all* namespaces down the document prior to canonicalisation, so that they are all visible to the canonicalisation algorithm. So this sounds correct.
Also when veryfying the signed document, the signature is found to be invalid (due to the extra namespace references?).
That doesn't sound correct! Are you verifying a document produced with the code below, or an old document that's had the schema attributes added?
Cheers, Berin
_________________________________________________________________ MSN Search, for accurate results! http://search.msn.nl
