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.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.