UN Science Workshop in Tokyo, June, 2007

[Kirk.Borne at gsfc.nasa.gov]

Thank you Rick, what you say is right on.  Yes, CDF does 
provide a framework for delivering (and storing) time series 
data.  So, let us not re-invent things that already exist.  
And of course VOEvent is obviously not the same as STC, 
nor is VOEvent supposed to be a data format for time series.

I think someone in this thread asked about our level
of interaction with the heliophysics research community.
I know that there are a lot of interactions, especially in 
my group at NASA-Goddard, where we interact with several of
the VxO's (Virtual 'anything' Observatories): VSO, VITMO,
VIRBO, VSPO, VHO, and more (including the SPASE data dictionary
project).  So, the interaction and synergy is taking place, 
and hopefully will grow in the months and years ahead.  
In particular, our CDF group is using NetCDF and OPeNDAP 
(from Peter Fox's UCAR group).  I believe that some of these 
technologies would be quite useful to IVOA.

- Kirk


> From: "Frederic V. Hessman" <hessman at Astro.physik.Uni-Goettingen.de>
> Subject: Re: UN Science Workshop in Tokyo, June, 2007
> Date: Mon, 23 Apr 2007 12:16:48 +0200
> To: Silvia Dalla <s.dalla at manchester.ac.uk>
> Cc: Rob Seaman <seaman at noao.edu>, IVOA List VOEvent <voevent at ivoa.net>,
      Peter Fox <pfox at ucar.edu>
> 
> > However, I am not entirely clear about what you mean with
> > 'VOEvent is a reasonable choice for reporting almost any time
> > sequence of measurements'. Please could you elaborate?
> >
> > There have been efforts to standardise data formats for time
> > series data - one such standard, becoming more and more popular,
> > is CDF:
> > http://cdf.gsfc.nasa.gov/
> 
> The point was that VOEvent shouldn't be transfering data but  
> reporting the existence of such data.  Thus, the data format is -  
> formally - irrelevant.
> 
> > I don't think there is currently a standard way of reporting
> > events, nor of querying for data within a specified time
> > range - this is why we drafted the Simple Time Access Protocol
> > proposal:
> > http://wiki.astrogrid.org/bin/view/Astrogrid/SimpleTimeAccessProtocol
> 
> As little as the VOEventers generally like STC, we've been there,  
> done that:  STAP needs STC-compliance to be fully general (if one  
> reports a solar flare that might be connected with a later  
> ionospheric radio squak, what's the meaning of "UT"?) and STC needs  
> (again) to be pushed to support really simple STAP-like queries (via  
> standard STC time environments, just as we pushed standard sky- 
> coordinate environments) to minimize the STC-gobblety-gook.
> 
> Rick
> 
> ------------------------------------------------------------------------ 
> ------------------------
> Dr. Frederic V. Hessman     Hessman at Astro.physik.Uni-Goettingen.DE
> Institut für Astrophysik          Tel.  +49-551-39-5052
> Friedrich-Hund-Platz 1         Fax +49-551-39-5043
> 37077 Goettingen                 Room F04-133
> http://www.Astro.physik.Uni-Goettingen.de/~hessman
> ------------------------------------------------------------------------ 
> -------------------------
> MONET: a MOnitoring NEtwork of Telescopes
> http://monet.Uni-Goettingen.de
> ------------------------------------------------------------------------ 
> -------------------------
> 
> 

-----------------------------------------------------------------------------
Dr. Kirk D. Borne
NASA Goddard Space Flight Center, SSDOO Program Manager, Perot Systems (ex-QSS)
and George Mason University, Associate Professor, Computational & Data Sciences 
<mailto:kirk.borne at gsfc.nasa.gov>  Tel. +1-301-286-0696  Fax: 301-286-1771
Staff page:      http://rings.gsfc.nasa.gov/
US Virtual Observatory:  http://www.us-vo.org/
Large Synoptic Survey Telescope:  http://www.lssto.org/