IPDA Registry Definitions Project Dan Crichton Pedro Osuna Alain Sarkissian

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.

Work Plan 30-Aug Project and Project Members Defined 1-Nov Registry Requirements Identified 1-Dec Registry architecture and associated set of registry types in PowerPoint 1-Feb Registry white paper concept 1-Mar Telecon with the TEG regarding registries 1-May Draft implementation plan 1-Jul Present results to the IPDA Steering Committee

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

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

IPDA Architecture

IPDA Data Access and Sharing

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

Uses of Registries

Registry/Repository System Component View* 10 Archive Mgmt Distribution Data Analysis Modeling Data Acquisition Science Planning Domain Data Models Local Data Models Repository Service Registry Service PDAP Service Data Access Services IPDA Common Schema & Dictionaries Representative Functional Objects Information Management Functional Objects Metadata / Resources Data Objects Query / Results * CCSDS Info Arch Ref Model

Proposed IPDA Registry Class Types Service Registry: Manages information about IPDA services – NOTE: This may be a simple database in practice with a webpage that shows the services Metadata Registry: Manages data dictionary and schema information including data elements (keywords) and values Resource Registry: Manages information about missions, instruments, targets, etc. Data Registry: Manages information about data sets, products, documents and software

Registry Objects Architecture IPDA Registry Objects IPDA Registry Objects IPDA Services Metadata Objects (Dictionary, Schemas) Resources (Targets, Missions, Instruments ) Data (Data Sets, Products, Documents)

IPDA Registry Scenario #1 IPDA/PDS Dataset Information Request for a IPDA/PDS Dataset Information – IPDA client requests information from a IPDA Service Registry regarding details of data set services – IPDA Service Registry returns information regarding registries that serve the data set information – IPDA client requests the data set information from an IPDA compliant data registry of registered data sets using the PDAP interface

IPDA Registry Scenario #2 Semantic Validation Validate PDS/IPDA Label – An IPDA compliant validation tool requests information regarding valid values from an IPDA data dictionary registry for a specific data element (e.g., MISSION_NAME) using the PDAP protocol – The registry returns valid values for the specific data elements which the tool can use to perform semantic validation

IPDA Registry Scenario #3 Available Resources Show list of valid missions and/or instruments – A web-based query tool requests a list of mission names from across the IPDA as follows Connects to the IPDA Service Registry to request information regarding the resource registry that manages the information Connects to the IPDA Resource Registry and requests information regarding mission names using the PDAP protocol – Displays the mission names in the browser

Registry Standards/Interfaces and their Mappings to IPDA Proposed Classes Standards Interfaces & Reference Models Data Registry Resource Registry Service Registry Metadata Registry ebXML (Reference Model) XXXX UDDIX ISO/IEC (Ref Model) X IPDA PDAP (APIs)XXXX NOTE: ebXML provides a nice reference model, but not specification for Interfaces or protocols.

Recommendations Front-end all registries with a REST- based/PDAP-style interface Initially, a service registry can be very simple Provide online access to data dictionary information Share mission, instrument and target databases

Next Steps Produce White Paper Select appropriate standards Define an implementation Plan – Define granular interfaces, etc

Backup

Registry Queries (1) a returns the XML label of the uniquely identified registered object from any of the federated registries (default - XML file) b. &selector=data_object -- returns the identified registered object from any of the federated registries (default - zip file?) c. &selector=data_object&package=zip -- returns the identified registered object from any of the federated registries as a zip file d. &selector_attribute=all -- returns the attribute names of the uniquely identified registered object from any of the federated registries (xml file) e. &selector_attribute_value=product_type -- returns the value of the attribute product_type of the uniquely identified registered object

Registry Queries (2) f. &package=VOTABLE -- returns the XML label of the identified registered object as a VOTABLE g. &registry_puid= -- returns the XML label of the identified registered object from the identified registry (registry puid obtained from service registry) h. &selector=latest -- returns the XML label of the latest (default) version of the logically identified registered object i. &selector=all – returns the XML labels of all of the versions of the logically registered object (xml file) j. -- returns the XML labels of all products of the specified product_type (latest versions default as XML file)

Registry Queries (3) k. &selector_max_return= returns the XML labels of the latest versions of the first 100 products of the specified product_type l returns the XML label of the registry controlled uniquely identified registered object from any of the federated registries m. &product_typ e= -- returns the XML labels of all products satisfying the constraints (latest versions and XML files)