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

Hello Credentials CG

From: Markus Sabadello <markus@projectdanube.org>
Date: Fri, 27 Mar 2015 17:21:44 +0700
Message-ID: <55152F38.40302@projectdanube.org>
To: public-credentials@w3.org
Hello there,

Just wanted to say hello, I have been on the list for a while but
haven't had a chance yet to participate.
For a while now, my friend Pavlik has been encouraging me to study the
great work you are doing!

I'd like to share a few observations, questions..

1. A few years ago I was working on the Eclipse Higgins project and
InfoCards (aka Microsoft CardSpace).
The Credentials work reminds me very much of what we did back then, so
probably you are aware of that?
What you call a credential was called a card, but it was before JSON-LD,
so our cards simply had 15 pre-defined key/value fields.
We basically had all the architecture and components working, with
browser plug-ins ("selectors") that could submit cards (credentials) as
well as accept newly issued ones.
We even built a simple iPhone browser plug-in that could do this, in
2008 even before Apple had released the App Store.
Okay enough history, you may have already known this anyway.

One thing that is not quite clear to me is whether a) a fresh credential
is obtained from the credential service every time it is needed at a
website, or whether b) it is just obtained once and then stored. Reading
your spec draft, I think it is a), but your intro video seems to suggest
b). So I assume you are considering both approaches.

Another question I have is, how would I actually submit a credential to
a website in practice, e.g. with a browser plug-in or otherwise, do you
have working demos of this?

2. I've also been working quite intensely with a technology called XDI,
which is a bit like the "evil twin" of RDF :)
XDI is politically a bit sensitive, and I don't want to get into it too
much.
But I do want to share a list of demos and use cases we have worked on
in the XDI world:
http://xdi2.org/demos.html

There seems to be some overlap with your use cases.
In one of them ("+acmepizza"), a website requests an up-to-date e-mail
address for a customer whenever it is needed.
This seems to be similar to your "Non-interactive Transmission" use case.

Anyway, just wanted to share this, looking forward to studying your work
more and comparing it with the technologies I have worked with.

3. My understanding is that a few of you will be at the upcoming IIW?
If so, it would be great to meet there and chat!

all the best,
Markus



Received on Friday, 27 March 2015 10:22:17 UTC

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