RE: DSig comments on XML Base

I have no access to the XML processor.  My library receives DOM Document
and Element objects when creating the signature.  When verifying the
Signature a deligate to the user to find and parse the URI.  I'm not
sure I totally understand the discussion that had taken place, but
I would say that I have no way of distinguishing which parts of
the source came from external entities, and forcing the user to
structure the DOM subtree that I am signing in a particular way is
a big no no.  Currently, the only thing that my library requires
is that the user hand me a DOM Document or Element that has been
parsed with a validating parser (with ignorable whitespace not


-----Original Message-----
From: John Boyer []
Sent: Thursday, July 27, 2000 1:59 PM
To: Jonathan Marsh;
Subject: RE: DSig comments on XML Base

Hi Jonathan,

OK, that makes some sense.  What you're saying is that we should have
extend the Xpath data model by adding an xml:base to the top level
of external entities.

This must be done by modifying the XML processor that generates the
node-set.  I wonder how easy this is for implementers.

I agree with you that trying to read between the lines on XML 1.0 is a
of time, but I disagree with the implication that this is what I'm
There are quite specific lines that tell an XML processor developer that
they need not distinguish between content derived within the document
content derived externally.

So, TAMURA Kent, Kevin Regan and others: could you please let us know if
can do this?  If so, then I'd like to do what you suggest Jonathan, then
place a note about the residual problem with base URI for top-level PIs.

John Boyer
Development Team Leader,
Distributed Processing and XML
PureEdge Solutions Inc.
Creating Binding E-Commerce
v: 250-479-8334, ext. 143  f: 250-479-3772
1-888-517-2675 <>

Received on Thursday, 27 July 2000 17:39:29 UTC