Charter for the VO Applications Interest Group

[Sonali A. Kale]

Dear Alberto,

    For interoperation between Aladin and VOPlot
the interchange of data is done using VOTable format.
Application created object IDs are used for referring
to specific objects (points in case of VOPlot).

So the main interface requires both applications
to support methods such as :
(1) loadData
(2) selectVOTableObject(list of objects)
(3) highlightVOTableObject(list of objects)

See http://aladin.u-strasbg.fr/java/FAQ.htx#ExtApp for
details.

Some methods such as select and highlight are application
specific (in this case for visualization), but I think we could
standardize the interchange format to be VOTables between
different VO Tools.

- Best Regards,
Sonali
------------------------------------
Sonali A. Kalé
Persistent Systems Private Limited
http://www.persistent.co.in
Ph: +91 (20) 2567 8900 (ext. 2328)
------------------------------------

----- Original Message -----
From: "Alberto Micol" <Alberto.Micol at eso.org>
To: "Thomas McGlynn" <tam at lheapop.gsfc.nasa.gov>; <apps at ivoa.net>
Sent: Wednesday, March 24, 2004 5:12 PM
Subject: Re: Charter for the VO Applications Interest Group


>
> Dear Tom,
>
> Regarding the charter of the applications interst group
> I was thinking that it would be nice if such group could discuss
> things like "how applications interact" maybe establishing a standard
> for that. For example, the main  AVO demo tool (Aladin) needs to interact
> with specview, voplot, and others in various ways. The way this was done
> for the AVO demo was to declare those other applications "plugins" of
> Aladin.
> Do not ask me the details because I do not know them, you might contact
> Pierre Fernique for that :-)
> Also, once a catalog is passed from Aladin to a plugin (eg voplot)
> there is the need to have the plugin talking back to the main application
> (for example highlighting a point in voplot makes Aladin highlighting
> the catalog entry and its relative identifier onto the displayed image).
>
> So the question would be, what's a VOPlugin ? What are the necessary
> interfaces to that an application should support to be able to
> invoke plugins, or to be invoked as a plugin?
>
> That's my suggestion for the charter of this interest group.
>
> Alberto
>
>