Re: Payment Protected Resources -- Using HTTP 402

With this complete lack of clarity, the WebPayments and WebID groups
won't ever leave their Incubation, IG or CG levels.

HTTP 402 to a browser user?  Hardly.

So obviously there must be at least two server-actors involved, right?

If not, the whole idea is bogus since *internal* operations can be built
as you like and do not need a standards committee for guidance.

Anders

On 2014-05-28 14:47, Kingsley Idehen wrote:
> On 5/28/14 1:27 AM, Anders Rundgren wrote:
>> The most important thing in a payment scenario are the actors and
>> their roles.  Linked Data in not a panacea.  If there are only two
>> actors, HTML is all you need.
> Again, nobody is indicating that Linked Data is a panacea.
>
> You need to be able to access, manipulate, and exchange data for
> anything to function in our realm of existing. Linked Data simply makes
> Data webby or web-like.
> RDF based Linked Data simply ensures the relations that constitute the
> Data are human and machine comprehensible.
>
> RDF based Linked Data is a vehicle for encoding and decoding
> information, via statements, in the medium provided by the Web (an HTTP
> network).
>
> RDF based Linked Data is a kind of Controlled Natural Language.
>
> Without Language, we are unable to function.
>
> Links:
>
> [1] http://slidesha.re/QEqLZN -- Natural Language & RDF based Linked Data .
>
> [2] http://bit.ly/1c3QeEc -- Language .
>

Received on Wednesday, 28 May 2014 13:51:50 UTC