W3C home > Mailing lists > Public > public-credentials@w3.org > November 2015

Re: Solutions to the NASCAR problem?

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Sun, 22 Nov 2015 17:54:13 +0100
Message-ID: <CAKaEYhK_VxuB7u9_7xwfnFP7T2pnO0zUim7zZDSA-Wp9WZdm2A@mail.gmail.com>
To: Henry Story <henry.story@gmail.com>
Cc: Anders Rundgren <anders.rundgren.net@gmail.com>, W3C Credentials Community Group <public-credentials@w3.org>, "public-webid@w3.org" <public-webid@w3.org>
On 22 November 2015 at 17:13, Henry Story <henry.story@gmail.com> wrote:

>
> > On 21 Nov 2015, at 07:11, Anders Rundgren <anders.rundgren.net@gmail.com>
> wrote:
> >
> > I'm interested hearing what's available and what's cooking:
> > http://indiewebcamp.com/NASCAR_problem
> >
> > Just the core (and links), no TL;DR BS please.
> >
> > Thanx,
> > Anders
>
> If the client has a database of identifiers the user can use, then one
> simple answer
> using WebAccessControl [1] is for the client to follow the acl Link header
> in the returned
> response to fetch information about what agents have access to the
> resource, and then
> present the user with the minimal selection of ids, if any.
>
> I am implementing something like this.
>

Yes, the client should be able to remember who is using it.  That's one
area of browser technology that hasnt really advanced much in the last 25
years.

This spec is promising tho:

https://w3c.github.io/webappsec-credential-management/

Then the nascar problem goes away.  Of course, there are those that might
not want the nascar problem to go away.


>
> Henry
>
>
> [1] http://www.w3.org/wiki/WebAccessControl
>   which we refer from the WebID set of specs
>   http://www.w3.org/2005/Incubator/webid/spec/
>
>
>
> >
>
>
>
Received on Sunday, 22 November 2015 16:54:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 July 2018 21:19:26 UTC