"Simon St.Laurent" wrote:
> 
> I think what Paul is proposing is something of a halfway-house, so that
> users can have some idea of what their content will end up looking like,
> but still use the power available in transformations.  It's a difficult
> proposal to make work, but I think it'd be worth considering for a large
> number of project types.

Note that I don't intend to propose anything radical here. SGML Editors
have had quasi-WYSIWYG stylesheets since there SGML editors. The only new
thing is that they could be standardized.

I know at least one XML editor is already using CSS -- but CSS with
extensions. I also know that that editor doesn't do everything that we
typically expect from structured markup editors -- in particular cross
references are a weak spot. Beyond generally useful CSS extensions (such
as cross references) there are some needs that are unique to XML editors.
For instance, most have a concept of a "default template" that is inserted
when an element is inserted. Most also have a way of triggering events
when elements are inserted. And so forth...

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco

"The Excursion [Sport Utility Vehicle] is so large that it will come
equipped with adjustable pedals to fit smaller drivers and sensor 
devices that warn the driver when he or she is about to back into a
Toyota or some other object." -- Dallas Morning News


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list