FEP -
Format Use by a Project Data System - Form

Identification Information

Submitter's Name

Submitter's Affiliation

Submitter's Project (if appropriate)

Submitter's E-mail Address

Submitter's Phone Number

Acronym or Name of Project

Acronym or Name of Format

1. Format (Format System) Identification

State how the format is typically identified, e.g., Common Data Format, version 2.6. List all versions used. Examples include FITS, HDF, CDF, NETCDF, PDS Labels, IDFS, SFDU Labels, etc. If there are multiple formats involved in a formatting system, identify each and give their roles - e.g., ODL in PDS Labels.

2. Data Model Extensions by Project

Describe the extent to which the basic data model of the format has been Extended or specialized to meet the project's needs, and why. For example, Describe additional project required attributes and any new relationships they establish among elements of the format.

3. Original Format Selection Rationale

Describe the original rationale for selecting the format/format system for use by the project. Describe the extent to which it has been validated by experience.

4. Data Types

Identify the types of data you cast into the named format by processing level and type of object.

• Processing Level
  • Level 0 (Instrument output values)
  • Level 1A (Reversibly processed instrument outputs)
  • Level 1B (Non-reversibly processed instrument outputs)
  • Higher level physical parameter data
• Object Types
  • Images
  • Spectra
  • Time Series
  • Multi-variate distributions
  • Other

5. Support

Identify the types of support you have needed for this format. Identify who (person or organization) has provided the support.

6. Project Software

Identify the types of software created by the project for handling the format. Briefly describe its functionality.

7. Experience

Describe your experience with this format in terms of its strengths and weaknesses.

Relative to its ability to manage project-needed metadata
Relative to its related software
Relative to its user support infrastructure
Relative to the overall functionalities of the whole package (format and software)
Relative to the needs of the scientists you support (vs. project level u ses)

8. Desired Functions

What additional functionalities or characteristics would make the format more useful in your environment?

9. Selection Criteria

If you were to manage a new project today, what characteristics would you look for in a format and why?.

10. Handling Plans for Format Evolution

Describe plans for handling any format evolution, if any.

11. Other Comments