home projects speaker

Trusted Data
– What is Trusted Data?

We live in a plane in the space-time continuum surrounded by data. An inconceivable amount of data. Every day we observe, process, interpret, analyse and act upon data. Not just with computers, but with anything, everywhere. We watch TV, use social media, we look through the window, we smell the rain, we sense the tingling feeling on our feet when walking barefooted in the grass. We collect data 24/7, even when we sleep. With so much data out there, how can we trust it? What is "Trusted Data"?

Table of Contents

  1. What is data?
  2. What is trust?
  3. Trusted data
    1. What is a source?
    2. Verification of data
    3. Examples of erroneous data
    4. What makes data untrustworthy?
    5. What risks are involved when we have untrustworthy data?
    6. Interpretation of data
  4. A final word

If we take in consideration, the whole observable universe, scientists have calculated the information capacity to be staggering 1090. How much data is that? Well, it is 1.25 × 1080 gigabytes. Not clear enough? It's the equivalent of all the digital data produced on earth every day( 5 exabytes in 2013 ) until the universe succumbs to heat death and long after that. And that copious amount of data does not include the digital data that is produced every day.

We are not going to indulge ourselves in the universe or the space-time continuum in this article, We are not all physicists. This article is not about "Big Data", this article is about the data we all deal with on an everyday basis, but especially, digital data and what makes it "Trusted Data".

To get a better grasp of the concept of "Trusted Data", we need to know what lies in the terminology used.

What is data?

Suman Deb Roy and Wenjun Zeng defines, in their book Social Multimedia Signals: A Signal Processing Approach to Social Network", data as "... an abstract concept (that) can be viewed as the lowest level of abstraction, from which information and then knowledge are derived."

Data is what we observe, what we perceive. It is what we humans collect through sensory input.

Digital data, in information theory and information systems, are discrete, discontinuous representations of information or works, as contrasted with continuous, or analogue signals which behave in a continuous manner, or represent information using a continuous function.

Digital data could be described as data that is collected and represented through a digital interface.

What is trust?

In a social context, trust has several connotations. Definitions of trust typically refer to a situation characterized by the following aspects: One party (trustor) is willing to rely on the actions of another party (trustee); the situation is directed to the future. In addition, the trustor (voluntarily or forcedly) abandons control over the actions performed by the trustee. As a consequence, the trustor is uncertain about the outcome of the other's actions; they can only develop and evaluate expectations. The uncertainty involves the risk of failure or harm to the trustor if the trustee will not behave as desired.

The definition of trust regarding relationship between people and technology is a bit more cumbersome, since it describes a state that conflicts with the rational reflection of human beings:

When it comes to the relationship between people and technology, the attribution of trust is a matter of dispute. The intentional stance demonstrates that trust can be validly attributed to human relationships with complex technologies. However, rational reflection leads to the rejection of an ability to trust technological artifacts.

When we collect, interpret and analyse data, we have to rely on a certain trust to the data we work with. The trust we rely on can be grouped in three levels of trust:

Deterrence-based trust (rules)

Deterrence-based trust means that there are rules in place that prevent one person from taking advantage of, or harming another person. In society, we have laws that govern our behaviour in personal and business settings.

Knowledge-based trust (experience)

This level of trust means that I have had enough experience with you and knowledge of your behaviour that I have a pretty good idea of how you will react and behave in relationship with me. We have had enough interactions over time where there has been a consistent display of trustworthy behaviour that I believe I can trust you with the everyday type issues we experience together.

Identity-based trust (identity)

This level of trust means that you know my hopes, dreams, goals, ambitions, fears, and doubts. I trust you at this level because over the course of time I have increased my level of transparency and vulnerability with you and you haven’t taken advantage of me. You have proven yourself to be loyal, understanding, and accepting.

"Trusted Data", regardless the level of trust, is data you can rely on to process information from, information used to gain knowledge, make decisions and act upon.

Trusted data

When we now have the terminology in order, what have others stated about this term?

... the condition of trusted data is easily quantified. Namely, condition is a technical measurement of data’s completeness, quality, age, schema, profile, and documentation. The assumption is that trusted data should come from carefully selected sources, be transformed in accordance with data’s intended use, and be delivered in formats and time frames that are appropriate to specific consumers of reports and other manifestations of data.

Philip Russom describes "Trusted Data" as a concept that is easily quantified by the conditions of the data. He quantifies that "Trusted Data" should:

  1. Come from carefully selected sources
  2. Be transformed in accordance with data's intended use
  3. Be delivered in formats and time frames that are appropriate to the specific consumers

So "Trusted Data" will come from sources that you carefully select? Let us explore this:

What is a source?

Definition: Any thing or place from which something comes, arises, or is obtained

A source could be a landscape, a scent, a taste, a book, a human, an API, a show on the television. Sources can give erroneous data, so how can we trust a source?

We can use the levels from the previously mentioned grouping to view the selection premises:

Rules

"The API can only give us information about this customers pension because the rules prohibit us to view another person's pension"

Experience

"We have experienced enough with the API that it always delivers the correct data"

Identity

"We know that the API (and the provider) is trustworthy of reputation and brand"

But these trust levels could apply to sources we already have used, what do we do with new sources? How can we verify sources to use them, and in the long run, trust them?

The validity of sources is only as valid as the data given. In the science terminology, reliability is a factor. If the same data can be reproduced, the data is reliable. But what about verifying the data?

Verification of data

The validity of data is often verified by several sources. In the social realm and the interaction between humans, i.e. communication, the validation of data is often done by confirmation: "Did you guys see that?", "Yes".

Who lied? Did anyone lie? How can we be certain? If the verification is done by a human, and the sensory input to a human in combination with how logical the human's thought process is and the fact that humans jump to conclusions ( fills in the blanks ), there will always be uncertainty.

Some data collected from digital sources can be verified by other data from digital or analogue sources. For example, a registered birthdate on a family member in an on-line family tree can be verified against the state record.

But if we validate fake data against fake data, how are we going to actually have data we can trust?

Examples of erroneous data

There are many, far too many, examples on erroneous data:

In genealogy

The longer back you research in genealogy, there are fewer or no decent and verified sources. Family trees can be based on other family trees that have erroneous data or no sources. Data about families can be deliberately falsified to preserve family ties, heirship and power. Family conflicts can sever a whole lineage due to the wrong religion.

When old church books are transcribed, often digitally (by OCR scanning) or by a human, letters and text can be interpreted wrong.

Maps

In the 16th and 17th century, the time before Google Maps and GPS, when the Earth was not fully mapped, the cartographers that created maps for the seafarers could for example depict sea monsters on the map. This was based on myths and legends, folklore and what the people in that time did not fully understand. But later in the 17th century, the monsters vanished, relative to the scientific progress of the time.

In these modern times, we rarely find these data anomalies (or abnormalities), due to satellite mapping and greater understanding. One of these rarities was the Google Maps anomaly, an unknow island appeared on Google Maps. This was later undiscovered.

Information Technology (IT)

Within IT, were handling of data could be crucial for the business, we find several examples with erroneous data. One good example is the MongoDB Fault Tolerance. MongoDB did not save data when instructed and then reported that the data got saved. This resulted in incomplete data-sets.

What makes data untrustworthy?

We all process data, in our jobs, in our lives, every day. We can verify the data we collect through sources. We can trust the source itself or verify the data from other sources. But what makes data untrustworthy?

The human factors are also relevant here. We are not perfect. We make mistakes. We are all individuals with our own unique thought patterns. We perceive things differently, we fill in the blanks, interpret things. We forget. We are blind, deaf, near-sighted, long-sighted, colour-blind. We have hidden agendas, political views, personal views, religious views. All of this are factors in how humans perceive, interpret and relay data.

We have technical factors when it comes to relaying and collecting data; Phone lines could be down, the mail could not be delivered. With digital data, we could have charset errors, disk crashes, network issues, bugs et al. These factors can delete data, let data never be collected, saved or relayed.

There are may factors to consider when we deem data untrustworthy. Risks in particular.

What risks are involved when we have untrustworthy data?

The risks involved with untrustworthy data could be sectioned into groups depending on the impact of these risks.

Low impact risks

Low impact risks are risks that has little or no effect in the surrounding context.

Personal risks could be:

  • Dead link to web page
  • Wrong reference to a book in a library
  • Wrong TV-program according to the TV-schedule
  • Missed the bus due to old bus schedule

Health risks could be:

  • Light injury because of missing warning signs

High impact risks

High impact risks are risks that has large effect in the surrounding context, a game-changer you might say.

Social risks coud be:

  • Loss of friendship
  • Bullying

Economical risks could be:

  • Big loss of profit in the stock market due to false reports on yield
  • Bankruptcy of businesses

Political risks could be:

Health risks could be:

  • Death
  • Severe injury
  • Terminal illness

This risk/impact grouping is not based on any empirical or statistic data, but a rough grouping by the author.

The grouping above is just a small collection of risks related to untrustworthy data. Data that is erroneous when relayed. But what about the interpretation of data. Could "Trusted Data" be interpreted differently?

Interpretation of data

When we observe or collect data, we also process it. A part of the process is the interpretation of data. We try to figure out the meaning of the data from our own unique understanding. This is the basis of that perspective and how we interpret data.

A programmer is going to the grocery store and his wife tells him, "Buy a gallon of milk, and if there are eggs, buy a dozen." So the programmer goes, buys everything, and drives back to his house. Upon arrival, his wife angrily asks him, "Why did you get 13 gallons of milk?" The programmer says, "There were eggs!"

To sum this up progammatically:

javascript
var milk = require('milk');
var customer = require('customer');
var store = require('grocery-store');

if (store.gotEggs()) {
  // Buy 12 gallons
  customer.buy().product(milk).quantity(12).unit('gallon');
} else {
  // By one gallon
  customer.buy().product(milk).quantity(1).unit('gallon');
}

The programmer interpreted the information in another way that his wife expected. You can argue extensively about why he interpreted it that way, but that is how we humans work. We interpret things differently. We have our own unique understanding about everything.

The wife, obviously for most people, assumed that the message was interpreted the same way she did. She assumed that her husband had the same understanding of what she asked. The data was interpreted differently.

But we can interpret this example even further:

javascript
var milk = require('milk');
var customer = require('customer');
var store = require('grocery-store');

// Buy one gallon
customer.buy().product(milk).quantity(1).unit('gallon');

if (store.gotEggs()) {
  // 12 more gallons
  customer.buy().product(milk).quantity(12).unit('gallon');
}

See what happened here?

"Buy a gallon of milk, and if there are eggs, buy a dozen."

The data was the same, the interpretation were different. This is the interpretation that the wife expected:

javascript
var eggs = require('eggs');
var milk = require('milk');
var customer = require('customer');
var store = require('grocery-store');

// Buy one gallon
customer.buy().product(milk).quantity(1).unit('gallon');

if (store.gotEggs()) {
  // 12 eggs
  customer.buy().product(eggs).quantity(12).unit('pieces');
}

A final word

We have now gone through the term "Trusted Data", but how do you work with the data that you want to be trustworthy?

The next article will cover these areas. It will hopefully give a good grasp on how to work with data, and how we make sure it can be trustworthy.

This article tried to reflect upon the definition of "Trusted Data", examples on how data can be false and how correct and false data can be interpreted in different ways.


About the author

Hi! My name is Alexander, and I am a creative frontender, specializing in UX, accessibility, universal design, frontend-architecture, node and design systems. I am passionate with open source projects and love to dabble with new emerging technologies related to frontend. With over 24 years of frontend experience, I have earned the right to be called a veteran. I am a lover of life, technologist at heart. If I am not coding, I am cooking and I love whisky and cigars. Oh, and coffee, I LOVE coffee!

If you want to know more about me, here is some links you might want to check out: GitHub, Instagram, Twitter, LinkedIn, CodePen, Slides.com, npm,

Speaker

I am also an avid speaker on several topics! Check out some of the things I speak about, and contact me if you are interested in having me at your next event!