 |
|
|
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@g...> 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/
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
