+1
On Fri, Jul 17, 2020 at 3:57 PM Vladimir Dzhuvinov
wrote:
> +1
>
> Vladimir
> On 15/07/2020 20:54, Dick Hardt wrote:
>
> +1
>
> On Wed, Jul 15, 2020 at 10:42 AM Rifaat Shekh-Yusef <
> rifaat.s.i...@gmail.com> wrote:
>
>> All,
>>
>> This is a *call for adoption* for the following *OAuth 2.1* d
The “type” field in the RAR spec serves an important purpose: it defines what
goes in the rest of the object, including what other fields are available and
what values are allowed for those fields. It provides an API-level definition
for requesting access based on multiple dimensions, and that’s
Hey Justin, glad to see that you have aligned with the latest XAuth draft
on a type property being required.
I like the idea that the value of the type property is fully defined by the
AS, which could delegate it to a common URI for reuse. This gets GNAP out
of specifying access requests, and enab
On 17/07/2020 17:38, Justin Richer wrote:
> And all that brings me to my proposal:
>
> 4) Require all values to be defined by the AS, and encourage specification
> developers to use URIs for collision resistance.
>
> So officially in RAR, the AS would decide what “type” means, and nobody else.
