W3C home > Mailing lists > Public > public-dwbp-wg@w3.org > May 2016

Sensitive data text for enrichment section

From: Phil Archer <phila@w3.org>
Date: Fri, 6 May 2016 15:50:26 +0100
To: Public DWBP WG <public-dwbp-wg@w3.org>, Bernadette Farias Lóscio <bfl@cin.ufpe.br>, Annette Greiner <amgreiner@lbl.gov>
Message-ID: <df99503b-af5f-483f-1dbf-e9a140ed7970@w3.org>
Berna,

As promised, I've copied the text from the sensitive data section and 
merged some of it with the data enrichment intro to end up with this as 
a suggestion.

@Annette - we resolved to do this and move the BP about data 
unavailability to the data access section. Do you agree with this?

===Begins==

Data enrichment refers to a set of processes that can be used to 
enhance, refine or otherwise improve raw or previously processed data. 
This idea and other similar concepts contribute to making data a 
valuable asset for almost any modern business or enterprise. It is a 
diverse topic in itself, details of which are beyond the scope of the 
current document. However, it is worth noting that techniques exist to 
carry out such enrichment at scale which in turn highlights the need for 
caution.

Not all data should be shared openly. Security, commercial sensitivity 
and, above all, individuals' privacy need to be taken into account. It 
is for data publishers, not a technical standards working group, to 
determine policy on which data should be shared and under what 
circumstances. Data sharing policies are likely to assess the exposure 
risk and determine the appropriate security measures to be taken to 
protect sensitive data, such as secure authentication and use of HTTPS.

Depending on circumstance, sensitive information about individuals might 
include: full name, home address, email address, national identification 
number, IP address, vehicle registration plate number, driver's license 
number, face, fingerprints, or handwriting, credit card numbers, digital 
identity, date of birth, birthplace, genetic information, telephone 
number, login name, screen name, nickname, health records etc. Although 
it is likely to be safe to share some of that information openly, and 
even more within a controlled environment, publishers should bear in 
mind that data enrichment techniques may allow some elements to be 
discovered and linked from elsewhere.

Notwithstanding that caution, data enrichment offers exciting 
possibilities for both data publishers and consumers.



== ends==

-- 


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

http://philarcher.org
+44 (0)7887 767755
@philarcher1
Received on Friday, 6 May 2016 14:50:31 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 May 2016 14:50:31 UTC