- From: David Carlisle <davidc@nag.co.uk>
- Date: Mon, 21 Jan 2002 09:40:47 GMT
- To: distobj@acm.org, xsl-editors@w3.org
> Using the rules defined for the XHTML media type[1], this document is > an XHTML document because the root namespace is the XHTML namespace. > If delivered as either application/xml or text/xml, it might > reasonably > be expected (see RFC 3023, Section 3, last paragraph) to process it as > XHTML, not as XSLT. I think that should include, in this case, processing <xsl:value-of . The modularisation of XHTML can only succeed if an agent which is processing the XHTML is prepared to hand over control for elements from another namespace. If a document with top level element being xhtml's html contans svg elements in the svg namespace and mathml elements in the mathml namepace then these will (probably) have to be processed (via some mechanism) by some other process and the resulting rendering passed back to the html agent for incorporation in the complete document. I don't see that handling xsl instructions is radically different from this. Of course if the agent receiving the document can't handle xsl then tough, but the same is true of sending an xhtml+mathml document to a non mathml-enabled browser. David [Note that I'm not on the working group, this is just a comment from someone subscribed to the comment address, not a response from the WG] _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service.
Received on Monday, 21 January 2002 04:41:10 UTC