• From: Frank Richards <frichards@s...>
• To: jwells123 <jwells123@e...>, xml-dev@l...
• Date: Thu, 23 Aug 2001 10:06:50 -0400

Umm, at the risk of appearing antedeluvian, xml is also used for [gasp]
documents...
if you are indeed pulling information out of an RDBMS, then you can bury the
slicing,
dicing and rearrangement in the SQL.

If you are putting online help into a bound users manual, or reprinting
journal articles
in a book, well, you can use XML (sgml), or you can key it again. (Or,
because humans are much
smarter that computers, you can send it out looking like junk.)

Frank

-----Original Message-----
From: jwells123 [mailto:jwells123@e...]
Sent: Tuesday, August 21, 2001 11:14 AM
To: xml-dev@l...
Subject: Re: Separating content from presentation


True, but server-side script has had this capability for years. I've seen
case studies on MSDN where a database-driven site was rewritten using SQL
2000 and XSLT, but I haven't seen any compelling reason for scripters to
switch to XSLT.

• References:
  • Re: Separating content from presentation
    • From: jwells123 <jwells123@e...>

• Prev by Date: Re: Namespaces,W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
• Next by Date: Re: "Uh, what do I need this for" (was RE: XML.COM: How I LearnedtoLove daBomb)
• Previous by thread: Re: Separating content from presentation
• Next by thread: Re: Separating content from presentation
• Index(es):
  • Date
  • Thread