Re: HTTP 402 (payment required) -- the missing link

On 24 June 2015 at 16:32, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

>
>
> On 17 June 2015 at 01:57, Melvin Carvalho <melvincarvalho@gmail.com>
> wrote:
>
>> I've implemented HTTP 402 a few times for payment protected resources.
>>
>> While it works well enough, I ran into a problem.
>>
>> If payment is required, how does the client know what to do next?
>>
>> I think ive found the missing link here, and wanted to run it by people
>> here.
>>
>> What about sending a Location: header telling the client where to go next?
>>
>> Then the client can find all the information about how to pay, their
>> balance, the cost etc.
>>
>> This should enable smooth work flows for payment protected resources, pay
>> walls etc.
>>
>> Thoughts?
>>
>
> FYI: the IETF directed me to :
>
> https://tools.ietf.org/html/draft-ietf-appsawg-http-problem-00
>
>
FYI: I got a response from dret (who was previously chair of the linked
data platform and author of this RFC)

[[
currently, the canonical model is defined in JSON. appendix a talks about
how to represent that model in XML. appendix b talks about "other
metamodels" and mentions RDF in passing, simply as one example of those
other metamodels. it would be possible to add more details about how to use
the canonical model in RDF-land, so that there would be no doubt *how* to
represent the canonical model in RDF. if there's any interest, that's
something that could be done in an additional appendix, and talking about
how that would look in JSON-LD as one RDF representation then also would be
pretty straightforward.
]]