W3C home > Mailing lists > Public > public-webpayments@w3.org > September 2014

Re: Unlinkability. Re: Building Linked Data into the Core of the Web

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Mon, 22 Sep 2014 21:50:19 +0200
Message-ID: <CAKaEYhKAcHOxDDkB8b14_rtBziiTmhCO6KXWgis7zWAtatXY+A@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: Kingsley Idehen <kidehen@openlinksw.com>, Web Payments <public-webpayments@w3.org>
On 22 September 2014 17:32, Anders Rundgren <anders.rundgren.net@gmail.com>
wrote:

> On 2014-09-22 13:16, Kingsley Idehen wrote:
>
>> On 9/22/14 2:31 AM, Anders Rundgren wrote:
>>
>>> I'm by no means an enemy to Linked Data, I just don't see what it
>>> would do for *conventional* payments except for introducing privacy
>>> and access control concerns.
>>>
>>
>> Please take time to digest:
>>
>> [1] http://bit.ly/enterprise-identity-management-and-
>> attribute-based-access-controls
>> [2] http://bit.ly/loosely-coupled-read-write-web-and-web-access-
>> controls-using-webid .
>>
>> You cannot make a moderately usable system without an identification
>> mechanism that isn't yet another data silo.
>>
>> *conventional* payments are an application of data driven identification,
>> interaction, and management.
>>
>
> My only ambition has been describing how you could "webify" an existing
> payment system,
> *without* changing data ownership, relationships, business-, trust-, or
> privacy-models.
>

Anders, re "webify" there's a term called "webize" coined by tim since 1998

http://www.w3.org/DesignIssues/Webize.html

It's a really important part of standardization.  The value add of a
universal payment system is that you can boostrap existing solutions (hence
the term universal).

For web payments to grow it is important to embrace what already exists out
there and fold it into our effort to grow the network.  Kingsley has done
this quite expertly for social systems.  But what is needed is someone to
do the same in payments, which is probably a 0.5 or 1 person task.

We have a small community group dedicated to webizing existing systems.
But in short it consists of mapping local variables to URIs.


>
> Since the main problem with identity information is not the information
> itself but
> how it will be used after being submitted, it seems like a safe(r) bet
> minimizing
> exposure of such data.  This is a corner-stone of my write-up.  Another
> example is
> FIDO which (at least on paper...) is the opposite to Linked Data since
> each site
> is supposed to be an identity silo.  In practice FIDO doesn't work as
> Google claims
> but that's altogether different discussion :-)
>
> Anders
>
>
>
>
>
>> Your point is inherently contradictory.
>>
>> --
>> Regards,
>>
>> Kingsley Idehen
>> Founder & CEO
>> OpenLink Software
>> Company Web:http://www.openlinksw.com
>> Personal Weblog 1:http://kidehen.blogspot.com
>> Personal Weblog 2:http://www.openlinksw.com/blog/~kidehen
>> Twitter Profile:https://twitter.com/kidehen
>> Google+ Profile:https://plus.google.com/+KingsleyIdehen/about
>> LinkedIn Profile:http://www.linkedin.com/in/kidehen
>> Personal WebID:http://kingsley.idehen.net/dataspace/person/kidehen#this
>>
>>
>
>
Received on Monday, 22 September 2014 19:50:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:39 UTC