Imperative sub titles

I took an action last week to provide slightly reworded subtitles for 
BPs 1-19. I offer the following.

However, I note that several of these are simple restatements of the 
title and therefore add nothing. In my view, they could be omitted 
altogether. These are marked with an asterisk.

I can easily bash out the remaining ones and am happy to do so but I;m 
interested to see whether others (I'm thinking of Annette) agrees with 
my formulations.


1. Provide metadata

Provide metadata for both human users and computer applications.


2. Provide descriptive metadata

Provide metadata describing the overall features of datasets and 
distributions.


3. Provide locale parameters metadata

Provide metadata describing the locale parameters (date, time, and 
number formats, language)


4. Provide structural metadata

Provide metadata describing the internal structure of a distribution and 
the schema(s) used.

5. Provide data license information

Link to a license or provide license information directly.

6. Provide data provenance information

Provide metadata describing the provenance of the data.*

7. Provide data quality information

Describe the quality of the data.*

8. Provide a version indicator

Indicate the version number or date for each dataset.*

9. Provide version history

Describe the change history of the data.

10. Use persistent URIs as identifiers of datasets.*

Assign persistent URIs to datasets.


11.  Use persistent URIs as identifiers within datasets

Where possible, reuse other people's URIs as identifiers for elements 
within datasets, assign your own if necessary.

12. Assign URIs to dataset versions and series

Assign URIs to individual versions of datasets as well as the overall 
series.*

13. Use machine-readable standardized data formats

Make data available in a machine-readable standardized format that is 
adequate for reuse by others.

14. Provide data in multiple formats

Provide data in more than one format*

15. Use standardized terms

Use standardized terms when providing data and metadata.*

16. Reuse vocabularies

Reuse shared vocabularies to encode data and metadata.*

17. Choose the right formalization level

When reusing a vocabulary, opt for a level of formal semantics that fits 
both data and applications.

18. Provide an explanation for data that is not available

Where data is referred to that is not open, or is available under 
different restrictions to the origin of the reference, provide an 
explanation about how the referred to data can be accessed and who can 
access it.

19. Provide bulk download

Provide a means through which the entire dataset can be downloaded for 
local processing.



-- 


Phil Archer
W3C Data Activity Lead
http://www.w3.org/2013/data/

http://philarcher.org
+44 (0)7887 767755
@philarcher1

Received on Monday, 25 April 2016 16:47:43 UTC