heres another strawman, incorporating our latest discussions:
1) Collections as datasets. Ethan and I think the cleanest way to allow
"collections as datasets" is to allow nested datasets. Collections remain
just groups of datasets. A Collection as a dataset is done as a dataset with
nested datasets. Nested dataset elements (Joe's meaning #2) should imply (in
some way we need to clarify better) nested datasets (Joe's meaning #1 and
2) allow compound services again. I have talked myself into that these will
be often useful.
3) services are now contained within any collection, rather than having to
be all in the top catalog element. They are scoped by the collection they
are in (so we no longer use ID, since those are global). This makes a
catalogRef have (almost) the same semantics as a collection.
4) a catalog now only has exactly one collection element. (i considered
eliminating catalog but i think its better this way).
5) "attribute" changed to "property" (tired of saying "the attribute
6) access element can specify an absolute URL with a serverType -or- a
reletive URL with a serverID.
Unless I get a barrage of objections, I will document this in more detail
ASAP. I will be gone for a week starting next Tuesdy, so Ethan will continue
the conversation as needed. Hopefully, we can converge soon and take a
break! I think I have incorporated all the good ideas i have heard in this
discussion. Have I left out something, or do you think any feature is not
worth the complexity?
>From owner-thredds@xxxxxxxxxxxxxxxx Fri 7 2002 Jun 21:54:15
Date: Fri, 7 Jun 2002 21:54:15 -0400
From: Benno Blumenthal <benno@xxxxxxxxxxxxxxxx>
To: THREDDS <thredds@xxxxxxxxxxxxxxxx>
Subject: Re: latest Catalog XML
Received: (from majordo@localhost)
by unidata.ucar.edu (UCAR/Unidata) id g581sH203986
for thredds-out; Fri, 7 Jun 2002 19:54:17 -0600 (MDT)
Received: from beluga2.ldgo.columbia.edu (beluga2.ldgo.columbia.edu
by unidata.ucar.edu (UCAR/Unidata) with ESMTP id g581sGJ03982
for <thredds@xxxxxxxxxxxxxxxx>; Fri, 7 Jun 2002 19:54:16 -0600 (MDT)
Received: (from nobody@localhost)
by beluga2.ldgo.columbia.edu (8.11.6/8.11.6/d: iri.mc,v 1.4 2001/12/06
15:09:45 root Exp root $) id g581sF612412
for thredds@xxxxxxxxxxxxxxxx; Fri, 7 Jun 2002 21:54:15 -0400 (EDT)
Received: from 184.108.40.206 ( [220.127.116.11])
as user benno@xxxxxxxxxxxxxxxx by iri.columbia.edu with HTTP;
Fri, 7 Jun 2002 21:54:15 -0400
Content-Type: text/plain; charset=iso-8859-1
User-Agent: Internet Messaging Program (IMP) 3.0
Quoting John Caron <caron@xxxxxxxxxxxxxxxx>:
> Recent changes:
> 1) Collections as datasets. Ethan and I think the cleanest way to allow
> "collections as datasets" is to allow nested datasets. Collections remain
> just groups of datasets. A Collection as a dataset is done as a dataset
> nested datasets. Nested dataset elements (Joe's meaning #2) should imply
> some way we need to clarify better) nested datasets (Joe's meaning #1 and
This does not quite work for me, unless you allow a catalog to contain exactly
one collection or exactly one dataset. Right now the only thredds thing that
can be pointed to is a catalog, with the added provision that a catalog with one
collection is effectively that collection -- I would like to point to datasets
with thredds, which requires either that a catalog can point to a dataset or a
collection, or that you extend collection to be isomorphic to dataset. The
catalog modification would be preferable.
> 6) access element can specify an absolute URL with a serverType -or- a
> reletive URL with a serverID.
If you are going to have a base element in service, it is only fair that you
have a suffix element, too. Please leave the suffix element in.