Lists Home |
Date Index |
- From: Marcus Carr <email@example.com>
- To: firstname.lastname@example.org
- Date: Wed, 12 Jan 2000 16:12:20 +1100
"Clark C. Evans" wrote:
> Let me re-phrase this. Are there examples of mixed-model
> use-cases, where one DTD does not have mixed-content,
> and a subordinate/contained DTD (ANY) does use mixed-content.
Yes, in my experience this is still quite common. For example, I'm currently working on a
system that relies on assembling fragments in different configurations to produce new
products. The top level is never mixed content - it's just a collection of elements that
are DOCTYPEs when they're created. These elements certainly might not themselves contain
mixed content, but there is every possibility that an element further down the tree will.
Perhaps we're just looking at this from different perspectives, but I'd be surprised if
you could substantially reduce the possibility of mixed content without protest.
> 2. Would it make sense to allow include
> <xhtml:plain> as a no-op for cases where
> xhtml mixed-content is included in eCommerce
> non-mixed content.
Wouldn't that be kind of a modern-day <blink>? It's hard to see any benefit for anything
Marcus Carr email: email@example.com
Allette Systems (Australia) www: http://www.allette.com.au
"Everything should be made as simple as possible, but not simpler."
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions now closed in preparation for transfer to OASIS.