[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Separating content from presentation
- From: "Bullard, Claude L (Len)" <clbullar@ingr.com>
- To: "Al B. Snell" <alaric@alaric-snell.com>
- Date: Thu, 23 Aug 2001 10:36:54 -0500
Umm.. gotta be picky. XML like SGML isn't
*designed* to do that. One does that because
as you say, it's good practice. I am
picky about it because otherwise, XHTML
wouldn't exactly make sense. Application
languages are what XML and SGML are
designed for designing. People don't
get that sometimes and we get all the
religious nonsense.
There are problems of confusing abstraction
for the sake of describing ever larger
variations of applications and the simple
technique of lossy downtranslation for
the sake of presentation. If one isn't
careful, the More Meta Than Thou creep
takes over and the abstractions result
in ThingThatDoesNothing. Too narrow
and it is the ThingThatDoesEverythingBadly.
Len
http://www.mp3.com/LenBullard
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
-----Original Message-----
From: Al B. Snell [mailto:alaric@alaric-snell.com]
Yep, but people have been doing this for ages, and XML doesn't help or
hinder this at all. XML as a way of seperating content and presentation
started because it was designed to split Web pages into content and
presentation, it's nothing to do with having content generating code
seperating from presentation code - that's just good programming practice,
XML or no XML.