[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

documentation vs document

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: documentation vs document
  • Date: Wed, 29 May 2002 12:08:21 -0400
Hi John,

I am beginning to have some regrets about what I did yesterday in terms
of misusing <documentation> by adding a name field.   I think it would
make more sense to have a <document> tag that has both a name and a
link:  documentation should be special (a special document???) and
separate.

So I would have something like this:

...

<documentation
xlink:href="http://iridl.ldeo.columbia.edu/SOURCES/.LEVITUS94/.dataset_documentation.html";
/>
<document
xlink:href="http://iridl.ldeo.columbia.edu/SOURCES/.LEVITUS94/.oceanviews.html";
name="oceanviews"/>
<document
xlink:href="http://iridl.ldeo.columbia.edu/SOURCES/.LEVITUS94/.oceanviews2.html";
name="oceanviews2"/>
<document
xlink:href="http://iridl.ldeo.columbia.edu/SOURCES/.LEVITUS94/.Zmix.html";
name="Zmix"/>

...

Does this make sense to you?

Benno

--
Dr. M. Benno Blumenthal          address@hidden
International Research Institute for climate prediction
Lamont-Doherty Earth Observatory of Columbia University
Palisades NY 10964-8000                  (845) 680-4450