- From: Heidi Vanparys via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Mar 2020 15:46:13 +0000
- To: public-dxwg-wg@w3.org
> Datasets surely must be digital in nature (ones and zeroes) I don't agree with that. See e.g. some historical examples described at https://en.wikipedia.org/wiki/Census and https://en.wikipedia.org/wiki/Census_in_Egypt : - "during the Roman Republic, the census was a list that kept track of all adult males fit for military service" - "In 1183, a census was taken of the crusader Kingdom of Jerusalem, to ascertain the number of men and amount of money that could possibly be raised against an invasion by Saladin, sultan of Egypt and Syria." So the result of a census is a dataset, isn't it? The term wasn't used back then, but with today's language it would be called a dataset. It contains data on the number of men and/or number of inhabitants, possibly registered per administrative unit, and the data allow to do certain types of analysis. Taxes can be calculated etc. Another example: I could write down in my analogue bullet journal or diary on what days I went for a 5 km run and also keep track of the amount of time in which I completed that run. To me, that is a dataset as well. I could also take a scan of that sheet of paper (or sheets of paper) and send that to my running coach as a PDF-document. And I could, at some time, enter those data in a spreadsheet and import into some smart application that can create nice diagrams etc. So, one dataset, different representations of it. So narrowing the dataset definition down to "digital" would be undesirable IMO (just as "published or curated by a single agent" is narrowing both resource and dataset down in an undesirable way). -- GitHub Notification of comment by heidivanparys Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1221#issuecomment-606080133 using your GitHub account
Received on Monday, 30 March 2020 15:46:16 UTC