The SEEDS (Strategic Evolution of ESE Data Systems) process is a strategy for maximizing the utility of Earth science data within NASA. It involves formulating best practices for data systems through a study of past and present systems. The SEEDS process engages data providers and users to incorporate lessons learned. It focuses on adopting common standards to increase flexibility rather than developing new systems. The document outlines the status of the SEEDS formulation studies, including the standards process study which recommends adopting the IETF process for approving and developing interoperability standards. It notes that standards working groups will be established to evaluate existing standards like HDF for adoption.

1. SEEDS Standards Process
Richard Ullman
SEEDS Standards Formulation Team Lead
Richard.E.Ullman@nasa.gov
05 December, 2002
HDF & HDF-EOS Workshop VI
1

2. SEEDS
• The Strategic Evolution of ESE Data Systems is:
– A strategy for ESE to maximize the science and applications utility
of ESE data.
– A formulation study of best practices in ESE data systems.
– A process for incorporating lessons learned from past and present
ESE data systems into new data system implementations.
– A tool for engaging communities of ESE data providers and users
in the SEEDS strategy.
– NOT a data system development or implementation project or
program - a strategy that applies to implementing organizations.
05 December, 2002
HDF & HDF-EOS Workshop VI
2

3. SEEDS Formulation Status
• Seven formulation study areas
–
–
–
–
–
–
–
Cost Estimation
Data Lifecycle
Reference Architecture and Reuse
Metrics
Technology Infusion
Standards Processes
Near Term Missions Standards
• Schedule
– SEEDS Formulation team has developed an integrated
Formulation Report and is presently working through GSFC, HQ,
and external review process prior to release.
– Third SEEDS Public Workshop - March 19-21, 2003 Annapolis
05 December, 2002
HDF & HDF-EOS Workshop VI
3

4. SEEDS Standards Premise
• "An important premise underlying [SEEDS] is that its
various parts should have considerable freedom in the
ways in which they implement their functions and
capabilities. Implementation will not be centrally
developed, nor will the pieces developed be centrally
managed. However, every part of [the ESE network]
should be configured in such a way that data and
information can be readily transferred to any other. This
will be achieved primarily through the adoption of
common interface standards and practices.” [SEEDS preformulation document]
• Standards are what make increased flexibility for SEEDS
participants possible.
05 December, 2002
HDF & HDF-EOS Workshop VI
4

5. Simplified Data Flow Diagram
Key
Satellite
Instruments
Science or Applications Data
Center
Internal data flow
L0 or spacecraft data
Distribution flow
Ground
Receiving
Station
L0 Processing
Standard Data
Processing
Near Term
Archive
PI-managed, Mission, Theme
Based or Multi-mission Data
Center
U
S
E
R
S
System interchange
Backbone Data Center or Long Term Archive
05 December, 2002
HDF & HDF-EOS Workshop VI
5

6. SEEDS Standards Process
• Standards Process Study has made recommendations to the
SEEDS formulation
– For approving and developing standards for the ESE network of
data systems and services throughout the SEEDS era.
– Types of standards to be addressed by these processes:
•
•
•
•
•
•
•
Distributed information search protocols (e.g., EOSDIS V0, Z39.50)
Data interface standards (e.g, OGC Web Map Services, DODS)
Data distribution packaging standards (e.g., HDF/HDF-EOS)
Data interchange packaging standards (e.g., HDF/HDF-EOS)
Metadata and documentation standards (e.g., GCMD DIF, ESML)
Service documentation standards (e.g., GCMD SERF)
Service communication protocols (e.g., UDDI, WSDL, SOAP)
05 December, 2002
HDF & HDF-EOS Workshop VI
6

7. SEEDS Standards Process
• Recommended process should have elements similar to the
IEFT process
• Preference should be given to adoption over development
• Standards should have demonstrated implementation
relevant to ESE.
• Process should be guided by a “Standards Working Group”
– Members to be drawn from NASA ESE funded activities
• Awardees of the REASoN CAN
• Representatives of NASA ESE mission science and project teams
• ESE Applications Office representation
05 December, 2002
HDF & HDF-EOS Workshop VI
7

8. International
& Interagency
Agreement
HQ Mandate
Science and
Applications
Project
Needs
Vendor
Offerings
Existing
Standards
Adopt or Develop ?
Requirements, needs, constraints come from
various places inside and outside of ESE
•These can be met either by adopting an
already existing specification or by
developing a specification.
•Adopting an existing specification is
preferred to developing a new one.
Adopt
Develop
Candidate
Standards
Revision
Requirements
Revision
Review
Profile
Extend
Existing
Standard
Existing
Standard
Existing
Standard
Testbed/
Spec
Initial
Draft Standards
Choose process
based on
interface
characteristics
Review
Inter-project
Collaboration
RFP/Proposal/
Contract
Approve
Major Revision
Initial
Draft Standards
RFCs
Working
Implementations
Initial
Review
Proposed
Standards
2 Working
Implementations &
Operational experience
Promote to
Draft
Draft
Standards
Declare
Standard
ESE
05 December, 2002
Standards
Significant implementation &
Successful Operational Use
The approval process is based on the IETF process as
documented in RFC2026.
“The goals of the Standards Process are:
•technical excellence;
•prior implementation and testing;
•clear, concise, and easily understood documentation;
•openness and fairness; and
•timeliness.*”
* rfc2026, Section 1.2
HDF & HDF-EOS Workshop- VI
8

9. Standards Process Status
• SEEDS in FY’03 is in “transition” from formulation.
• Refinement of process recommendations and status of
concurrence by NASA management will be discussed at
next community workshop
– March 19-21 @ “Historic Inns of Annapolis”
• Standards Study Formulation Team is preparing for
initiation of Standards Working Group.
– Group may be initiated shortly after community workshop
– Initial focus will be organizational
– Hope to rapidly begin consideration of “ratifying” standards
already in wide use within ESE (such as HDF)
05 December, 2002
HDF & HDF-EOS Workshop VI
9

10. SEEDS Near-Term Study Findings
• Requirements for system interchange among ESE
components are different from requirements for
distribution to end-users.
– System interchange packaging standards must focus on interface
standardization, completeness, and correctness of transfer over
“ease of use”.
– The primary requirement for distribution to end-users is “ease of
use”.
• In the near-term, the chief mode of delivering data remains
the transfer of discrete files.
– Data format is the critical component of data packaging.
05 December, 2002
HDF & HDF-EOS Workshop VI
10

11. SEEDS Near-Term Study Findings
• The use of a general standard is insufficient for
interoperability.
– A common “profile” of the standard is required.
– “profile” is a convention for use of a standard within a user
community.
– “Community-based” standards and profiles of standards, are
preferable
• Evolution of standards for mission science data over the
lifetime of the mission and beyond is inevitable. These
include standards for:
–
–
–
–
Data formats.
Catalog interfaces.
Associated metadata content and format.
Documentation standards
05 December, 2002
HDF & HDF-EOS Workshop VI
11

12. More SEEDS Information
•
Get reports here:
http://eos.nasa.gov/seeds
05 December, 2002
HDF & HDF-EOS Workshop VI
12