The NASA Earth Science Data and Information System (ESDIS) is migrating documentation for their data and products towards International Standards developed by ISO Technical Committee 211 (ISO/TC211). In order to do this effectively, NASA must understand and participate in the ISO process. This presentation was given at a NASA ISO Seminar during November 2012. It outlines the ISO standards process and describes some extensions to the ISO standards that are being proposed to address ESDIS requirements not addressed in the original standard.

1. ESDIS and International Standards
Ted Habermann, NASA ISO Metadata Workshop
November, 2012

2. ISO Process
Preliminary
Proposal
Draft New
Work Item
Proposal
0-6 months
New Work
Item
Proposal
Working
Draft
or PAS
Committee
6 months
Enquiry
Approval
5 months
? months
Preparatory
2 months
12 months
Technical
Consensus
(DIS)
9 months
Final Draft
International
Standard
(FDIS)
Publication
3 months
International
Standard
(IS)

3. ISO Project Options
Stage
Proposal
Preparatory
Committee
Enquiry
Approval
Publication
Normal
Procedure
Acceptance
of Proposal
Preparation
of working
draft
Develop and
accept
committee
draft
Develop and
accept
enquiry draft
Approval of
FDIS
Publication
of
International
Standard
Draft With
Proposal
Acceptance
of Proposal
Study by
Working
Group
Develop and
accept
committee
draft
Develop and
accept
enquiry draft
Approval of
FDIS
Publication
of
International
Standard
Fast
Track
Acceptance
of Proposal
Accept
enquiry draft
Approval of
FDIS
Publication
of
International
Standard
Technical
Specification
Acceptance
of Proposal
Technical
Report
Publically
Available
Specification
Acceptance
of Proposal
Approve
draft PAS
Accept Draft
Publication
of Technical
Specification
Accept Draft
Prepare Draft
Publication
of Technical
Report
Publication
of PAS

4. ISO Timeline
3 years
P
C
E
A
P
P
Implementation
*
C
E
A
P
6-8 years
*
19115-1 (Metadata Conceptual Model: IS 2013/06)
19115-3 (Metadata Schema, Transform, Schematron: IS 2015/05)
19115-2 (Metadata Acquisition / Images Conceptual Model)
*
3 years
3-5 years
*
*
*
19139-2 (Metadata Acquisition / Images Schema: TS 2012/10)
19157 (Data Quality Conceptual Model: IS 2013/04)
19157 (Data Quality Schema)
*
TS 19130 Parts 1-2 (Imagery Sensor Models for Geopositioning
Conceptual Model: TS 2012/12)

5. Conceptual Models and Implementations
Model
Delay
Schema
19115
2003-05
3.3 Years
19139
2006-08
19115-2
2009-02
3.6 Years
19139-2
2012-10
19115-1
2013-06
1.9 Years
19115-3
2015-05
5.8 Years
~50% Decrease
19157
2013-04
?
19157-2
?
19130
2012-12
?
?
?
Now creating XML schemas directly from UML models using software developed in OGC
Testbed. This capability is also being added directly into the tool by the vendor.
Test schemas for 19115-1 and 19157 with proposed NASA extensions are available now.

6. Conventions and Extensions
P
C
E
Implementation
A
P
P
C
E
Conventions and Extensions
Conventions are agreements that ensure consistent usage of the standard and
facilitate interoperability across communities. They are expressed as guidance and
best practices for the community.
Requirements not considered during the development of the original standard or
that emerge during the implementation period can be addressed using extensions to
the standard.
These extensions should be considered as candidate changes when the standard is
revised every five years.
Developing NASA conventions and extensions:
1) makes it possible to use the standard now and
2) increases the chances of addressing NASA needs in the next version of the
standard.
A
P

7. NASA Documentation Requirements
Users
NASA Documentation
Requirements
GCMD
ECHO
DAACs/ECS
Missions
Science Teams
ISO Standards

8. (Some) Existing Documentation Requirements
More than 2600 Collections have
been described using the ECHO
metadata dialect.
Almost 6000 DIFs include the
word NASA.

9. ECHO Dialect
~150 Elements with content. Keywords, identifiers, and contact information are the most
commonly occurring fields.
324 AdditionalAttributes occur over 3000 times
Most Common: PROCESSVERSION QAPERCENTGOODQUALITY QAPERCENTOTHERQUALITY
QAPERCENTNOTPRODUCEDCLOUD QAPERCENTNOTPRODUCEDOTHER

10. DIF Dialect
~130 elements with content. Keywords, identifiers, and contact information are the
most commonly occurring fields.
99% translation to ISO, ~79% translation to ECHO

11. More Overlap Than Difference
The metadata dialects currently used
by ESDIS have much more overlap than
difference.
The mappings are generally well
understood: we are in a tweaking
stage.
ECHO
DIF
The translations can be implemented
using well-known, standard tools that
are designed for XML processing.
These are different from the
programming languages generally used
for scientific data processing.
ISO

12. Additional Attributes
The ECHO AdditionalAttributes are an undifferentiated pile of information.
They can be translated to ISO, but we need to know where to put them. In order to do
that, we need to identify their types.

13. AdditionalAttributes and ISO
Many of the AdditionalAttributes fit into
standard ISO elements.
Others are implementation specific elements of
existing ISO types.
Rules:
Percent/Pct > contentInformation
Quality > qualityInformation
Gain/Bias > instrumentInformation
75% of the attributes, 81% of content
citation.date
citation.identifier
citation.pointOfContact
contentInformation
descriptiveKeywords
distributionInformation
extent
geographicIdentifier
instrumentInformation
lineage
processingInformation
qualityInformation

14. RecordType/Record - ISO with XML Reference
RecordType
<eos:otherPropertyType>
<gco:RecordType xlink:href="http://www.echo.nasa.gov/ingest/schemas/operations/Collection.xsd#
xpointer(//element[@name='AdditionalAttribute'])">Echo Additional Attribute</gco:RecordType>
</eos:otherPropertyType>
<eos:otherProperty>
<gco:Record xmlns:echo="http://www.echo.nasa.gov/ingest/schemas/operations">
<echo:AdditionalAttribute>
<echo:Name>ScanAngle</echo:Name>
<echo:DataType>float</echo:DataType>
<echo:Description>The angle between the sensor view vector and the nadir axis</echo:Description>
<echo:MeasurementResolution/>
<echo:ParameterRangeBegin/>
<echo:ParameterRangeEnd/>
<echo:ParameterUnitsOfMeasure>degrees</echo:ParameterUnitsOfMeasure>
<echo:ParameterValueAccuracy/>
<echo:ValueAccuracyExplanation/>
<echo:Value>47.5</echo:Value>
</echo:AdditionalAttribute>
</gco:Record>
</eos:otherProperty>
Record

15. MD_Metadata
MI_Plan
MI_Platform
+ citation[0..*] : CI_Citation
+ identifier : MD_Identifier
+ description[0..1] : CharacterString
+ sponsor[0..*]: CI_ResponsibleParty
+ type[0..1] : MI_GeometryTypeCode
+ status : MD_ProgressCode
+ citation[0..*] : CI_Citation
+ platform 0..*
+ acquisitionPlan 0..*
+ mountedOn 0..1
MI_AcquisitionInformation
+ instrument 0..*
+ environmentalConditions
0..*
MI_Instrument
+ citation[0..*] : CI_Citation
+ identifier : MD_Identifier
+ type : CharacterString
+ description[0..1] : CharacterString
+ operation
0..*
MI_EnvironmentalRecord
MI_Operation
+ averageAirTemperature : Real
+ maxRelativeHumidity : Real
+ maxAltitude : Real
+ meteorologicalConditions : CharacterString
+ objective
0..*
+ description[0..1] : CharacterString
+ citation[0..1] : CI_Citation
+ identifier : MD_Identifier
+ status : MD_ProgressCode
+ type[0..1] : MI_OperationTypeCode0
+ requirement
0..*
MI_Objective
+ identifier[1..*] : MD_Identifier
+ priority[0..1] : CharacterString
+ type[0..*] : MI_ObjectiveTypeCode
+ function[0..*] : CharacterString
+ extent[0..*] : EX_Extent
gmi:MI_AcquisitionInformation
MI_Requirement
+ citation[0..1] : CI_Citation
+ identifier : MD_Identifier
+ requestor[1..*] : CI_ResponsibleParty
+ recipient[1..*] : CI_ResponsibleParty
+ priority : MI_PriorityCode
+ requestedDate : MI_RequestedDate
+ expiryDate : DateTime

16. MD_Metadata
MI_Plan
MI_Platform
+ citation[0..*] : CI_Citation
+ identifier : MD_Identifier
+ description[0..1] : CharacterString
+ sponsor[0..*]: CI_ResponsibleParty
+ otherPropertyType [0..1]: RecordType
+ otherProperty [0..1]: Record
+ type[0..1] : MI_GeometryTypeCode
+ status : MD_ProgressCode
+ citation[0..*] : CI_Citation
+ platform 0..*
+ acquisitionPlan 0..*
+ mountedOn 0..1
MI_AcquisitionInformation
+ instrument 0..*
+ environmentalConditions
0..*
MI_Instrument
+ citation[0..*] : CI_Citation
+ identifier : MD_Identifier
+ type : CharacterString
+ description[0..1] : CharacterString
+ otherPropertyType [0..1]: RecordType
+ otherProperty [0..1]: Record
+ mountedOn
0..1
+ operation
0..*
MI_EnvironmentalRecord
MI_Operation
+ averageAirTemperature : Real
+ maxRelativeHumidity : Real
+ maxAltitude : Real
+ meteorologicalConditions : CharacterString
+ description[0..1] : CharacterString
+ citation[0..1] : CI_Citation
+ identifier : MD_Identifier
+ status : MD_ProgressCode
+ type[0..1] : MI_OperationTypeCode0
+ sensor 0..*
MI_Sensor
+ citation[0..*] : CI_Citation
+ identifier : MD_Identifier
+ type : CharacterString
+ description[0..1] : CharacterString
+ otherPropertyType [0..1]: RecordType
+ otherProperty [0..1]: Record
+ objective
0..*
+ requirement
0..*
MI_Objective
+ identifier[1..*] : MD_Identifier
+ priority[0..1] : CharacterString
+ type[0..*] : MI_ObjectiveTypeCode
+ function[0..*] : CharacterString
+ extent[0..*] : EX_Extent
eos:MI_AcquisitionInformation
MI_Requirement
+ citation[0..1] : CI_Citation
+ identifier : MD_Identifier
+ requestor[1..*] : CI_ResponsibleParty
+ recipient[1..*] : CI_ResponsibleParty
+ priority : MI_PriorityCode
+ requestedDate : MI_RequestedDate
+ expiryDate : DateTime

17. If(count(source) + count(processStep) =0) and
(DQ_DataQuality.cope.level = 'dataset' or 'series')
then statement is mandatory
MD_Metadata
DQ_DataQuality
+ scope : DQ_Scope
LI_Lineage
+ lineage 0..1
+ statement [0..1] : CharacterString
+ source 0..*
+ processStep 0..*
LE_Source
+ description [0..1] : CharacterString
+ scaleDenominator [0..1] : MD_RepresentativeFraction
+ sourceReferenceSystem [0..1] : MD_ReferenceSystem
+ sourceCitation [0..1] : CI_Citation
+ sourceExtent [0..*] : EX_Extent
+ processedLevel[0..1] : MD_Identifier
+ resolution[0..1] : LE_NominalResolution
LE_ProcessStep
+ sourceStep
0..*
+ output, source
0..*
+ processingInformation
0..*
+ report 0..*
LE_ProcessStepReport
+ name : CharacterString
+ description[0..1] : CharacterString
+ fileType[0..1] : CharacterString
+ algorithm 0..*
LE_Algorithm
+ citation: CI_Citation
+ description : CharacterString
gmi:DQ_Lineage
+ description : CharacterString
+ rationale [0..1] : CharacterString
+ dateTime [0..1] : DateTime
+ processor [0..*] : CI_ResponsibleParty
LE_Processing
+ identifier : MD_Identifier
+ softwareReference[0..*] : CI_Citation
+ procedureDescription[0..1] : CharacterString
+ documentation[0..*] : CI_Citation
+ runTimeParameters[0..1] : CharacterString

18. If(count(source) + count(processStep) =0) and
(DQ_DataQuality.cope.level = 'dataset' or 'series')
then statement is mandatory
MD_Metadata
DQ_DataQuality
+ scope : DQ_Scope
LI_Lineage
+ lineage 0..1
+ statement [0..1] : CharacterString
+ source 0..*
+ processStep 0..*
LE_Source
+ description [0..1] : CharacterString
+ scaleDenominator [0..1] : MD_RepresentativeFraction
+ sourceReferenceSystem [0..1] : MD_ReferenceSystem
+ sourceCitation [0..1] : CI_Citation
+ sourceExtent [0..*] : EX_Extent
+ processedLevel[0..1] : MD_Identifier
+ resolution[0..1] : LE_NominalResolution
LE_ProcessStep
+ sourceStep
0..*
+ output, source
0..*
+ processingInformation
0..*
+ report 0..*
LE_ProcessStepReport
+ name : CharacterString
+ description[0..1] : CharacterString
+ fileType[0..1] : CharacterString
+ algorithm 0..*
LE_Algorithm
+ citation: CI_Citation
+ description : CharacterString
+ additionalCitation: CI_Citation
+ version: CharacterString
eos:DQ_Lineage
+ description : CharacterString
+ rationale [0..1] : CharacterString
+ dateTime [0..1] : DateTime
+ processor [0..*] : CI_ResponsibleParty
LE_Processing
+ identifier : MD_Identifier
+ softwareReference[0..*] : CI_Citation
+ procedureDescription[0..1] : CharacterString
+ documentation[0..*] : CI_Citation
+ runTimeParameters[0..1] : CharacterString
+ otherPropertyType [0..1]: RecordType
+ otherProperty [0..1]: Record

19. Granules/HDF
Semantic Mashups
User Input
Identifiers
GIS
Services
Users
NASA Documentation
Requirements
GCMD
ECHO
DAACs/ECS
Missions
Science Teams
ISO Standards
Preservation Objects
Data Quality
Lineage / PROV

20. Questions?
thabermann@hdfgroup.org