Slots in Kyoto

[Guy Rixon]

I'd second that! IVOA needs some reporting structure whereby registry
operators can be told of duff entries. Kyoto would be a good time to set that
up.

On Wed, 2 Mar 2005, Christophe ARVISET wrote:

> Ray
>
> In your presentation at ADASS 2004
> (http://adass.ipac.caltech.edu/Presentations/Tuesday/Plante_O7_1.ppt#33),
> VGs #33-34 mentioned the issue about registry curation. You mentioned that
> many of the existing registry entries are not declared properly and
> therefore could not be a real use for a VO application/client who would
> like to make use of them.
>
> I believe that it would be time to tackle this issue and that it would be
> worth discussing this at Kyoto.
>
> Would you agree ?
>
>
> Cheers
>
> Christophe
>
> At 19:40 01/03/2005, Ray Plante wrote:
> >Hi Tony,
> >
> >On Tue, 22 Feb 2005, Tony Linde wrote:
> > >  Session 1: Registering applications
> > >           + other Registry extensions/amendments
> > >  Session 2: Registry interface
> > >           + Registry Query
> > >  Session 3: Registry data model
> > >           + Registering data quality 'indicators'
> > >           + Plans for V1.0
> >
> >I do plan to attend this meeting.  Your general schedule breakdown looks
> >good to me.  A couple of questions of clarification...
> >
> >   o  I'm unsure what "Registering applications" refers to; is this
> >      the CEA model?  (We should definitely hear about this.)
> >
> >   o  "other Registry extensions/amendments":  do you see this being mainly
> >      in the form of extensions/amendments to schemas, or might it include
> >      interface and architecture issues?
> >
> >Here are some specific things I think we need to talk about and can be fit
> >into your general categories:
> >
> >   Data Model Stuff:
> >     *  Move standardization process forward for the VOResource core
> >           schema.
> >     *  Integration of STC into the VODataService schema
> >     *  Updating the VORegistry schema to support the Registry Interface
> >           spec.
> >   Registry Interface:
> >     *  Remaining issues with RI spec before presentation as PR
> >
> >All of these items require a certain amount of prep work to happen on the
> >list ahead of time.  For example, Kevin & I have been making another pass
> >at the RI spec; we'll bring up some issues for discussion on the list
> >soon.  I'm also preparing some documents on VOResource necessary for
> >moving the standardization process forward.
> >
> > > And which other workgroup sessions should we avoid? As a workgroup, I'd
> > > suggest we should attend the DM Catalogue model session. Any others
> > > important to the workgroup as a whole?
> > >
> > > (Personally I'd like to attend the VOQL session but don't think it is
> > > critical to the workgroup.)
> >
> >I would like to attend the VOQL session.  Our adoption of ADQL for
> >querying registries last year required some minor changes to the ADQL
> >spec; it would be good to keep a connection going between our groups as
> >these standards progress.
> >
> >cheers,
> >Ray
>
>
>
> Cheers
>
> Christophe
>
> --- Christophe ARVISET
> --- European Space Agency (ESA)
> --- European Space Astronomy Centre (ESAC)
> --- Research and Scientific Support Department (RSSD)
> --- Science Operations and Data Systems Division (SCI-SD)
> --- Urb. Villafranca del Castillo
> --- P.O. Box 50727, 28080 Madrid - SPAIN.
> --- Tel: +34 91 813 12 78, Fax: +34 91 813 11 72
> --- E-mail : Christophe.Arviset at esa.int
>

Guy Rixon 				        gtr at ast.cam.ac.uk
Institute of Astronomy   	                Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA		Fax: +44-1223-337523