Lists Home |
Date Index |
- From: "Simon St.Laurent" <firstname.lastname@example.org>
- To: Ann Navarro <email@example.com>, "XML-Dev Mailing list" <firstname.lastname@example.org>
- Date: Mon, 30 Aug 1999 10:36:29 -0400
At 10:11 AM 8/30/99 -0400, Ann Navarro wrote:
>At 10:12 AM 8/30/99 +0800, James Tauber wrote:
>>However, as David Megginson and Tim Bray have argued, capturing the
>>commonality between, say, "p" in each DTD is not just valuable, but pretty
>I think that the distinctions are just as vital, from the global
>perspective, not just from an application developer perspective.
This may sound like a stupid question, but as I stated earlier I've never
seen those distinctions as either useful or worthwhile.
In what sense do you see those distinctions as vital? What do they do,
apart from add varying levels of obfuscation? What is this 'global
perspective', and how does it matter to developers and users?
It really reads like a badly thought-out grandfather clause foolishly
insterted into HTML a few versions ago. Sometimes history is an anchor
dragging us down rather than a useful guide to the future.
Adding namespaces to an issue that's already of uncertain value seems to
generate enormous amounts of chaos. Personally, I'd have like to see
namespaces used to indicate modules within XHTML - though I know that
presents large problems as well - not to identify different flavors of
After more coffee, I'll try to come up with better questions.
XML: A Primer (2nd Ed - September)
Building XML Applications
Inside XML DTDs: Scientific and Technical
Sharing Bandwidth / Cookies
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)