1 CCSDS Information Architecture Working Group Daniel J. Crichton, Chair NASA/JPL 14 September 2005

2 Agenda IAWG Agenda Date/Time: Wednesday, September 14, 2005 Chair: Dan Crichton Agenda 09:00 AM – 09:15 AM Agenda Review 09:15 AM – 12:00 PM Discussion on updates to IA document 12:00 PM - 01:30 PM Lunch 01:30 PM - 02:30 PM Discussion on IA/IPR NASA TIM 02:30 PM – 05:00 PM Next steps and planning for IAWG Charter review Reference implementations Formalization of interfaces Working with MOIMS Best practices Information Infrastructure Specification (E.g., Registries and Repositories)

3 Status of WG F Technical Green Book – Reference Architecture for Space Information Management CCSDS G-1 – September 2005 Version ä Incorporates updates resulting from NASA TIM between MOIMS/GSFC and SEA/JPL in August ä Major updates since Fall and Spring CCSDS Meetings ä Integrated CNES OMG MDA concepts ä Working to be consistent with OAIS F Ontology developed based on white book. Captured in Protégé. F Initial discussions between GSFC and JPL to look at jointly working together between IA and IPR to focus on registries efforts ä One day TIM at GSFC in August discussed XML-based services

4 IA Draft Green Book Review F Incorporates updates resulting from NASA TIM between MOIMS/GSFC and SEA/JPL in August F Major updates since Fall and Spring CCSDS Meetings F Integrated CNES OMG MDA concepts F Working to be consistent with OAIS

5 Chapter 1: Overview F Define both the information view and functional the functional view for managing information across the space domain end-to-end. F Focus on “Application Information Objects”

6 Chapter 2: Information Objects F Refocus on Information Objects to Application Information Objects F Update AIO relationship to domain and meta models F Identify relationship to OAIS

7 Chapter 2: OAIS Mapping

8 Chapter 2: OAIS to IA Mapping

9 Chapter 2: Identify AIO as a simple model

10 Chapter 2: Other IO Concepts and Changes F Cardinality(2.2.1) ä Conceptually we identify as one-to-one ä In practice, it is many-to-many F Taxonomy/Classification of AIOs ä Primitive F Bound by a simple set of attributes ä Simple F Bound by a domain set of attributes ä Package F Aggregate set of IOs F Relationship to XFDU

11 Chapter 2: Modeling Concepts

12 Chapter 2: Meta Models F ISO/IEC F DEDSL F XFDU

13 Chapter 2: Space Domain Models F Planetary Science Model (NASA) F Space Physics Archive and Search Environment (Intl) F EOSDIS (NASA) F EOS Core Model (NASA) F Others?

14 Chapter 2: Data Description Languages F PVL/ODL F EAST F XML

15 Chapter 2: Interoperability

16 Chapter 3: Introduction F Primitive Functional Objects F Functional Information Management Objects

17 Chapter 3: Primitive Information Objects F Functions: Get, Put F Objects: Data Store and Query Object

18 Chapter 3: Primitive Information Objects (Interfaces) F find(expression) F get(identifier) F put(identifier)

19 Chapter 3: Functional Objects F Repository Service Objects ä Provide common components for management of information objects. Provides for short-term and long-term management. F Registry Service Objects ä Provide common components for management/discovery of metadata F Product Service Objects ä Provides specialization for access, transformation of information objects F Query Service Objects ä Manages routing of queries in order to discover and locate the appropriate product service objects, as well as repository service objects

20 Chapter 3: Repository Object F Extension of a data store F Functional Interfaces ä Get(identifier) ä Put(AIO)

21 Chapter 3: Repository Functional Object Classes Repository Object TypeObject PropertiesObject Description Data StorePrimitive Component (e.g., DBMS, and File system) Basic Data Store component described in Section 3.1 sits behind Data Store Object and supports Repository Interface to get and put data (lower level data such as streams and bits) Operational ArchiveComponent that stores data products and higher level products, possibly including metadata. Supports retrieval of data products through possibly complex methods, and processing. No support for permanence. Stores products for short term (e.g. less than 10 years), and allows retrieval of products. Advanced Component supporting retrieval of possibly complex data products, including their metadata. Repository where writes are frequent and reads are frequent. Data products stored in this type of archive will be updated and versioned. Examples of products stored in this archive are command sequence products sent using spacecraft telemetry. Long-term ArchiveStores products for long term archiving, and supports basic archive functionality. Archive for long-term preservation of data products, and data permanence. Supports basic archive functional interfaces (e.g. get, put).

22 Chapter 3: Registry Objects F Functional Interfaces ä Query(expression)

23 Chapter 3: Registry Functional Object Classes Registry TypeReturn Object TypesQuery Interface Parameters Metadata RegistryData Dictionaries, Data ElementsQuery for Data Element properties, or Data Element IDs, or Data Dictionary IDs Service RegistryService Endpoints, Service Metadata (interface properties, interface type, return schema) Query for Service properties Resource RegistryData Products, Resource Registry Locations Data Resource properties

24 Chapter 3: Query Service Object F Provides interfaces to various objects for ä Registry access/discovery ä Repository access/retrieval ä Retrieval of sets ä Domain processing F Interface: query(expression)

25 Chapter 3: Product Service Object F Effectively a complex object built on repository and query objects to provide ä Transformation ä Packaging/Aggregation F Interface: query(expression)

26 Chapter 3: Archive Service Object F Effectively a complex object built on repository and registry objects to provide ä Ingestion F Interface: ingestPackage(IO), retrievePackage(identifier)

27 Chapter 4: IA Views F Information – Effectively our chapter 2 F Functional – Effectively our chapter 3

28 Chapter 5: Space Data Systems F Related projects ProjectInformation Architecture Concepts Used OAISinformation objects, information packages archive service object SPACEGRIDinformation objects, registry service object EOSDISMeta models, domain models, metadata objects, information objects European Data Gridinformation objects, information packages, archive service object, registry service object National Virtual Observatoryinformation objects, information packages, archive service object, registry service object

29 Chapter 6: Annex on CCSDS related standards Information Architecture ConceptCCSDS Standard Meta Model Specification (Section 2)DEDSL (Data Entity Dictionary Specification Language) Archive Ingestion Model (Section 3)Reference Model for an Open Archival Information System (OAIS) Data Element Semantics and Specification (Section 2) The Data Description Language EAST Specification (CCSD0010). Blue Book. Issue 2. November Specification of Application Information Object Format (Section 2) Information Interchange Specification Data Value Representation (Section 2)Parameter Value Language Specification (CCSD0006 and CCSD0008). Blue Book. Issue 2. June Packaging Specification (Section 2)XML Formatted Data Unit (XFDU) Structure and Construction Rules. White Book, Issue 2, September /IPRWBv2a.doc Data Object Format Specification (Section 2)Standard Formatted Data Units — Control Authority Data Structures. Blue Book. Issue 1. November

30 LUNCH

31 Agenda IAWG Agenda Date/Time: Wednesday, September 14, 2005 Chair: Dan Crichton Agenda 09:00 AM – 09:15 AM Agenda Review 09:15 AM – 12:00 PM Discussion on updates to IA document 12:00 PM - 01:30 PM Lunch 01:30 PM - 02:30 PM Discussion on IA/IPR NASA TIM 02:30 PM – 05:00 PM Next steps and planning for IAWG Charter review Reference implementations Formalization of interfaces Working with MOIMS Best practices Information Infrastructure Specification (E.g., Registries and Repositories)

32 NASA XML-based Services Meeting 2:00- 2:15 Overview of Goals of Session Dan Crichton 2:15-2:45 JPL work on XML enterprise services Dan Crichton/P Shames 2:45-3:15 GMSEC usage/rqmts for using XML Dan Smith or Representative 3:30-4:00 DSMS usage/rqmts for using XML T McVittie or Representative 4:00-4:30Exploration/C3I usage of XML Bob Bradford 4:30-5:00CCSDS SLE usage of XML Erik Barkley 5:00-5:30CCSDS IPR/IA Registry Repository Study Dan Crichton/Lou Reich 5:30-600Action items/planning for Toulouse meeting

33 Goals of the TIM F Understand how various efforts are implementing or planning to implement XML-based services F Identify similarities, differences F Identify the NASA interest in working together to define a common set of XML-based services F Discuss how this might work within CCSDS and then engage the international community

34 Agenda IAWG Agenda Date/Time: Wednesday, September 14, 2005 Chair: Dan Crichton Agenda 09:00 AM – 09:15 AM Agenda Review 09:15 AM – 12:00 PM Discussion on updates to IA document 12:00 PM - 01:30 PM Lunch 01:30 PM - 02:30 PM Discussion on IA/IPR NASA TIM 02:30 PM – 05:00 PM Next steps and planning for IAWG Charter review Reference implementations Formalization of interfaces Working with MOIMS Best practices Information Infrastructure Specification (E.g., Registries and Repositories)

35 FY05 Plan AreaDescriptionDate IAWGHold SEA IAWG MeetingApril 2005 IPR/IAWGHold Joint Meeting on Registries with IPR April 2005 IPR/IAWGIPR/IA Technical Interchange Meeting + XML Planning August 2005 IAWGPublish current whitebook as a technical document for CCSDS (green book) September 2005 IPR/IAWGDiscuss registry-based services and thrust between IA and IPR December 2005