Difference: IvoaOps (1 vs. 50)
Revision 502024-12-18 - TamaraCivera
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
Roadmap | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | See the Operations entry in the IVOA Roadmap document (currently 2024A) | ||||||||||||||||||
| > > | See the Operations entry in the IVOA Roadmap document (currently 2024B) | ||||||||||||||||||
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
| |||||||||||||||||||
Revision 492024-12-16 - TamaraCivera
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 2024A)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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 482024-08-23 - TamaraCivera
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 2024A)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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 472024-08-22 - TamaraCivera
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
Roadmap | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | See the Operations entry in the IVOA Roadmap document (currently 2019B) | ||||||||||||||||||
| > > | See the Operations entry in the IVOA Roadmap document (currently 2024A) | ||||||||||||||||||
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
| |||||||||||||||||||
Revision 462023-06-09 - TamaraCivera
IVOA Operations Interest GroupOverviewOrganisation | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
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 | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | Mailing list | ||||||||||||||||||
| > > | Mailing list | ||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
Roadmap | |||||||||||||||||||
| Deleted: | |||||||||||||||||||
| < < | See the Operations entry in the IVOA Roadmap document (currently 2019B) | ||||||||||||||||||
| Added: | |||||||||||||||||||
| > > | See 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: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
| Deleted: | |||||||||||||||||||
| < < | |||||||||||||||||||
| |||||||||||||||||||
Revision 452023-05-03 - MarkTaylor
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: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 442023-04-26 - MarkTaylor
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
| |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 432023-04-18 - MarkTaylor
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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 422022-09-26 - MarkTaylor
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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 412022-04-12 - MarkTaylor
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
| |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 402022-04-06 - MarkTaylor
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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 392021-10-12 - MarkTaylor
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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 382021-05-21 - MarkTaylor
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
| |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 372021-05-13 - MarkTaylor
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 | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 362021-05-10 - MarkTaylor
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: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 352021-04-09 - MarkTaylor
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: | |||||||||||||||||||
| < < |
| ||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 342021-03-08 - MarkTaylor
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: SoftID | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | Following discussions at Interops (Mark in College Park, Markus in Groningen) we are considering recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. This was initially codified on the UserAgentUsage page, but is now being considered as a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid. | ||||||||||||||||||
| > > | Ops 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
| |||||||||||||||||||
Revision 332021-03-05 - MarkTaylor
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. | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | Identifying Operational Clients | ||||||||||||||||||
| > > | Identifying Client/Server software: SoftID | ||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | The wiki page UserAgentUsage discusses best practice for use of the HTTP User-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | ||||||||||||||||||
| > > | Following discussions at Interops (Mark in College Park, Markus in Groningen) we are considering recommendations for best practice in use of the HTTP User-Agent and Server headers so that clients (especially "operational-mode" clients such as validators) and servers can be identified by other software they are interacting with. This was initially codified on the UserAgentUsage page, but is now being considered as a draft IVOA Note edited by Markus Demleitner. This document currently lives at https://github.com/msdemlei/softid. | ||||||||||||||||||
| Deleted: | |||||||||||||||||||
| < < |
Identifying Server SoftwareIn some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTPServer header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar. | ||||||||||||||||||
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||||
Revision 322020-11-02 - MarkTaylor
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 Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Identifying Server SoftwareIn some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTPServer header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar.
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > |
| ||||||||||||||||||
| |||||||||||||||||||
Revision 312020-02-10 - MarkTaylor
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. | |||||||||||||||||||
| Changed: | |||||||||||||||||||
| < < | |||||||||||||||||||
| > > | |||||||||||||||||||
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 Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Identifying Server SoftwareIn some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTPServer header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar.
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||||
Revision 302019-10-18 - MarkTaylor
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
| |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > | 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 Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Identifying Server SoftwareIn some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTPServer header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar.
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||||
Revision 292019-10-15 - MarkTaylor
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
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. | |||||||||||||||||||
| Added: | |||||||||||||||||||
| > > | |||||||||||||||||||
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 Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Identifying Server SoftwareIn some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTPServer header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar.
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||||
Revision 282019-10-15 - MarkTaylor
IVOA Operations Interest Group | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Chair: Mark Taylor Vice Chair: Steve Groom | ||||||||||||||||
| > > | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | IVOA Operations Interest Group Charter | ||||||||||||||||
| > > | Overview | ||||||||||||||||
| Added: | |||||||||||||||||
| > > |
Organisation
| ||||||||||||||||
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. | |||||||||||||||||
| Added: | |||||||||||||||||
| > > | See also the Operations IG Charter. | ||||||||||||||||
Specific responsibilities
| |||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | Organisation | ||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Chair: Mark Taylor | ||||||||||||||||
| > > | Mailing list | ||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Vice Chair: Steve Groom | ||||||||||||||||
| > > |
| ||||||||||||||||
| Added: | |||||||||||||||||
| > > | |||||||||||||||||
Operations Projects | |||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | Procedure for Removing Non-Responsive Services | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | VO-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. | ||||||||||||||||
Federated Validation Services | |||||||||||||||||
| Added: | |||||||||||||||||
| > > | The 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. | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | NCSA/HEASARC Validation tests (Conesearch and SIA) | ||||||||||||||||
| > > | |||||||||||||||||
| Added: | |||||||||||||||||
| > > | |||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | VO Paris Validation Test ESA Validation Tests | ||||||||||||||||
| 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. | |||||||||||||||||
| Added: | |||||||||||||||||
| > > | 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 Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | |||||||||||||||||
| > > | Identifying Server Software | ||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Mailing list | ||||||||||||||||
| > > | In some circumstances it is useful for a client (espeically an operational client such as a validator) to know what server software (e.g. VO publication suite) is running at a service it is using. Following Markus's talk in Groningen (Oct 2019) we are investigating use of the HTTP Server header for this purpose; if that doesn't work we might look at another convention such as a new VO-Server header or similar. | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < |
| ||||||||||||||||
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | Links | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | The earlier list of validators is now subsumed into the IvoaValidatorsSummary. | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | Continuous hourly monitoring of VO services is available at the HEASARC | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group | ||||||||||||||||
| |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
Revision 272019-10-12 - MarkTaylor
IVOA Operations Interest GroupChair: Mark Taylor Vice Chair: Steve Groom IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Mark Taylor Vice Chair: Steve GroomOperations ProjectsProcedure 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. | |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
Federated Validation Services | ||||||||||||||||
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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Identifying Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 262019-09-17 - MarkTaylor
IVOA Operations Interest GroupChair: Mark Taylor Vice Chair: Steve Groom IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Mark Taylor Vice Chair: Steve GroomOperations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Identifying Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Mailing list
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
| |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 252019-08-22 - MarkTaylor
IVOA Operations Interest Group | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Chair: Tom McGlynn Vice Chair: Mark Taylor | ||||||||||||||||
| > > | Chair: Mark Taylor Vice Chair: Steve Groom | ||||||||||||||||
IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
Organisation | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Chair: Tom McGlynn | ||||||||||||||||
| > > | Chair: Mark Taylor | ||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Vice Chair: Mark Taylor | ||||||||||||||||
| > > | Vice Chair: Steve Groom | ||||||||||||||||
| Added: | |||||||||||||||||
| > > | |||||||||||||||||
Operations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Identifying Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point.
Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 242019-05-12 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Identifying Operational Clients | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | The wiki page UserAgentUsage discusses best practice for use of the HTTP User-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | ||||||||||||||||
| > > | The wiki page UserAgentUsage discusses best practice for use of the HTTP User-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | ||||||||||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 232018-11-22 - MarkTaylor
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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. | |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
Identifying Operational ClientsThe wiki page UserAgentUsage discusses best practice for use of the HTTPUser-Agent header to identify clients involved in operations-related (as opposed to end-user) service queries. At time of writing (11/2018) this is work in progress. It might turn into a Note at some point. | ||||||||||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 222018-11-06 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 212018-05-27 - MarkTaylor
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations ProjectsProcedure 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.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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests 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.Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
LinksThe earlier list of validators is now subsumed into the IvoaValidatorsSummary. Continuous hourly monitoring of VO services is available at the HEASARCDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 202017-10-27 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
Organisation | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | Chair: Tom McGlynn | ||||||||||||||||
| > > | Chair: Tom McGlynn | ||||||||||||||||
Vice Chair: Mark Taylor
Operations Projects | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | [June 2015] Procedure for Removing Non-Responsive Services | ||||||||||||||||
| > > | Procedure for Removing Non-Responsive Services | ||||||||||||||||
| VO-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. | |||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | [June 2015] Coordination of VO validation services | ||||||||||||||||
| Added: | |||||||||||||||||
| > > | A revised procedure was adoped by the IVOA in October 2016.
Coordination of VO validation services | ||||||||||||||||
| It 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper. | ||||||||||||||||
| > > | 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. | ||||||||||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < |
| ||||||||||||||||
| |||||||||||||||||
| Changed: | |||||||||||||||||
| < < |
| ||||||||||||||||
| > > |
| ||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
Links | |||||||||||||||||
| Changed: | |||||||||||||||||
| < < | IvoaValidatorsSummary | ||||||||||||||||
| > > | The earlier list of validators is now subsumed into the IvoaValidatorsSummary. | ||||||||||||||||
| Changed: | |||||||||||||||||
| < < | VO Paris validators: for use directly by developers or to search results of automated scans. | ||||||||||||||||
| > > | Continuous hourly monitoring of VO services is available at the HEASARC | ||||||||||||||||
| Deleted: | |||||||||||||||||
| < < | ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repo | ||||||||||||||||
DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 192017-10-18 - MarkTaylor
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||||
| Added: | |||||||||||||||||
| > > |
| ||||||||||||||||
LinksIvoaValidatorsSummary VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repoDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||||
Revision 182017-05-24 - KostandinVrioni
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test | |||||||||||||||
| Changed: | |||||||||||||||
| < < | ESA Validation Tests | ||||||||||||||
| > > | ESA Validation Tests | ||||||||||||||
Data from these documents has been combined into the following documents:
These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.
Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
LinksIvoaValidatorsSummary VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repoDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
| Added: | |||||||||||||||
| > > |
| ||||||||||||||
Revision 172017-05-08 - MarkTaylor
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||
| Added: | |||||||||||||||
| > > |
| ||||||||||||||
LinksIvoaValidatorsSummary VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repoDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
Revision 162017-02-20 - MarkTaylor
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings | |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| |||||||||||||||
| Changed: | |||||||||||||||
| < < |
| ||||||||||||||
| > > |
| ||||||||||||||
| Added: | |||||||||||||||
| > > |
| ||||||||||||||
LinksIvoaValidatorsSummary VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repoDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
Revision 152016-04-18 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings
| |||||||||||||||
| Changed: | |||||||||||||||
| < < | |||||||||||||||
| > > | |||||||||||||||
| Added: | |||||||||||||||
| > > |
| ||||||||||||||
LinksIvoaValidatorsSummary VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repoDocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
Revision 142016-04-11 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings
Links | |||||||||||||||
| Added: | |||||||||||||||
| > > | IvoaValidatorsSummary | ||||||||||||||
VO Paris validators: for use directly by developers or to search results of automated scans.
ESA Validators for DAL services
NCSA Cone search and Simple Image Access validators.
TAPLint included in STILTS.
VO Monitoring at the HEASARC
VO Validation at the HEASARC
Validators at VO/Paris
Cone search validator at NCSA
SIA Validator at NCSA
Validator for IVOA identifiers with examples
Validator/Resolver for Publisher dataset identifiers with examples
Validation suite for RegTAP services: svn repo
DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
Revision 132015-10-31 - MarkusDemleitner
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests Data from these documents has been combined into the following documents: These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper.Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA | |||||||||||||||
| Added: | |||||||||||||||
| > > | Validator for IVOA identifiers with examples Validator/Resolver for Publisher dataset identifiers with examples Validation suite for RegTAP services: svn repo | ||||||||||||||
DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||||
Revision 122015-09-28 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] Coordination of VO validation services | |||||||||||||
| Deleted: | |||||||||||||
| < < | A comparison of the Cone search validation errors is now availabla | ||||||||||||
| It 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests | |||||||||||||
| Changed: | |||||||||||||
| < < | The cone search tests from the three validators are compared in this first attempt to standardize the nomenclature for the tests. | ||||||||||||
| > > | Data from these documents has been combined into the following documents: | ||||||||||||
| Added: | |||||||||||||
| > > | These documents suggest a standard approach for identifying validation tests that we may wish to develop into a white paper. | ||||||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||||
| Added: | |||||||||||||
| > > |
| ||||||||||||
Revision 112015-09-25 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] Coordination of VO validation services | |||||||||||
| Added: | |||||||||||
| > > | A comparison of the Cone search validation errors is now availabla | ||||||||||
It 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.
NCSA/HEASARC Validation tests (Conesearch and SIA)
VO Paris Validation Test
ESA Validation Tests
The cone search tests from the three validators are compared in this first attempt to standardize the nomenclature for the tests.
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||
| Changed: | |||||||||||
| < < |
| ||||||||||
| > > |
| ||||||||||
Revision 102015-07-22 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) VO Paris Validation Test ESA Validation Tests | |||||||||||
| Added: | |||||||||||
| > > | The cone search tests from the three validators are compared in this first attempt to standardize the nomenclature for the tests. | ||||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||||
| Added: | |||||||||||
| > > |
| ||||||||||
Revision 92015-07-14 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA) | |||||||||
| Added: | |||||||||
| > > | VO Paris Validation Test ESA Validation Tests | ||||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||
| Added: | |||||||||
| > > |
| ||||||||
Revision 82015-07-10 - RenaudSavalle
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. NCSA/HEASARC Validation tests (Conesearch and SIA)Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| |||||||||
| Added: | |||||||||
| > > |
| ||||||||
Revision 72015-07-06 - TomMcGlynn
IVOA Operations Interest GroupChair: Tom McGlynn Vice Chair: Mark Taylor IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationChair: Tom McGlynn Vice Chair: Mark TaylorOperations Projects[June 2015] 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.[June 2015] 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. | ||||||||
| Added: | ||||||||
| > > | NCSA/HEASARC Validation tests (Conesearch and SIA) | |||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. VO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Revision 62015-06-19 - TomMcGlynn
IVOA Operations Interest Group | ||||||||
| Changed: | ||||||||
| < < | Chair (Interim): Tom McGlynn Vice Chair: TBD | |||||||
| > > | Chair: Tom McGlynn Vice Chair: Mark Taylor | |||||||
IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
Organisation | ||||||||
| Changed: | ||||||||
| < < | Interim Chair: Tom McGlynn | |||||||
| > > | Chair: Tom McGlynn | |||||||
| Added: | ||||||||
| > > | Vice Chair: Mark Taylor
Operations Projects[June 2015] 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.[June 2015] 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. | |||||||
Mailing list
Operations sessions
IVOA Interoperability Meetings | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Links | ||||||||
| Added: | ||||||||
| > > | VO Paris validators: for use directly by developers or to search results of automated scans. ESA Validators for DAL services NCSA Cone search and Simple Image Access validators. TAPLint included in STILTS. | |||||||
VO Monitoring at the HEASARC
VO Validation at the HEASARC
Validators at VO/Paris
Cone search validator at NCSA
SIA Validator at NCSA
DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| ||||||||
Revision 52015-06-17 - RenaudSavalle
IVOA Operations Interest GroupChair (Interim): Tom McGlynn Vice Chair: TBD IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationInterim Chair: Tom McGlynn Mailing list
Operations sessions
IVOA Interoperability Meetings
LinksVO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Revision 42015-05-14 - TomMcGlynn
IVOA Operations Interest GroupChair (Interim): Tom McGlynn Vice Chair: TBD IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationInterim Chair: Tom McGlynn Mailing list
Operations sessions
| ||||||||
| Added: | ||||||||
| > > |
IVOA Interoperability Meetings
| |||||||
LinksVO Monitoring at the HEASARC VO Validation at the HEASARC Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSADocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| ||||||||
Revision 32015-05-07 - TomMcGlynn
IVOA Operations Interest GroupChair (Interim): Tom McGlynn Vice Chair: TBD IVOA Operations Interest Group CharterGoal 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.Specific responsibilities
OrganisationInterim Chair: Tom McGlynn Mailing list
Operations sessions
LinksVO Monitoring at the HEASARC VO Validation at the HEASARC | ||||||||
| Added: | ||||||||
| > > | Validators at VO/Paris Cone search validator at NCSA SIA Validator at NCSA | |||||||
DocumentsIVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group
| ||||||||
Revision 22015-05-07 - TomMcGlynn
IVOA Operations Interest GroupChair (Interim): Tom McGlynn Vice Chair: TBD IVOA Operations Interest Group Charter | ||||||||
| Added: | ||||||||
| > > | Goal of the IVOA Operations Interest Group | |||||||
| Added: | ||||||||
| > > | Coordinate 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.
Specific responsibilities
| |||||||
Organisation | ||||||||
| Added: | ||||||||
| > > | Interim Chair: Tom McGlynn | |||||||
Mailing list
| ||||||||
| Changed: | ||||||||
| < < | ||||||||
| > > | Operations sessions | |||||||
| Deleted: | ||||||||
| < < | Interop MeetingsOperations sessions at Interop meeting will be organised for: | |||||||
Links | ||||||||
| Added: | ||||||||
| > > | VO Monitoring at the HEASARC VO Validation at the HEASARC | |||||||
Documents | ||||||||
| Changed: | ||||||||
| < < | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> | |||||||
| > > | IVOAOpsCharter-v20150327.docx: Charter for the IVOA Operations Interest Group | |||||||
| Changed: | ||||||||
| < < | ||||||||
Revision 12015-04-29 - TomMcGlynn
IVOA Operations Interest GroupChair (Interim): Tom McGlynn Vice Chair: TBD IVOA Operations Interest Group CharterOrganisationMailing list
Interop MeetingsOperations sessions at Interop meeting will be organised for:
LinksDocuments<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> <--
|
View topic | History: r50 < r49 < r48 < r47 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback