i don't know xopus, but i think all editors could be rewritten not to
duplicate aggregations and transformations from the publication - by
delegating it. every editor is free to apply another post-processing
step and tweak the content as it wants (see tiny again: the rendered
page from the publication sitemap is augmented with the necessary
javascript snippets).
No. Every web-based visual xml editor I am aware of is driven by some
sort of xml-to-xhtml mapping (the rest does raw document styling by
css and direct xml processing - see BXE 1). BTW I guess you would
want xhtml editors to operate on the raw source.
For the xml-to-xhtml variants the content server has to provide
what's needed to build the corresponding map. This is usually xslt
data (XOpus, BXE 2, Yulup) for doing a xml-to-xhtml transformation
whereas xslt's are not only used for rendering the corresponding page
(what you would like to delegate to the server) but also for back-
propagating modifications from xhtml to xml.
What's needed is a simple and possibly standardized way of generating
xslt's required by those editors out of what's already in use in the
xhtml rendering pipelines.
Cheers
Thomas
------------------------------------------------------------------------
-----
Thomas Comiotto
[EMAIL PROTECTED]
Universitaet Zuerich
Informatikdienste Tel: +41 44
63 54541
Winterthurerstrasse 190 +41 44
63 43333
CH-8057 Zuerich Fax: +41 44
63 54505
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
