1. T HE I NTERNATIONAL V IRTUAL O BSERVATORY ALLIANCE Service Validators in Practice (within the VAO) Theresa Dower Registry WG 18 May 2011 IVOA Interoperability Meeting -- Naples

2. Usage of Service Validators On service deployment and updates Service providers responsibility Service toolkit authors responsibility? On registry resource publication and ingest Registry owners responsibility Routine registry polling after publication Registry owner, curator, other operational staff 18 May 2011IVOA Interoperability Meeting -- Naples

3. Validators Used Cone Search, SIA at NCSA Derived SSA service OAI (used in RofR process) Basic XML VOResource schema validation No TAP or VOSI Some known issues, esp. SSA 18 May 2011IVOA Interoperability Meeting -- Naples

4. Registry Deployment Harvesting to VAO from IVOA XML Schema validation only Home validationLevel preserved VAO (STScI) Publication XML Schema validation User / Authority / identifier validation Upcoming: service validation Default validationLevel 18 May 2011IVOA Interoperability Meeting -- Naples

5. validationLevels Registry resource-level 2 … Capability-level 2 … 18 May 2011IVOA Interoperability Meeting -- Naples

6. validationLevels 18 May 2011IVOA Interoperability Meeting -- Naples 0 The resource has a description that is stored in a registry. This level does not imply a compliant description. 1 In addition to meeting the level 0 definition, the resource description conforms syntactically to this standard and to the encoding scheme used. 2 In addition to meeting the level 1 definition, the resource description refers to an existing resource that has demonstrated to be functionally compliant.When the resource is a service, it is consider to exist and functionally compliant if use of the service accessURL responds without error when used as intended by the resource. If the service is a standard one, it must also demonstrate the response is syntactically compliant with the service standard in order to be considered functionally compliant. If the resource is not a service, then the ReferenceURL must be shown to return a document without error. 3 In addition to meeting the level 2 definition, the resource description has been inspected by a human and judged to comply semantically to this standard as well as meeting any additional minimum quality criteria (e.g., providing values for important but non-required metadata) set by the human inspector. 4 3++

7. Checking Existing Resources Service validation polling in VAO Michael Preciado, HEASARC Continuously polling subsets of records Cone Search, SIA (OAI/SSA idle) Automated reporting at http://heasarc.gsfc.nasa.gov/vo/validation Human inspection for serious defects, lower-order concerns, errors on bad input, validator bugs. 18 May 2011IVOA Interoperability Meeting -- Naples

8. VAO Validation: Summary Timeouts, known validator issues included. 18 May 2011IVOA Interoperability Meeting -- Naples

9. VAO Validation: Search 18 May 2011IVOA Interoperability Meeting -- Naples

10. VAO Validation: Site Summary Malformed URL still common throughout registries (could be fixed within publishing interfaces). 18 May 2011IVOA Interoperability Meeting -- Naples

11. Process for invalid resources IN DEVELOPMENT. Human inspection of invalid resources Contact curator by email NEW: after long notification period make validationLevel changes to capability in VAO search registry NEW: hide services from registry search results with validationLevel below a minimum value 18 May 2011IVOA Interoperability Meeting -- Naples

12. Meaning for registries/apps Is anyone using validationLevels? Schema allows multiple validationLevels for each resource AND capability No date: assumes each is most recent by validatedBy authority link VAO registry does not fully support 18 May 2011IVOA Interoperability Meeting -- Naples