NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Tom, There's some pretty good discussion of the attribute-vs-element issue at http://www.oasis-open.org/cover/elementsAndAttrs.html In particular, I like the last paragraph of the "Sperberg-McQueen" comments which suggests that it really doesn't matter all that much. Basically, most seem to agree that it depends on how the designer plans to use the XML. In the case of the inventory catalog XML, sub-elements were used to hierarchically organize the datasets and attributes were used for just about everything else (except for free text). Ethan Tom Whittaker wrote: > > Sorry, I had an incompleted thought at the end of my last note: > > > Finally, I don't have much experience in XML, but a few things I've read > > suggest that using attributes instead of elements to describe data. > > should have ended: "...to describe data is a bad idea." > > > Is this > > one of those "religous wars" things? > > tom > > -- > Tom Whittaker (tomw@xxxxxxxxxxxxx) > University of Wisconsin-Madison > Space Science and Engineering Center > Phone/VoiceMail: 608/262-2759 > Fax: 608/262-5974 -- Ethan R. Davis Telephone: (303) 497-8155 Software Engineer Fax: (303) 497-8690 UCAR Unidata Program Center E-mail: edavis@xxxxxxxx P.O. Box 3000 Boulder, CO 80307-3000 http://www.unidata.ucar.edu/
thredds archives: