why distinctions within XHTML?

[Jeff Greif]

The ability to put XHTML inside XML seems just to depend upon
 -- having a well-defined XHTML
 -- having a DTD or schema for the containing document that allows XHTML
elements inside some of the XML elements it defined.  Clearly the XHTML
modularization will help with this.

The ability to put XML inside XHTML is more problematic.  Has anyone ever
proposed some kind deferred validation -- the document is well-formed but
not valid according to the XHTML DTD, but it becomes valid when the XML is
transformed by the accompanying XSL stylesheet into XHTML?  That is, the
document with the XSL result tree substituted for the original XML becomes a
valid document.  In general, the application processing the document might
be required, as instructed by the document contents, to process the document
in several stages, deferring validation until some of those stages had
completed.  Is anyone working on something like this?

Jeff

----- Original Message -----
From: Mark Birbeck <Mark.Birbeck at iedigital.net>
To: XML-Dev Mailing list <xml-dev at ic.ac.uk>
Sent: Friday, September 03, 1999 5:02 AM
Subject: RE: why distinctions within XHTML?


> The world needs the ability to nest XHTML inside XML and XML inside
> XHTML as soon as possible, true. But that will take schemas if you want
> validation, so there's nothing XHTML can do about that. The world also
> wants lots of neat little chunks of parts of XHTML to put in their
> mobile phones and toaster browser code. But that's still early days.



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)