1. International Planetary Data Alliance Registry Project Update September 16, 2011

2. Topics Registries Overview Project Overview Service Registry Prototype 2

3. Project Description At the July 2009 Steering Committee, a new project was discussed regarding the definition of registries. Both the Technical Experts Group (TEG) and the IPDA Architecture have discussed the importance of registries in moving IPDA towards sharing of data and services. Registries provide the ability to "register" services, data, etc. Within the IPDA, it is important that services and data can be "discovered" across the enterprise. Examples of registered items may include services (such as search services), data dictionary elements, data products, and data set and mission information, etc. The purpose of this project is to define the requirements and then the associated registries needed for IPDA so an implementation plan can be developed.

4. IPDA Level 1-2 Requirements 2.1IPDA will develop recommendations for interoperability within a federation of international planetary data archive systems 2.3 IPDA will encourage international planetary data archives to share and exchange data using IPDA data standards 3.3IPDA will maintain a structured data dictionary containing definitions of data elements, their relations, and their scopes in aim to enable standardized descriptions of planetary science data 3.9IPDA will publish standards for querying planetary data system catalogs including standard query models, protocols, and templates of user interfaces

5. Level 3 Registry Requirements 2.1IPDA will develop recommendations for interoperability within a federation of international planetary data archive systems IPDA will develop a registry specification for sharing content between international planetary data archive systems 2.3 IPDA will encourage international planetary data archives to share and exchange data using IPDA data standards IPDA will develop a registry specification for registering services, data products, and information useful to the community. 3.3IPDA will maintain a structured data dictionary containing definitions of data elements, their relations, and their scopes in aim to enable standardized descriptions of planetary science data IPDA will publish the data dictionary to an online registry 3.9IPDA will publish standards for querying planetary data system catalogs including standard query models, protocols, and templates of user interfaces IPDA will maintain a service registry of standard services and their interfaces

6. IPDA Architecture

7. IPDA Data Access and Sharing

8. What is a registry? A registry is “an information system that securely manages any content type and the standardized metadata that describes it” [ Farrukh Najami, ebXML Registry Standard] A Registry addresses the following essential functional requirements* : Discovery and maintenance of registered content. Support for collaborative development, where users can create content and submit it to the registry for use and potential enhancement by the authorized parties. Persistence of registered content. Secure version control of registered content. Federation of cooperating registries to provide a single view of registered content by seamless querying, synchronization, and relocation of registered content. Event notification. * CCSDS Registry Repository Reference Architecture (White Book), October 2009

9. Uses of Registries

10. Registry Service Functions Manage Policy – manage artifact types and required metadata Publish Artifact – request registration of artifacts and their metadata Update Artifact – change registered artifacts and their metadata Approve Artifact – approve registered artifacts Deprecate Artifact – deprecate registered artifacts when no longer pertinent Undeprecate Artifact - undeprecate registered artifacts when their pertinence have been restored Delete Artifact -delete registered artifacts from the registry Query Artifact - discover registered artifacts from the registry by submitting queries against the registered metadata attributes

11. Registry Concept in IPDA Registries are part of the IPDA System Architecture and are planned to be developed to interoperate and share information across IPDA agencies as follows: Service Registry captures descriptions about services provided by the IPDA agencies in which IPDA participants can share their services via this registry to help promote reuse Dictionary Registry captures and stores information object and element definitions that make up the IPDA data dictionary Inventory Registry Captures descriptions about products available within the IPDA system PDS is using an inventory that will be accessible via PDAP

12. Registry Project 2010-2011 Focus has been on two activities Publishing a registry document (posted on http://planetarydata.org/standards/registry- specification/registry-specification/) Creating a prototype service registry (available at http://planetarydata.org/services/registry) 12

13. Registry Service Architecture

14. Registry Service Interface

15. Registry Service Data Model 15

16. Registry Deployment Concept 16

17. Registry APIs The registry specification identifies the following interface including: A web service REST-based external interface which is accessible via the Hypertext Transfer Protocol (HTTP) For managing the registry For search of data holdings, we imagine PDAP being one of the interfaces

18. IPDA Service Registry A place to register and discover tools (and some services)

19. What is it? Web site for member institutions to register tools they’ve developed Also, web services Search for existing tools And web services Links to specification documents, notes, and more

20. Anatomy of a tool or service Name, short description, and abstract Release date, version number, operating system platforms, curator Categorization: Analysis, data reader, design, dissemination, generation, plan Interface types: API, console, GUI, script, web service

21. List of services

22. Creating a service registration

23. Architecture IPDA Web Site PDS Registry Service Web Browser Other Clients HTTP HTML HTTP REST HTTP REST planetarydata.orgpdsops2.jpl.nasa.gov

24. ebXML Registry Information Model Service: a single published use of web- accessible software Has Service Bindings Service Binding: endpoint at which to access a Service Has Specification Links Specification Links: tells how to use an endpoint

25. Services or Tools? ebXML model designed for web services For tools, just use Service and nothing else For services, use Service, Service Binding, and Specification Link

26. How to access it Read only: Visit http://planetarydata.org/services with a browser Read+write: Log in at http://planetarydata.org/login_form Then visit http://planetarydata.org/services Security: must be a member of the “Registrars” user group

27. Next Steps Begin broadly capturing the services available across IPDA groups; make sure their services are registered Improve the website access Open the REST interface to IPDA This could be a potential project to support convergence between PDAP, Registries and other services PDS will work to “open source” its registry software 27

28. Backup