Data Ownership

Hi Tim,

I'm investigating the concept of deploying RWW / LDP based technology for
TV systems, so that users store their own personalisation data (and
hopefully also, improve some of the economics for community broadcasters,
etc.).

I've worked on VOD / Hybrid TV solutions for many years , and when it was
brought-up at a conference, i became involved - identifying shortly
thereafter, an potential opportunity for RWW/LDP technology utilisation.

In a Guardian Article [1] you stated;

“What are these people going to do with that data? They’re going to target
you with an ad which makes you feel a bit queasy. Targeted adverts are not
the future.”

I'm hoping you could clarify the meaning of your statement so i can better
understand (and communicate to others) whether i'm working in-line with
your thinking or outside of its boundaries.

*CONSIDERATIONS*
Broadcast Only TV: only supports advertising by relatively large
businesses. Australia has a 'free TV culture', where advertising has
traditionally funded the cost of delivering media to TV (highly
accessible).

Technology Enhancements to support Local advertisements (by very small
businesses) can aid economic development in an array of ways, and
personalisation data is likely more involved than simply the data stored
for targeting advertising (ie: education, government and other services via
"free tv" services) understanding everyone currently needs to afford the
internet/data access fees, via service providers who can hopefully lower
the cost, and improve the performance of their networks....

As we know = there is a distinction between RWW / CrossCloud / LDP like
data-storage models (decentralised) vs. Traditional (relational DB)
Technologies, end-user agreements, etc..

This also relates somewhat to the functions being considered by
Web-Payments and Credentials Groups, around privacy, what info is needed by
merchant vs. payment processor, etc.

I'm not sure the industry at large really understand the difference between
these works; and the technical functions of traditional systems that would
use a relational database (and therefore also, store user-data centrally,
etc.); and therefore might attempt to compare apples with oranges, then
find this guardian document and get further confused...

Perhaps my underlying assumption; is that we may be able to perform these
types of technical functions whilst significantly enhancing privacy. ie:
Web-Payments / Credentials systems privacy use-cases between merchants and
customers; vs. the needs of payment processors.

I note; Free TV (DVB-T) has no payment ($$$) processing requirements, which
is considered socially supportive.

*FURTHER BACKGROUND*
The HbbTV Specification [2] appears to provide support for WebID-TLS (which
will need to be tested, etc.) and my hope is that RWW / LDP infrastructure
might enable storage of personalisation data by users rather than TV
Service Operators.  I've quickly written some thoughts on this [3] however
more work needs to be done, if the concept gets initial support, etc.

In theory; RWW/LDP styled storage solution may solve an array of problems.
Taking into consideration the notes by sandro[3] recently (his radical
theory, HbbTV[5] V2 including 'web-sockets'[6], etc.) any solution would
need an array of different scripts for managing content distribution (ie:
Community TV provider) and/or end-user data-storage; yet overall, it might
just work!! (and be something that has broader opportunities / effects...)

The note in July [7] helped with thinking; yet the WebID-TLS spec, IMHO -
probably still needs to attribute a TV as a TV that can then be assigned to
Persona/s, and perhaps reset to a 'generic function' on a time-basis -
being considerate of the amount of work that would need to be done should
the concept be viable...

Yet at the moment; given the article exists - i'm a bit worried about the
interpretation by professionals from other fields.

Kind Regards,

Tim.H.

[1]
http://www.theguardian.com/technology/2014/oct/08/sir-tim-berners-lee-speaks-out-on-data-ownership
[2]
http://www.etsi.org/deliver/etsi_ts/102700_102799/102796/01.02.01_60/ts_102796v010201p.pdf
[3]
http://lists.w3.org/Archives/Public/public-rww/2014Oct/att-0003/CloudStorage.pdf
[4] http://lists.w3.org/Archives/Public/public-ldp-wg/2014Nov/0010.html
[5] http://www.w3.org/2013/10/tv-workshop/papers/webtv4_submission_13.pdf
[6] http://www.w3.org/2013/10/tv-workshop/minutes.html#day1-item052
[7] http://lists.w3.org/Archives/Public/public-rww/2014Jul/0040.html