mWdsb2JhbACCIy6ObgEBAQEBCAUGCREFmgeEVA
X-IronPort-AV: E=Sophos;i="4.31,314,1215352800";
d="scan'208";a="16159436"
by
antispam.ballarat.edu.au with ESMTP; 06 Aug 2008 19:20:43 +1000
by
ms01.oasis-open.org with esmtp id 1KQfC7-00021N-TC
for
j.avery@ballarat.edu.au; Wed, 06 Aug 2008 05:20:36 -0400
Received: (qmail 5907 invoked by uid 60909); 6 Aug 2008 09:20:24 -0000
Delivered-To: mailing list
xml-dev@lists.xml.org
Received: (qmail 5899 invoked by uid 0); 6 Aug 2008 09:20:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=
gmail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:cc:in-reply-to:mime-version:content-type:references;
bh=RnZkMpfxFKOH/84TEMjGZxO023im2+HIU3og5vC/7f8=;
b=KRIkX7MS6uLIm+2CY12eV+84HPYP0kMIPmETZ6oKbAGiIs2d/9TGdGS0BdCz2hK8dO
c/omyUoe5c7W+N39OlAzFYcB5rgLxNk7rjVy/Ltv/IcY4+RQOmgwDjLsvgdsNz3UD4M0
rqX4sK0iXm3WWyFnZF1pqr2F6NHEJCwrC0+dQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=
gmail.com; s=gamma;
h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
:content-type:references;
b=P/F8BQthfv/EqsRzjPP5W7z9F+Yw5bbfZBWlV3Js/4/FTlrHRqoSMnyGZQ7+iQ2SXV
Uke9uqtZ1gvOOQ4VuFmLVnwxzAL+SQTUpbwg01AmsLd5HqtlWipfHh6qLFHs2WJKZNvR
G6mnaEelx67J4WGISs6kFRCo4hFPCXqX8Syxo=
Message-ID: <
b1c8e2c80808060220v70e7dc62v3976e29e85a63008@mail.gmail.com">
b1c8e2c80808060220v70e7dc62v3976e29e85a63008@mail.gmail.com>
Date: Wed, 6 Aug 2008 14:50:21 +0530
To: "Andrew Welch" <
andrew.j.welch@gmail.com>
Cc:
xml-dev@lists.xml.org
In-Reply-To: <
74a894af0808060200h2024b63ei32ad8a14785fd5ad@mail.gmail.com">
74a894af0808060200h2024b63ei32ad8a14785fd5ad@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_1762_2080986.1218014421667"
<
74a894af0808060200h2024b63ei32ad8a14785fd5ad@mail.gmail.com">
74a894af0808060200h2024b63ei32ad8a14785fd5ad@mail.gmail.com>
X-Antivirus-Scanner: ClamAV at OASIS detected no problems
X-Spam-Score: -2.5
X-Spam-Level: --
Subject: Re: [xml-dev] XML Transformation
------=_Part_1762_2080986.1218014421667
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
- Show quoted text -
According to the xml specification though
http://www.w3.org/TR/REC-xml-names/#scoping-defaulting the inner scope
definition overrides the parent one if the NSAttName is the same. In our
case of the xml above it is the same as its the default namespace. So i dont
see why the inner scope namespace declaration element be removed and use the
parent namespace.
Anishek
On Wed, Aug 6, 2008 at 2:30 PM, Andrew Welch <
andrew.j.welch@gmail.com>wrote:
> > For better or worse, the digital signature mechanisms follow XML
> > Canonicalization by deciding that namespace prefixes are significant: see
> >
> >
http://www.w3.org/TR/xml-c14n#NoNSPrefixRewriting
> >
> > for discussion.
>
> ! That's good to know...
>
> I guess it all comes down the fact that the prefix isn't expanded to
> the URI.... which is the root cause of the problem of XPath requiring
> the prefixes to be mapped elsewhere.
>
> I guess there is an argument for dropping the URI altogether, and just
> using the prefix. Some things would get harder, but many more would
> get a lot easier.
>
>
> --
> Andrew Welch
>
http://andrewjwelch.com
> Kernow:
http://kernowforsaxon.sf.net/
>
------=_Part_1762_2080986.1218014421667
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<div dir="ltr">According to the xml specification though
<a href=""
http://www.w3.org/TR/REC-xml-names/#scoping-defaulting">http://www.w3.org/TR/REC-xml-names/#scoping-defaulting</a> the inner scope
definition overrides the parent one if the <a id="scoping"
name="scoping">NSAttName is the same. In our case of the xml above
it is the same as its the default namespace. So i dont see why the
inner scope namespace declaration element be removed</a><a
id="scoping" name="scoping"></a> and use the parent namespace.
<br>
<br>
<br>Anishek<br><br><div class="gmail_quote">On
Wed, Aug 6, 2008 at 2:30 PM, Andrew Welch <span
dir="ltr"><<a href=""mailto:andrew.j.welch@gmail.com">andrew.j.welch@gmail.com</a>></span>
wrote:<br><blockquote class="gmail_quote" style="border-left:
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<div class="Ih2E3d">> For better or worse, the digital signature mechanisms follow XML<br>
> Canonicalization by deciding that namespace prefixes are significant: see<br>
><br>
> <a href=""http://www.w3.org/TR/xml-c14n#NoNSPrefixRewriting" target="_blank">http://www.w3.org/TR/xml-c14n#NoNSPrefixRewriting</a><br>
><br>
> for discussion.<br>
<br>
</div>! That's good to know...<br>
<br>
I guess it all comes down the fact that the prefix isn't expanded to<br>
the URI.... which is the root cause of the problem of XPath requiring<br>
the prefixes to be mapped elsewhere.<br>
<br>
I guess there is an argument for dropping the URI altogether, and just<br>
using the prefix. Some things would get harder, but many more would<br>
get a lot easier.<br>
<font color="#888888"><br>
<br>
--<br>
Andrew Welch<br>
<a href=""http://andrewjwelch.com" target="_blank">http://andrewjwelch.com</a><br>
Kernow: <a href=""http://kernowforsaxon.sf.net/" target="_blank">http://kernowforsaxon.sf.net/</a><br>
</font></blockquote></div><br></div>
------=_Part_1762_2080986.1218014421667--
