RE: Re: DHTML browsers [was Accessibility]

On Mon, 13 Sep 2004 16:20:32 -0500, Austin, Darrel wrote
> 
> The more 
> I work with XML (I'm pretty much a newbie to all of that) the more I 
> see the disadvantage of storing content using the limited palet of 
> HTML tags for structure.

I think content should always be stored as XML in the CMS and all published
sites.  The application server can render and cache XML content as HTML for
delivery to the browser.  There may be exceptions for legacy content or such a
huge volume that the only decently-performing solution requires pre-rendering
in this format.  There are many factors leading me to this conclusion but I am
interested in any arguments against such an architecture.

As it merges content with presentation, WYSIWYG seems to break down even when
content is stored as XHTML with CSS references.  Users do seem to have valid
needs for tabular data, and a worse case is where the WYSIWYG allows unmanaged
links in the content, but again I don't see any real way to avoid these
problems (suggestions gladly accepted).

I will look into the concepts of semantic markup at XStandard, but if they
can't give a release date for the non-ActiveX version it won't be an option.

Thanks again,

   -John