[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: why distinctions within XHTML?

• From: David Megginson <david@m...>
• To: "XML-Dev Mailing list" <xml-dev@i...>
• Date: Mon, 30 Aug 1999 11:17:38 -0400 (EDT)

Ann Navarro writes:

 > If I'm going to write an XHTML editor (that's worth anything as an
 > *xhtml editor* vs. just a plain text editor), I surely want to know
 > whether the differences in what can occur in a <p> in strict
 > vs. transitional. If my application doesn't know these differences,
 > it can't provide appropriate options or indicate errors
 > appropriately.

I used the PSGML editor to create dozens of XHTML documents that
conformed to the last working draft, and even though there was just
one XHTML Namespace in that draft, my editor still would not let me
insert a <font> element in a strict-flavoured document.

That's why you have a DTD -- the qualified names identify what things
are (an HTML paragraph), and the DTD or other schema identifies how
things are to be arranged.

You can already use the XHTML DTDs with XML editors like PSGML,
XMetaL, and WordPerfect just fine.  We need to hear another argument.

 > If I'm writing an application that will parse XHTML documents, and
 > apparently I only care that <p> is a structural container, then I
 > suppose I don't care about the differences -- but even that
 > reasoning escapes me, in that if I find <p align=center> when we're
 > purporting to be XHTML 1.0 Strict, then there's a problem.

Sure -- that's why you have a DOCTYPE declaration at the top, so that
validating processors can check the HTML against a DTD.

 > Modularization brings it's own namespace issues to the table. More on that
 > when the next draft becomes public. 

That's an even worse problem coming up -- three namespaces is already
bad enough.  By the way, with SAX, XSL, DOM, or any other existing
infrastructure, three Namespaces does not mean three extra lines of
code; it means triple the code for every part that deals with elements
or attributes (three times as many XSL patterns, for example, not
just three more patterns).


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
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@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Why namespaces?
    • From: Paul Prescod <paul@p...>
  • Re: why distinctions within XHTML?
    • From: Ann Navarro <ann@w...>

• References:
  • Re: NAMESPACES: expressing commonality or distinction
    • From: Ann Navarro <ann@w...>
  • NAMESPACES: expressing commonality or distinction
    • From: "James Tauber" <jtauber@j...>
  • why distinctions within XHTML?
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: why distinctions within XHTML?
    • From: Ann Navarro <ann@w...>

• Prev by Date: Re: why distinctions within XHTML?
• Next by Date: RE: ATTN: Please comment on XHTML (before it's too late)
• Previous by thread: RE: why distinctions within XHTML?
• Next by thread: Re: why distinctions within XHTML?
• Index(es):
  • Date
  • Thread