Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Include Elements from other namespace in own XML

From: Joseph Kesselman <keshlam-nospam@-------.--->
To: NULL
Date: 7/6/2007 6:47:00 PM

Benjamin Kalytta wrote:
> However the application (browser) don't know what to do 
> with <html:a> for example.

If you're going to use outdated applications... I'd suggest that rather 
than prefixes, you try using the default-namespace convention. That is, 
instead of <html:a>, use <a xmlns="http://www.w3.org/1999/xhtml/">.

If the application is really namespace-unaware, that should look like an 
HTML element to it.

Note that since namespace declarations are inherited, you won't 
necessarily have to re-bind xmlns on every element. A smart serializer 
should do the Right Things in that regard.


However, my position is that outdated applications should be discarded 
in favor of ones that support new standards -- so I'd recommend that you 
solve this instead by making the whole document either HTML or XHTML 
rather than mixing the two, and then use a browser (or other tool) that 
understands the language you're actually working in.

-- 
Joe Kesselman / Beware the fury of a patient man. -- John Dryden


transparent
Print
Mail
Like It
Disclaimer
.

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.

.
.

transparent

transparent