As long as no one insists that it is the "intent" of XML
to separate presentation and content, that's a pertinent 
topic.  It's just a smart thing to use XML to do.  

My problem with pipelines, particularly ones that use transformation, 
is that someone has to sit down and solve the "gossip chain" 
problem.  That is, small semantic errors that creep into 
the maps.  As much as we may say XML is devoid of intent, 
a chained process isn't.   That is why so much is made of 
strong semantic types; send this; return that.  Know a priori 
what this and that are.   Functional, yes, but entirely 
practical.

len

-----Original Message-----
From: W. E. Perry [mailto:wperry@[...].com]

Since we're touting Extreme Markup (with good reason; it's an excellent
conference), I too will be speaking on (gasp!--sorry, Len) "Separate
Presentation From Content:  But How To Distinguish Them?" 

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>