This table contains all BPs and its respective "Example" and "Tests" status.
The Need review status suggests that there is an already written section, but it's, probably, non-deterministic, so it has to be rewritten and become deterministic.
The Target date points to the deadline when the status of both sections must be Done.
If you can, please, feel free to put yourself into the Member(s) assigned column in order to colaborate with the task of (re)write those BP sections.
Feel free to change the status when it's necessary and make changes in this file.
|Best Practice||Example section status||Test section status||Member(s) assigned||Target date|
|BP 1: Provide metadata||Done||Done||Bernadette||February 19|
|BP 2: Provide descriptive metadata||Done||Done||Bernadette||February 19|
|BP 3: Provide locale parameters metadata||Done||Done||Bernadette||February 19|
|BP 4: Provide structural metadata||Done||Done||Bernadette, Newton||February 19|
|BP 5: Provide data license information||Done||Done||Newton, Phil||February 19|
|BP 6: Provide data provenance information||Incomplete||Need review||Deirdre Lee||February 19|
|BP 7: Provide data quality information||Done||Done||Riccardo, Antoine||February 19|
|BP 8: Provide versioning information||Done||Done||Annette||February 19|
|BP 9: Provide version history||Done||Done||Annette||February 19|
|BP 10: Avoid Breaking Changes to Your API, Communicate Changes to Developers||Need review||Need review||Annette, Yaso||February 19|
|BP 11: Use persistent URIs as identifiers of datasets||Done||Done||Phil||February 19|
|BP 12: Use persistent URIs as identifiers within datasets||Done||Need review||Phil||February 19|
|BP 13: Assign URIs to dataset versions and series||Done||Need review||Phil||February 19|
|BP 14: Use machine-readable standardized data formats||Done||Need review||Newton, Laufer||February 19|
|BP 15: Provide data in multiple formats||Done||Incomplete||Newton, Laufer||February 19|
|BP 16: Use standardized terms||Done||Need review||Antoine||February 19|
|BP 17: Reuse vocabularies||Done||Done||Antoine||February 19|
|BP 18: Choose the right formalization level||Done||Done||Antoine||February 19|
|BP 19: Provide data unavailability reference||Done||Need review||Bernadette, Eric Stephan||February 19|
|BP 20: Provide bulk download||Need to be done||Incomplete||Eric Stephan||February 19|
|BP 21: Use Web Standardized Interfaces||Need review||Need review||Annette, Yaso||February 19|
|BP 22: Serving data and resources with different formats||Done||Need review||Newton||February 19|
|BP 23: Provide real-time access||Need to be done||Need review||Eric Stephan||February 19|
|BP 24: Provide data up to date||Done||Incomplete||Eric Stephan||February 19|
|BP 25: Document your API||Done||Need review||Annette, Yaso||February 19|
|BP 26: Use an API||Need review||Need review||Annette, Yaso||February 19|
|BP 27: Assess dataset coverage||Done||Incomplete||Deirdre Lee||February 19|
|BP 28: Use a trusted serialisation format for preserved data dumps||Done||Done||Peter Winstanley||February 19|
|BP 29: Update the status of identifiers||Done||Done||Peter Winstanley||February 19|
|BP 30: Gather feedback from data consumers||Need to be done||Need review||Eric Stephan||February 19|
|BP 31: Provide information about feedback||Done||Need review||Eric Stephan||February 19|
|BP 32: Enrich data by generating new metadata.||Done||Need review||Annette||February 19|