- From: Paul Prescod <paul@prescod.net>
- Date: Wed, 23 Jan 2002 14:17:44 -0800
- To: "Simon St.Laurent" <simonstl@simonstl.com>
- CC: www-tag@w3.org
Consider a namespace like XSLT or maybe SOAP. They treat the other namespaces as XML elements and attributes. You could almost say "lexically". They don't try to understand it. Now if I'm sending HTML in one of these containers, does it matter what the namespace of the inner stuff is? Would you really want: Content-Type: multipart/mixed(text/html, image/jpeg) Probably not? Consider a namespace like XHTML. Maybe it has embedded SVG. Why do you care? Okay, you can't render it if you don't have an SVG plug-in. So what? You can't render it if it has <IMG SRC="something.sfg> either. Is there an example of an application that really needs to know about multiple namespaces before it reads the document? Paul Prescod
Received on Wednesday, 23 January 2002 17:19:16 UTC