- Metadata
- Provide metadata
- Provide descriptive metadata
- Provide structural metadata
- Data Licenses
- Provide data license information
- Data Provenance
- Provide data provenance information
- Data Quality
- Provide data quality information
- Data Versioning
- Provide a version indicator
- Provide version history
- Data Identifiers
- Use persistent URIs as identifiers of datasets
- Use persistent URIs as identifiers within datasets
- Assign URIs to dataset versions and series
- Data Formats
- Use machine-readable standardized data formats
- Use locale-neutral data representations
- Provide data in multiple formats
- Data Vocabularies
- Reuse vocabularies, preferably standardized ones
- Choose the right formalization level
- Data Access
- Provide bulk download
- Provide Subsets for Large Datasets
- Use content negotiation for serving data available in multiple formats
- Provide real-time access
- Provide data up to date
- Provide an explanation for data that is not available
- Make data available through an API
- Use Web Standards as the foundation of APIs
- Provide complete documentation for your API
- Avoid Breaking Changes to Your API
- Data Preservation
- Preserve identifiers
- Assess dataset coverage
- Feedback
- Gather feedback from data consumers
- Make feedback available
- Data Enrichment
- Enrich data by generating new data
- Provide Complementary Presentations
- Republication
- Provide Feedback to the Original Publisher
- Follow Licensing Terms
- Cite the Original Publication
Created
February 20, 2017 09:31
-
-
Save othree/77d7f3baa7ddb63d8ac07ea8e6db611b to your computer and use it in GitHub Desktop.
Data on the Web Best Practices
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment