Date: Thursday, 05 August 2010 USA
Time: 1:00PM - 2:00PM Pacific Time (21:00-22:00 UTC)
PLEASE DIAL ONE OF THE FOLLOWING NUMBERS:
1) Skype Number: +9900827047990866
(this will connect you directly to the conference room)
{Bill is not able to join Skype chat from current work location}
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)
AGENDA
NOTE: THE IDEARPAD LINK FOR TODAY IS:
http://xdi.idearpad.org/7
The password is:
turtle
Please try to preface each of your comments with your name so the transcription into the minutes is easier.
(Note: the link to last week is
http://xdi.idearpad.org/6 - password was "turtle".)
1) TOPIC PRIORITY PLANNING FOR XDI RETREAT
Although this was also the lead topic last week, we still need to finish the discussion to determine and prioritize the topic list for the XDI Retreat at Whistler, B.C. Aug 12-16. Notes from last week included:
2 tracks for retreat: technical and
business focused
Technical Topics for the retreat:
- JSON format
(including datatypes)
- Is XDI a network protocol and how do we separate it
from language definition
- XDI Messaging: async vs sync, push vs pull, pub
sub?
- Link contracts
Business Topics for the retreat:
- Applying
Social Networking
- VRM
- Branding and adoption-driving
- Product and
user-experience2) XDI JSON SCHEMA
This topic was also discussed last week. The goal is to frame a precise list of the remaining open issues so that they can be discussed in detail and hopefully decided at the XDI Retreat (if Bill or others are not able to make it, hopefully they will be able to join by telecon).
3) LINK CONTRACTS
This may be a topic to tackle at the retreat:
http://lists.oasis-open.org/archives/xdi/201001/msg00010.html
- If link contracts are enabled at an XDI endpoint and no link contracts exists, what is the "default" behavior? Allow nothing? Allow only $get?
- Can an XDI endpoint have a special notion of the XDI endpoint "belonging" to a user?
- Is yes, does that user automatically have "full rights" to the XDI endpoint outside of normal link contract evaluation?
- As an alternative to signing XDI messages with a key, can an XDI message contain a user's password for authentication?
Second, Markus posed another excellent set of questions this week around link contract processing:
http://lists.oasis-open.org/archives/xdi/201006/msg00048.html
We need to discuss these as well.
4) PDX EXAMPLE APPS WIKI PAGE
Pending topic:
http://wiki.oasis-open.org/xdi/PdxExampleApps
5) QUESTIONS AROUND $IS SEMANTICS
Open issue: 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
6) COMPATIBILITY WITH COOL URIS
Continue previous discussion about the use of standard RDF URIs in XDI:
http://lists.oasis-open.org/archives/xdi/201006/msg00023.html
7) XDI ACCESS CONTROL QUESTIONS
Markus sent a proposal for how OAuth access tokens could be used with XDI:
http://lists.oasis-open.org/archives/xdi/201006/msg00021.html
Review and see how TC members feel about this approach.
8) NEW BUSINESS
9) NEXT CALL