Component Markup Language

Mark Birbeck Mark.Birbeck at
Thu Feb 4 20:54:02 GMT 1999

> One cannot rely on "HTML 5" as a solution to this problem. The next
> generation of HTML will not provide any such facilities. Information
> about the nature of the next generation HTML can be obtained 
> by reading
> current Working Draft:

Can people please be specific, so I can see if I have lost the plot

If I was to propose a component-XML DTD that began with a tag called
HTML, then others called HEAD and BODY, and it had definitions for text
fields, buttons, drop-boxes, images, tables and more, as well as being
able to call up external programs and all the rest of it; what
ADDITIONAL features is everyone saying they would want to be present in
*their* component-XML that are not in 'mine' (and I really think the
lack of graphics on a button is insufficient justification for spending
the next year writing an entire XHTML!)

I'm not saying that the user-interface has to then be a web browser -
make it Java if you want. All I'm saying is there is a very good syntax
in place for defining user interfaces - why not use it?

Mark Birbeck
Managing Director
Intra Extra Digital Ltd.
39 Whitfield Street
t: 0171 681 4135
e: Mark.Birbeck at

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

More information about the Xml-dev mailing list