xml-dev - When to use attributes vs. elements

[peter@weblogic.com (Peter Seibel)]

Is there an XML philosophy (or an SGML philosophy for that matter) about
when to use attributes vs when to use elements when desigining a document
type. For example if I was writing a document type for representing (part)
java classes I could have something like:

<class>
  <package>x.y.z</package>
  <name>Foo</name>
  <!-- other more complicated stuff: definitely elements -->
</class>

or I could have:  

<class package="x.y.z" name="Foo">
  <!-- other more complicated stuff: definitely elements -->
</class>

Obviously I wouldn't use attributes, if the value had any structure to it.
But in a case like this is there some principle that would give some guidence?

-Peter

P.S. Actually in the attribute case I think I'd do something more like:
<class name="x.y.z.Foo"> and let the application split apart the package
part from the base name; that way I could declare name to be ID since it
should be unique.

-- 
Peter Seibel          Perl/Java/English Hacker      peter@weblogic.com

                     Is Windows98 Y2K compliant? 



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