Altova Mailing List Archives

Re: Content v. attribute

From: "James Tauber" <jtauber@-------.--->
To: <xml-dev@--.--.-->
Date: 10/26/1998 6:19:00 PM
-----Original Message-----
From: Dave Winer <dave@u...>

>I consider it a flaw of XML that it has two ways to do hierarchy

Bear in mind that XML was designed primarily for *document* interchange. The
attribute vs element decision (which is really just a markup vs content
decision)  IMO, is a lot less clear in data-centric applications than it is
in document-centric ones. XML might have looked quite different if the
things people are doing nowadays with XML were thought up when SGML was
being developed.

James Tauber / jtauber@j... /
Associate Researcher, Electronic Commerce Network
Curtin University of Technology, Perth, Western Australia

Maintainer of :, and

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as:
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...)


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.