XML to XHTML via XSLT

[Sannyasin Sivakatirswami]

Mark, you certainly hit the mark... we *do* need the XML on the input 
side for the very reason you describe. My Rev app interface allows 
non-tech types to input data and the app outputs the data in perfectly 
formed XML... i.e. forcing it into an XML structure means no bad input 
on the front end. (I can also pull this into InDesign with paragraph 
styles which is an added bonus)

But, the more I think about using XSLT, the less I think we need it.  
I'll just use Rev XML functions to parse the content and write an 
xtTalk script to build the web pages... I've been doing this latter bit 
for 10 years, so I don't see any reason to jump through XSLT hoops...

are the XML libraries bundled with the engine these days? i.e. can we 
talk to Rev XML libraries on a faceless server engine installed app 
with CGI?

Sannyasin Sivakatirswami
Himalayan Academy Publications
at Kauai's Hindu Monastery
katir at hindu.org

www.HimalayanAcademy.com,
www.HinduismToday.com
www.Gurudeva.org
www.Hindu.org

On Apr 16, 2004, at 8:32 PM, Mark Brownell wrote:

> This is done so that static web pages can be written by non-tech-types 
> that can be transformed into their company's HTML pages and that 
> include CGI & server side database information. So the content person 
> writes in an editor that outputs XML data based on its DTD validation. 
> The company uses this validated format system to update their website 
> faster and with less technical advice from the tech side. In a way it 
> gives tech-power to the creative side of website providers team.