Re: Payment Protected Resources -- Using HTTP 402

On 27 May 2014 20:14, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> On 5/27/14 1:23 PM, Melvin Carvalho wrote:
>
>> Many of us are now using web ACLs on a regular basis.
>>
>> A rule may look like:
>>
>> <>
>>     <http://www.w3.org/ns/auth/acl#accessTo> <.>, <> ;
>>     <http://www.w3.org/ns/auth/acl#agent> <http://melvincarvalho.com/#me>
>> ;
>>     <http://www.w3.org/ns/auth/acl#mode> <http://www.w3.org/ns/auth/
>> acl#Read>, <http://www.w3.org/ns/auth/acl#Write> .
>>
>> This essentially says that my user ID can have read and write access to
>> the named resource.
>>
>> I thought it might be an interesting idea to extend this type of access
>> control to allow payment protected resources.
>>
>> So each server will maintain a balance for each user, as is typical with
>> many commercial business models these days.
>>
>> If the user does not have any credit the server will return a 402 HTTP
>> response code, explaining the cost of the item and how they can top up
>> their balance. This could either be via a traditional payment method such
>> as Euros, or, say, via a balance in crypto currencies, or as part of a
>> loyalty / reward scheme that the web site issues.
>>
>> I'm wondering if we can extend the vocab we have to add payments?
>>
>> Perhaps a simple way would be to subclass #accessTo with #paidAccessTo
>>
>> Then have in the ACL rule a simple payment amount (or rule)
>>
>> Then say something like:
>>
>> <#amount>  0.001^^BTC
>>
>> Anyone have any thoughts on whether this could be implemented?
>>
>
> ## Turtle Start ##
> ## Grants Read-Write privileges on <> and <.>.
>
> <>
>     <http://www.w3.org/ns/auth/acl#accessTo> <.>, <> ;
>     <http://www.w3.org/ns/auth/acl#agent> <http://melvincarvalho.com/#me>
> ;
>     <http://www.w3.org/ns/auth/acl#mode> <http://www.w3.org/ns/auth/
> acl#Read>, <http://www.w3.org/ns/auth/acl#Write> .
>
> ## Turtle End ##
>
> Thus,
>
> ## Turtle Start ##
> <>
>     <http://www.w3.org/ns/auth/acl#accessTo> <.>, <>, <ledger.ttl> ;
>
>     <http://www.w3.org/ns/auth/acl#agent> <http://melvincarvalho.com/#me>
> ;
>     <http://www.w3.org/ns/auth/acl#mode> <http://www.w3.org/ns/auth/
> acl#Read>, <http://www.w3.org/ns/auth/acl#Write> .
>
> ## Turtle End ##
>
> Enables the entity denoted by <http://melvincarvalho.com/#me> to read and
> write data (to and from ) the document denoted by <ledger.ttl>.
>
> You can do that right now.
>
> If you seek uniformity of terms then an accounting oriented ontology will
> do, in regards to the RDF statements that serve as the content of the
> document <ledger.ttl>  :-)
>

+1

I'm trying to work out how such an accounting oriented ontology would
look.  Let's say I wanted to start by creating a simple pay wall on an
article.  I think this would be a good way to start growing liquidity in
the web payments eco system ...


>
> --
>
> Regards,
>
> Kingsley Idehen
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: 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
>
>
>
>
>
>