OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Minutes: XDI TC Telecon Thursday 1-2:30PM PT 2011-01-13


Following are the minutes of the unofficial telecon of the XDI TC at:

Date:  Thursday, 13 January 2011 USA
Time:  1:00PM - 2:30PM Pacific Time (21:00-22:30 UTC)

PLEASE DIAL ONE OF THFollowing are the minutes of the unofficial
telecon of the XDI TC at:

Date:  Thursday, 13 January 2011 USA
Time:  1:00PM - 2:30PM Pacific Time (21:00-22:30 UTC)

ATTENDING

Michael Schwartz
Giovanni Bartolomeo
Drummond Reed
Joseph Boyle
Markus Sabadello


THE GOTOMEETING FOR TODAY IS:
     https://www2.gotomeeting.com/join/969244355

THE IDEARPAD LINK FOR TODAY IS:
     http://xdi.idearpad.org/18

Please try to preface each of your comments with your name so the
transcription into the minutes is easier.


1) REVIEW MIKE SCHWARTZ'S USE CASES

Mike started by explaining the use case he proposed via email to the list:

A student "Foo1" from University A and a student "Foo2" from Univerity
B "high-four" their pokens.  Each poken is associated with a
"Persona." Foo1's persona is private.  Foo2's persona is public.

When Foo2 downloads his poken data, Foo1 automatically sees a "friend
request." After accepting this friend request, a link contract is
created, and Foo1 should be able to see the  respective published
attributes. Foo2's persona is public. When Foo1 downloads his poken
contacts, he should immediately be able to see Foo2's persona
information (attributes).

XDI is necessary because between institutions, we cannot use LDAP. The
 LDAP server is managed at the organizational level, and there is no
way to  create ACIs to allow Foo1 or Foo2 (or a server on their
behalf) to access  the data. Also, the policy is too complicated to
express in an LDAP ACI.

Mike then explained what a "Poken" is. See http://poken.com. The can
take three forms:

 * Hardware tokens that have a "hand" for "swiping" with other pokens.
 * An iPhone application can scan a picture of another Poken using a QR code.
 * A smartcard form (Miike didn't think it had been released yet).

There is a one-to-one relationship between pokens and personas. The
information given out in each context is different.

Poken currently aggregates all data for Poken.com in Switzerland. Gluu
is offering for universities to host their own Poken data, but to do
so, Gluu needs a federation protocol that can handle link contracts.

Currently, in Gluu, a Poken friend request produces a link contract
attribute of the persona.

Drummond asked Mike a few specifics about what Gluu needs from Poken
friend link contracts.

 * Does the link contract need to control access at the attribute
level? Mike said no, currently he only needs it to cover yes/no access
to an entire Poken persona. (However Gluu may have another use case --
white pages -- that may need attribute-level controls.)
 * What is the authentication requirements? Mike said none: any
request received for a private persona will be approved by the user.
However verification of the source of the request at the university
level would be a value-add. For Gluu's use case, each university could
sign requests with their IdP key. He doesn't think authentication is
needed at the person level or persona level.
 * Is there any reason to grant any other permission besides read
access (XDI Get)? Mike said no, just read access.

We then discussed implementing this. Mike is looking at a tactical
implemention that would minimize complexity.

We discussed XRI resolution. Right now swapping Pokens only produces a
Poken ID. So either Gluu or Poken.com would need to provide a
resolution service for Poken IDs.

We walked through the link contract exchange process for friend
requests. It does involve an approval state at the XDI endpoint of the
person receiving the friend request.


2) REVIEW GIOVANNI BARTOLOMEO'S PDF WITH NOTES ON THE GLOBAL GRAPH

We ran out of time to review this, but Giovanni asked everyone to read
through this PDF document and provide feedback on the list before next
week's call if you can. The document is available at:

   http://www.oasis-open.org/committees/download.php/40757/notes%20on%20the%20global%20graph.pdf

He also said that one purpose of this document is to further explaiin
how XDI can function as a backward-compatible extension of the RDF
linked data ("web of data") universe. Otherwise we risk being "out of
the game" of the semantic community.


3) NEXT CALL

The next call is next week at the regular time.



------------
ONGOING ISSUES LIST

Each of these is a candidate for the agenda for future calls.

* PROPOSED CONSTRUCTS/OPERATORS FOR XDI

Discuss the following wiki page originally posted by Giovanni:

  http://wiki.oasis-open.org/xdi/XdiNewFoundation

* DICTIONARY STRUCTURE

Mike would like an example of the PDX dictionary as soon as we can do it.

*   EQUIVALENCE SEMANTICS

Close on whether we need an additional $ word that is the equivalent
of Higgins Personal Data Model (PDM)  semantics   of h:correlation,
which is not as strong as $is.

      http://lists.oasis-open.org/archives/xdi/201006/msg00036.html

* COOL URIS

Continue previous discussion about the use of standard RDF URIs in XDI:

  http://lists.oasis-open.org/archives/xdi/201006/msg00023.html

E FOLLOWING NUMBERS:

1) Skype Number: +9900827047990866
(this will connect you directly to the conference room)

2) US/Canada Toll Number: +1-201-793-9022  7990866#

3) International Toll Number (follow this with the Conference Room Number:
7990866#)
Austria (0820 401 15470)
Belgium (0703 57 134)
France (0826 109 071)
Germany (0180 500 9527)
Ireland (0818 270 968)
Spain (902 885 791)
Switzerland (0848 560 397)
United Kingdom/Northern Ireland (0870 0990 931)

THE GOTOMEETING FOR TODAY IS:
     https://www2.gotomeeting.com/join/969244355

THE IDEARPAD LINK FOR TODAY IS:
     http://xdi.idearpad.org/18

Please try to preface each of your comments with your name so the
transcription into the minutes is easier.


AGENDA


1) REVIEW MIKE SCHWARTZ'S USE CASES

Mike said on last week's call he was going to post some specific use
cases that we would review on this week's call. If Mike is able to
post them, we'll do a first pass through them.


2) REVIEW GIOVANNI BARTOLOMEO'S PDF WITH NOTES ON THE GLOBAL GRAPH

Giovanni uploaded this PDF today. The document is available at:

   http://www.oasis-open.org/committees/download.php/40757/notes%20on%20the%20global%20graph.pdf


3) CONTINUE DISCUSSION OF XDI DICTIONARY PATTERNS

If there is time, we'll continue the discussion we began last week. See:

   http://wiki.oasis-open.org/xdi/XdiDictionaryPatterns


4) NEXT CALL



------------
ONGOING ISSUES LIST

Each of these is a candidate for the agenda for future calls.

* PROPOSED CONSTRUCTS/OPERATORS FOR XDI

Discuss the following wiki page originally posted by Giovanni:

  http://wiki.oasis-open.org/xdi/XdiNewFoundation

* DICTIONARY STRUCTURE

Mike would like an example of the PDX dictionary as soon as we can do it.

*   EQUIVALENCE SEMANTICS

Close on whether we need an additional $ word that is the equivalent
of Higgins Personal Data Model (PDM)  semantics   of h:correlation,
which is not as strong as $is.

      http://lists.oasis-open.org/archives/xdi/201006/msg00036.html

* COOL URIS

Continue previous discussion about the use of standard RDF URIs in XDI:

  http://lists.oasis-open.org/archives/xdi/201006/msg00023.html


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]