This is a "Joe Anyone" answer. I'd defer to Ted on "best practices" -- e.g. specific encodings from ISO of the concepts such as "now" and "now minus 7 days" that would most readily be understood by data the growing list of standards-based data discovery tools.
You describe making a dynamically computed start and end date/time (computed by the TDS server) available as THREDDS metadata. Useful, but as we discussed below, not the whole story for discovery purposes. The question seems to be what metadata to provide to also communicate the cycle of updates that goes with the dataset. A natural answer would seem to be that TDS should do as complete a job as it can of generating the Unidata NetCDF Attribute Convention for Dataset Discovery (http://www.unidata.ucar.edu/software/netcdf-java/formats/DataDiscoveryAttConvention.html) metadata. However the NACDD conventions seem incomplete for this task as-is.
Serving outputs of operational models has fairly well defined needs -- e.g. a forecast run every 2 days at 3AM forecasting 10 days into the future and aggregating in a rolling archive of 30 days into the past. So I'd hope for this collection of information (schematic):
John Caron wrote:
On 6/10/2010 10:18 AM, Steve Hankin wrote:Hi John,
-- Steve Hankin, NOAA/PMEL -- address@hidden 7600 Sand Point Way NE, Seattle, WA 98115-0070 ph. (206) 526-6080, FAX (206) 526-6744 "The only thing necessary for the triumph of evil is for good men to do nothing." -- Edmund Burke
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.