Altova Mailing List Archives

Re: handling namespaces in advance Re: [xsl] namespace required in transform

From: "James Fuller" <james.fuller@---------->
Date: 7/21/2002 4:21:00 AM
----- Original Message -----
From: "Michael Kay" <michael.h.kay@xxxxxxxxxxxx

> I don't think it's ever likely that XSLT or XPath will be extended to
> handle XML that isn't namespace-well-formed. Even the raw XML 1.0 spec
> warns people not to use colons that way.

Hello Mike,

I think your statement might be de-emphasising my main point, yes it is true
that people misuse colons, and thats a side matter, and I agree that
xslt/xpath or whatver will never be extended to handle anything other then
well formed xml. The rest of the question is directed at the xslt list as a

I don't see why the actual syntatic construction of xml could not itself be
abstracted( instead of angle brackets, why not slashes...etc ) and defined,
a sorta schema for base/physical format; maybe this is a route of
introducing binary xml....ok yes there are issues all over the place, just a

back to my original meaderings;

The issue I have is one of performance in a streaming environment, imagine a
multi node SOAP server process, There may be at any one time, a few servers
talking to each other in the form of generating a HTTP request with xml body
or a HTTP response. Another analogous situation would be very long SAX

one could introduce possibly <test:test></test:test xmlns:test="urn:test">
at the end of processing...., could force the processing model to wait until
all data is gathered, just another thought.

In any event I dont see any harm in wanting to handling unknown namespaces,
why for instance does an 'error' have to throw if a namespace is unknown,
why not assign a temporary unique id and handle it, effectively giving us
the hook to handle it.

cheers, jim fuller

 XSL-List info and archive:


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 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.