Recommended Formats Statement

1. Platform-independent, character-based formats are preferred over native or binary formats as long as data is complete, and retains full detail and precision. Preferred formats include well-developed, widely adopted, de facto marketplace standards, e.g.
1. Formats using well known schemas with public validation tool available
2. Line-oriented, e.g. TSV, CSV, fixed-width
3. Platform-independent open formats, e.g. .db, .db3, .sqlite, .sqlite3
2. Any proprietary format that is a de facto standard for a profession or supported by multiple tools (e.g. Excel .xls or .xlsx, Shapefile)


3. Character Encoding, in descending order of preference:
   1. UTF-8, UTF-16 (with BOM),
   2. US-ASCII or ISO 8859-1
   3. Other named encoding

For data (in order of preference):

1. Non-proprietary, publicly documented formats endorsed as standards by a professional community or government agency, e.g. CDF, HDF
2. Text-based data formats with available schema

For aggregation or transfer:

1. ZIP, RAR, tar, 7z with no encryption, password or other protection mechanisms.

Consult the appropriate sections of this document to identify the preferred formats for supplementary material

1. Public download URLs
2. Automated private download URLS with any necessary API keys or credentials
3. Hard drive; CD-ROM; DVD-ROM

1. Deposits should include all applicable metadata, data dictionaries, XML schemas, and technical specifications as appropriate. Discipline-specific metadata standards should be used whenever possible
2. As supported by format:
1. Title
2. Creator
3. Creation date
4. Place of publication
5. Publisher/producer/distributor
6. Contact information
7. A list of software used to produce, render or compress the data (if applicable)
8. Character encoding
3. Include if available:
1. Language of work
2. Other relevant identifiers (e.g., DOI, LCCN, canonical URL, etc.)
3. Subject descriptors
4. Abstracts
5. Key or reference to each data field
6. Checksums
7. Permanent version specifiers (e.g., date, version number, etc.)
8. Information about how the data was collected and any sampling or post-processing which as been applied
9. Known copyright terms, especially for datasets which combine data from multiple sources
4. For datasets serving as part of a database: proprietary database package and version
5. For aggregate files: manifest or file list of payload content 

• Files must contain no measures (such as digital rights management technologies or encryption) that control access to or prevent use of the digital work.
• Files in formats which support linking or embedding external resources (e.g. XML, JSON, Excel .xls or .xlsx) should be self-contained to remain useful in the event of external service changes.
• Files in formats which support executable code (e.g. Excel) do not contain executable code.

Files in formats which support executable code do not depend on embedded programs for purposes other than display (e.g. search, filtering, etc.); the raw data is available without executing code.

Complete set of the content contained within the database

1. Publisher web interface with:
1. Comprehensive and user-friendly search and discovery
2. Counter compliant usage statistics
2. Delivered preservation content

Documented API