- From: Chris Lilley <chris@w3.org>
- Date: Mon, 22 Nov 2004 13:39:29 +0100
- To: David Carlisle <davidc@nag.co.uk>
- Cc: www-tag@w3.org
On Monday, November 22, 2004, 1:23:05 PM, David wrote: DC> That said, what the browsers actually do with #foo in the case of DC> arbitrary XML served as application/xml styled with XSL via the DC> xml-stylesheet pi is interpret the fragid in the (x)html that is DC> generated internally by the stylseet, not as an identifier in the XML DC> that is actually served. So even here (if one wanted to standardise DC> currently implemented behaviour) a pure XML xpointer based fragid syntax DC> wouldn't really help... That is a very good point, which I isolated to comment on so it doesn't get lost. Its one instance of a processing pipeline; the content as served has one media type, but then processing (xslt, xinclude, whatever) happens to it so that the displayed resource is of another media type. There are known problems where the type of the derived resource is assumed by the client (eg in WinIE, where anything created by XSLT is assumed to be text/html) but equally, its not clear how to declare the type of the derived resource. Not how to address it - link into it, etc. Is it a resource, since it does not have a URI? Is it perhaps a secondary resource? This has knock-on effects on various TAG findings. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Monday, 22 November 2004 12:39:35 UTC