applications software metadata

[Guy Rixon]

Roy,

I suggest that you need a VOEventCapability which describes the exact use of
VOEvent by a service and can be added to the registration of a service that is
not primarily "about" VOEvent handling. This fits with the model being
developed on the reg-dm list.

Under the proposed new model (which is not quite accepted yet even in the
reg-dm group), Capability elements are independent of each other and any
Service resource can have any number of them.  Therefore, it seems reasonable
that any WG developing a standard can develop their own Capability sub-type to
go with the standard, and can do this independently of other WGs.

Cheers,
Guy

On Tue, 7 Feb 2006, Roy Williams wrote:

> On Feb 6, 2006, at 2:12 PM, Robert Hanisch wrote:
> > Here is a V0.1 draft of applications software metadata. 
>
> I would like to start a mechanism to register VOEvent servers. Every
> service that can resolve VOEvent identifiers should be part of the
> registry infrastructure. Services would have specialized metadata with
> information about which protocols are used, how it uses iamalive
> packets, if it publishes original or aggregated or filtered streams,
> where the content comes from, who is in charge, etc etc.
>
> (a) How do I get such registry extensions properly built and approved?
> There are quite a few registry extensions now, do we all work
> independently or is there an IVOA process?
>
> (b) Is this part of the Applications metadata thread or am I in the
> wrong place? If the latter, is this purely a matter for the VOEvent WG,
> or would Registry WG get involved?
>
> Roy
>
>
>
> California Institute of Technology
> 626 395 3670
>

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