Re: xhtml compatibility guideline

Hi Mark,

At 12:14 PM 12/22/2002 -0800, you wrote:
> In this case, I think (hope) it's
> not too much more work to actually do the
> right thing.  This seems to be:
>
>     - If the browser sends an accept header that allows
> XHTML, write the
>       DOM as XML (with approriate mime
> type).
>     - If the browser doesn't explictly allow an XHTML
> response, 
>       write the DOM as HTML (with approriate
> mime type).
>
> this could actually work independently of the original document
> format;
> a document that started out as HTML can be written as XHTML.
>
> Of course, all of this is just me typing e-mail, there are probably
> some
> other underlying issue that might make it a bit harder.

This sounds excellent!  I was thinking actual browser detection, but
just looking at the headers for allowing xhtml support is the idea way to
go. That's how things were always *supposed* to work.  And the fact
that XMLC could output whatever type of document that the browser states
that it supports, even one that is different than the original document
template, is just one more reason why XMLC is the best presentation
technology out there.  Hopefully it isn't much harder to implement
than you described.

Happy Holidays!

Jake