1 ccsds information architecture working group daniel j. crichton, chair nasa/jpl 14 september 2005
TRANSCRIPT
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
Technical Green Book – Reference Architecture for Space Information Management CCSDS 312.0-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
Ontology developed based on white book. Captured in Protégé.
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
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
5
Chapter 1: Overview
Define both the information view and functional the functional view for managing information across the space domain end-to-end.
Focus on “Application Information Objects”
Middleware and Messaging
Comm Layer
Metamodel
Information Components
ApplicationInformation
Object
Domain Model
Metamodel
Information Components
ApplicationInformation
Object
Domain Model
Middleware and Messaging
Comm LayerCommon Protocols - TCPIP, ...
Common Messaging - SOAP, JMS, ...
Common Functions - Registry, Repository, ...
Common or Mediated Metamodel - DEDSL, ISO1179, UML
Common or Mediated Domain Models --Planetary Data Systems, EOSDIS, ...
Information Exchange - Science, Mission, etc, Data Products, Observations, SLE Objects, ...
Communications
Software/Application
Data Architecture/ Content
6
Chapter 2: Information Objects
Refocus on Information Objects to Application Information Objects
Update AIO relationship to domain and meta models
Identify relationship to OAIS
Application Information Object
(AIO)
Data Object
Metadata Object
described by
Metamodels
Domain Models
DataDictionary
Schema/Ontology
prescribed by
instance of
prescribed by
7
Chapter 2: OAIS Mapping
8
Chapter 2: OAIS to IA Mapping
Data Object Metadata Object
9
Chapter 2: Identify AIO as a simple model
Metadata ObjectData Object
Application Information
Object
Has a Has a
describes
10
Chapter 2: Other IO Concepts and Changes
Cardinality (2.2.1) Conceptually we identify as
one-to-one In practice, it is many-to-many
Taxonomy/Classification of AIOs Primitive
Bound by a simple set of attributes
Simple Bound by a domain set of
attributes
Package Aggregate set of IOs Relationship to XFDU
Data Metadata
[0101011110..] NameTypeDate….
Primitive Application Information Object
11
Chapter 2: Modeling Concepts
M3
M2
M1
M0
ISO11179 UML model
MOF( Meta- Oject Facility)
Domainmodel
DataDictionary
MODELS
XMLSchema
M3
M2
M1
M0
ISO11179 UML model
MOF( Meta- Oject Facility)
Domainmodel
Application Information
Object
DataDictionary
MODELS
XMLSchema
OMG - Hierarchy of Models
12
Chapter 2: Meta Models
ISO/IEC 11179
DEDSL
XFDU
13
Chapter 2: Space Domain Models
Planetary Science Model (NASA)
Space Physics Archive and Search Environment (Intl)
EOSDIS (NASA)
EOS Core Model (NASA)
Others?
14
Chapter 2: Data Description Languages
PVL/ODL
EAST
XML
15
Chapter 2: Interoperability
Classification Category
Normative Constructs
Normative Abstracted Structure (Metaphor)
Structuring Rules
Meta Model
Domain A Data Model
Domain BData Model
Interchange ModelModel Element Mappings
Prescribes Prescribes Prescribes
Domain A Domain B
Describes
DescribesDescribes
Something to be interchanged
16
Chapter 3: Introduction
Primitive Functional Objects
Functional Information Management Objects
17
Chapter 3: Primitive Information Objects
Functions: Get, Put
Objects: Data Store and Query Object
Put Operation
Data Store Object
H1
H2
.
.
.HN
D1
D2
.
.
.DN
Local Identifier
DO
DO
Data Store
LegendInformation
Management Object
Operation
Data Store Subcomponent
Dataflow
LocalIdentifier
Get Operation
Data Store Object
H1
H2
.
.
.HN
D1
D2
.
.
.DN
Local Identifier
DO
Local Identifier
Data Store
LegendInformation
Management Object
Operation
Data Store Subcomponent
Dataflow
DO
18
Chapter 3: Primitive Information Objects (Interfaces)
find(expression)
get(identifier)
put(identifier)
<<Component>>
Query Object
<<Component>>
Physical Data Storage (or DSO)
1
1
<<Interface>>
Query
+find(expression):DOs
Has a
<<Component>>
Data StoreObject
<<Component>>
Physical Data Storage
1
1Has a
<<Interface>>
Data Store
+get(local identifier):DO+put(DO):local identifier
19
Chapter 3: Functional Objects
Repository Service Objects Provide common components for management of information objects.
Provides for short-term and long-term management.
Registry Service Objects Provide common components for management/discovery of metadata
Product Service Objects Provides specialization for access, transformation of information objects
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
Extension of a data store
Functional Interfaces Get(identifier)
Put(AIO)<<Component>>
Repository Service Object
<<Component>>
Data Store Object
1
1
<<Interface>>
Repository Request
+get(identifier): AIO+put(AIO):identifier
21
Chapter 3: Repository Functional Object Classes
Repository Object Type Object Properties Object Description
Data Store Primitive 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 Archive Component 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 Archive Stores 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
Functional Interfaces Query(expression)
<<Component>>
Registry Service Object
1
1
<<Component>>
Query Object
<<Component>>
Data StoreObject
1
1
Has a
Has
a
<<Interface>>
Metadata Query
+query(expression):metadata object
23
Chapter 3: Registry Functional Object Classes
Registry Type Return Object Types Query Interface Parameters
Metadata Registry Data Dictionaries, Data Elements Query for Data Element properties, or Data Element IDs, or Data Dictionary IDs
Service Registry Service Endpoints, Service Metadata (interface properties, interface type, return schema)
Query for Service properties
Resource Registry Data Products, Resource Registry Locations
Data Resource properties
24
Chapter 3: Query Service Object
<<Component>>
Query Service Object
1
1
<<Component>>
Query Object
1
*
Co
mm
un
icate
s W
ith<<Component>>
Domain Processing Object
1
1
<<Component>>
Registry Service Object
1
*
<<Component>>
Repository Service Object
<<Interface>>
Query Service
+query(expression):IOs
Has a
Provides interfaces to various objects for Registry access/discovery
Repository access/retrieval
Retrieval of sets
Domain processing
Interface: query(expression)
25
Chapter 3: Product Service Object
Effectively a complex object built on repository and query objects to provide Transformation
Packaging/Aggregation
Interface: query(expression) <<Component>>
Product Service Object
1
1
<<Component>>
Query Object
<<Component>>
Repository Service Object
1
1
Has a
<<Component>>
Domain Processing Object
1
1
Uses
Use
s
<<Interface>>
Product Service
+query(expression):IO
26
Chapter 3: Archive Service Object
Effectively a complex object built on repository and registry objects to provide Ingestion
Interface: ingestPackage(IO), retrievePackage(identifier)
<<Component>>
Archive Service Object
1
1
<<Component>>
IngestService Object
<<Component>>
Repository Service Object
1
1
Uses
Uses
<<Component>>
Registry Service Object
1
1
Has A
<<Interface>>
Archive Service
+ingestPackage(IO):Identifier+retrievePackage(Identifier):IO
27
Chapter 4: IA Views
Information – Effectively our chapter 2
Functional – Effectively our chapter 3
28
Chapter 5: Space Data Systems
Related projects
Project Information Architecture Concepts Used
OAIS information objects, information packages archive service object
SPACEGRID information objects, registry service object
EOSDIS Meta models, domain models, metadata objects, information objects
European Data Grid information objects, information packages, archive service object, registry service object
National Virtual Observatory information objects, information packages, archive service object, registry service object
29
Chapter 6: Annex on CCSDS related standards
Information Architecture Concept CCSDS Standard
Meta Model Specification (Section 2) DEDSL (Data Entity Dictionary Specification Language) http://www.ccsds.org/documents/647x1b1.pdf
Archive Ingestion Model (Section 3) Reference Model for an Open Archival Information System (OAIS) http://www.ccsds.org/documents/650x0b1.pdf
Data Element Semantics and Specification (Section 2)
The Data Description Language EAST Specification (CCSD0010). Blue Book. Issue 2. November 2000. http://www.ccsds.org/documents/644x0b2.pdf
Specification of Application Information Object Format (Section 2)
Information Interchange Specification http://www.ccsds.org/documents/642x1g1.pdf
Data Value Representation (Section 2) Parameter Value Language Specification (CCSD0006 and CCSD0008). Blue Book. Issue 2. June 2000. http://www.ccsds.org/documents/641x0b2.pdf
Packaging Specification (Section 2) XML Formatted Data Unit (XFDU) Structure and Construction Rules. White Book, Issue 2, September 2004.http://www.ccsdsrg/docu/dscgi/ds.py/Get/File-1912/IPRWBv2a.doc
Data Object Format Specification (Section 2) Standard Formatted Data Units — Control Authority Data Structures. Blue Book. Issue 1. November 1994. http://www.ccsds.org/documents/632x0b1.pdf
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:30 Exploration/C3I usage of XML Bob Bradford
4:30-5:00 CCSDS SLE usage of XML Erik Barkley
5:00-5:30 CCSDS IPR/IA Registry Repository Study Dan Crichton/Lou Reich
5:30-600 Action items/planning for Toulouse meeting
33
Goals of the TIM
Understand how various efforts are implementing or planning to implement XML-based services
Identify similarities, differences
Identify the NASA interest in working together to define a common set of XML-based services
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
Area Description Date
IAWG Hold SEA IAWG Meeting April 2005
IPR/IAWG Hold Joint Meeting on Registries with IPR
April 2005
IPR/IAWG IPR/IA Technical Interchange Meeting + XML Planning
August 2005
IAWG Publish current whitebook as a technical document for CCSDS (green book)
September 2005
IPR/IAWG Discuss registry-based services and thrust between IA and IPR
December 2005