Data: Intent and Primary Interpretation
Take a JPEG image file and a CSV file. Which of these two is data? Is one of them more obviously data than the other? I think the key difference is the intent behind the data and its primary interpretation.
The way we experience different files is governed by the tools we use. Every file browser and operating system these days displays an image as a thumbnail, so we know immediately what it is (and what it’s of). That can make it difficult to appreciate how much goes into transforming the data encoded in the JPEG format into pixels you can see.
The same is true for the CSV, though it’s the other way around. CSV is a text format, which makes it easy to read for humans. Any text editor can show you the characters that make up the numbers. It takes more work to turn this into a representation that can be used by programs, though, because they need to parse all those strings of numbers back into useable binary representations.
Both are data in the end, of course, since anything a computer can store is data by definition. That doesn’t even just include files you think of as data but also programs, the low-level structure of the storage medium itself, etc.
What does distinguish data files from others is the intent with which they were created. They have file extensions, file format markers, and metadata that tells the system that they are specific kinds of files and – more importantly – that there is a specific way of interpreting them. Not the only way, but a clearly meaningful way.
Images, videos, etc., are created with a primary interpretation in mind. For an image, it is to be rendered onto the screen (and maybe manipulated in a photo editor), for a video it is to be played (or edited, in a specific editor), a 3D design to be rendered in 3D and perhaps sliced for a 3D printer, a sound file to be played through speakers, etc.
Data files are different because they record data without a specific intent. There is nothing that makes one CSV file work better as a bar chart and another better as a line chart. One data file isn’t better aggregated by year while another needs to be filtered to a particular region first and then summed up across vendors.
The data that is of interest for data analysis and visualization is different from images because it does not have a primary interpretation. A database table can contain many different kinds of data in each of its columns, describing anything. Business transactions, counts of salmon at different observation points over time, vote counts, etc.
Since there is no primary interpretation, choices have to be made. A program can analyze the data and make suggestions, but ultimately the user needs to figure out what way of dealing with the data is the most useful. Perhaps it’s a scatterplot or a bar chart. Perhaps a script that processes the data into some other form, sends out alerts, creates a website. Perhaps it’s just a table listing the numbers in all the rows and columns (assuming that is a reasonable assumption about the file’s structure), but even that is a choice.
This is part of what makes data so interesting, though: there are many possible interpretations of the same data; sometimes finding a good one is obvious and easy, often it is hard and requires trying out many different approaches.
Of course images, videos, etc. are data too. Of course it can be a good idea to try out interpretations other than the obvious ones, and of course that can be interesting or lead to new insights – or it can be a novelty without much value.
But the image already has an intent and a primary interpretation associated with it that works for the vast majority of people. The data file does not. That I think is the key difference between the two.