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

Re: latest Catalog XML



Benno Blumenthal wrote:
> 
> You are quite right:  going to the extreme of one dataset per xml
> document is not very efficient.   Having the ability to make a
> thredds catalog that contains a single URL does not mean that I
> am going to use it for all datasets:  that is not my plan.   I
> just want the ability to do it should it seem appropriate. Given
> that one server's collection is another server's dataset, you
> really ought to allow it.
> 
> I think I can paraphrase your point about dataset aliases in
> that, since one can create an alias for a dataset, it does not
> matter that whatever document it is contained in may or may not
> contain a useless collection.  True in a functional sense, I
> suppose, but rather ugly code that forces one to put in a
> collection even when it has no meaning in the sense of being a
> desired nesting.
> 
> At the moment, I am requesting two small changes: let a catalog
> contain a collection or a dataset, and let suffix be a property
> of a service.   The first one may not be particularly useful,
> but it is quite minor.   The second one is extremely useful to
> me:  I cannot make use of compound services without it.

The first item seems quite minor but would actually move some complexity back
into the catalog element that we recently removed for various reasons.

The second item we addressed by allowing service elements to contain property
elements. Doesn't capture the full semantics of what you are trying to convey
but a stop-gap measure while we work on this further.

> Please Please Please

Considering this is the current DTD acceptable to you till the next round of
changes?

Ethan

> Benno

-- 
Ethan R. Davis                       Telephone: (303) 497-8155
Software Engineer                    Fax:       (303) 497-8690
UCAR Unidata Program Center          E-mail:    address@hidden
P.O. Box 3000
Boulder, CO  80307-3000              http://www.unidata.ucar.edu/

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.