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.
Ethan and John, I am sorry to be so late for sending my comments. The XML stuff for inventory catalog looks very nice to me. I just raise two questions for you to consider. 1) Datasets may appear in multiple collections. It may cause information repetition (datasets). Have you considered using links to eleminate the repetition as we did in DIMES. 2) I am thinking about multiple data delivery mechanism for one dataset (or data collection in your case). For example, a dataset can be accessed through DODS and is also available for ftp. Do you think we should use multiple values for serverID attributes? It is always possible that a user find a interesting data set through DODS protocol, and want to download the dataset to his/her desktop for intensive analysis. -- Regards! --Ruixin John Caron wrote: > A new version of the inventory catalog XML document is available for your > comments: > > http://www.unidata.ucar.edu/staff/caron/thredds/InvCatalog.html > > This version adds XML namespaces, renames some elements for clarity, and > expands > the documentation element.