I guess the issues are
* edit-time (pre-substitution) behavior: it would
be très nice to do DTD-driven editing based on an
extension to XHTML (or any other XML DTD :) , and
* run-time in-browser (post-substitution) behavior:
if there are errors,
* does the doc stay well-formed and XHTML-valid
(so that a picky browser like FFox does not
catastrophically fail to render the document), and
* in a rendered XHTML view, are they visible
(as faulty RIFE tags) or hidden ?
If you want tags to validate _as_XHTML_at_edit-time_, then
the XHTML spec doesn't give you much support; there's only
one user-defined attribute valid for all elements (IIRC;
"class"), so editors would not give you much guidance,
and runtime tag parsing & substitution would be a pain
in the butt (unpacking multiply-assigned attributes).
If common editors could be configured to treat the edit
-time doctype as a RIFE extension to XHTML, that would
be cool, but I'm not sure that's possible. I'm sure it
would very much depend on the editor. Ditto for PI's.
(Short list: XXE, Oxygen, Serna.) But then also the
runtime templating engine could _change_ the doctype
from RIFE-ML to XHTML.
So I suppose that all-in-all, I'd guess that the PI
approach is nicely, robustly, and undemandingly XML-ish.
my 0,02e.
fred
--
F.Baube *
Georgetown/MSFS/1988 * Think pangalactically.
fbaube#saunalahti.fi * Act locally.
gsm +358 41 536 8192 *
wmd 60°11'10.8"N 24°57'36.9"E
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
