IVOA Operations Interest GroupOverviewOrganisation
Goal of the IVOA Operations Interest GroupCoordinate and publicize activities of individuals, institutions and groups interested in facilitating robust operations of distributed astronomy applications, particularly those based upon implementations of IVOA protocols. See also the Operations IG Charter.Specific responsibilities
Mailing list
RoadmapSee the Operations entry in the IVOA Roadmap document (currently 2019B)Operations ProjectsFederated Validation ServicesThe following links are to reports from services that perform bulk validation on a regular basis of all registered services of particular types (SCS, SIA, SSA, TAP, ...). If you are the operator of a registered service, you can (and should!) go here to see whether your service is passing the validation tests.Coordination of VO validation servicesIt was agreed that the three sites that are currently collecting validation statistics will try to coordinate their activities. The first step is to provide a standard set of identifiers for issues so that results from the validators can be compared. This will allow us to compare the validator results and 'validate' the validators. Data from these documents has been combined into the following documents: Analysis of the results from these documents suggests that the validators are making somewhat different queries and that any given validator is only testing a subset of all poassible errors. Negative results regarding a service are generally valid. In principle a service should pass all validators.List of Validation SoftwareThe Operations IG maintains a list of available validation software is indexed by the IVOA standard whose content they check, on the wiki page IvoaValidatorsSummary. This list is usually reviewed at six-monthly Interop meetings, but if you have updates you can edit the wiki page directly.Procedure for Removing Non-Responsive ServicesVO-Paris has presented a plan for a process for removing non-responsive services from the Registry which was presented to the Exec and discussed in the Interest Group. A revised version will be provided. A revised procedure was adoped by the IVOA in October 2016.Identifying Client/Server software: SoftIDOps IG is considering best practice for client and server software to report its identity and purpose to components with which is is interacting (User-Agent and Server HTTP headers). For more information see page SoftID.
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||||
Changed: | |||||||||||||||||||
< < |
| ||||||||||||||||||
> > |
| ||||||||||||||||||
Added: | |||||||||||||||||||
> > |
| ||||||||||||||||||
|