- From: Geoff Deering <gdeering@acslink.net.au>
- Date: Sat, 11 Oct 2003 13:39:51 +1000
- To: "Charles McCathieNevile" <charles@sidar.org>, "David Woolley" <david@djwhome.demon.co.uk>
- Cc: <w3c-wai-ig@w3.org>
That's one of the main points in storing data in XML in a CMS. Through designing appropriate XSLT the CMS can deliver content to different media; browsers, PDF, mobile devices, slide presentations, etc. This is also the Cost/Benefit and ROI on this type of approach. So you are not just publishing to the web, it's aimed at providing content to all media, as well as providing the content in a semantic form that can be understood by other computing processes. This approach can also be taken using HTML and CSS designing an appropriate CSS for each media type, but the XML/XSLT approach offers more options and flexibility. Geoff -----Original Message----- From: Charles McCathieNevile The average CMS is essentially an environment for authoring a particular kind of content, and the ones I have seen have the benefit of being able to handle non-HTML content reasonably well, and the drawback of not being very good for HTML unless you like writing code. This is not true of them all, of course - some of them do HTML very well. Just my 2cents worth Cheers Chaals
Received on Friday, 10 October 2003 23:41:07 UTC