Minutes: XDI TC Telecon Friday 2012-05-18

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

Date: Friday, 18 May 2012 USA

Time: 9:00AM - 10:00AM Pacific Time (16:00-17:30 UTC)

THE ETHERPAD LINK FOR TODAY IS:

http://piratepad.ca/BxqnCsdcTe

ATTENDING

Bill Barnhill

Markus Sabadello

Drummond Reed

Joseph Boyle

Michael Schwartz

Phil Windley

1) SMARTDATA AND PII 2012 UPDATE

Drummond said he attended the opening reception and first day of the SmartData conference in Toronto on Monday and the direction of SmartData is very compatible with the work of XDI. SmartData seeks to use intellgent agents to control the release of personal data to protect privacy. From the perspective of the personal data ecosystem, this is like adding a "brain" to a personal data store/personal cloud to be able to sense when is and is not the right conditions for sharing data.

Drummond and Joseph reported that the Privacy/Identity/Innovation 2012 conference in Seattle was good but didn't really involve any technical discussions; it was mostly focused on privacy policy and business related developments. It certainly reinforced that the market for privacy-respecting solutions is growing and becoming more sophisticated.

2) OPEN SOURCE PROJECT UPDATES

Mike reported that the OpenXDI project added more tests to oxTest Tool; changed look and feel of config page; added validation of credentials; next week: will add automatic client id / secret registartion;

http://seed.gluu.org/oxTestTool

3) OASIS TEST XDI SERVER

Markus said that OASIS still has not completed the contract, but that this may be due to email issues.

# MARKUS AND DRUMMOND to check into email issues.

Mike proposed to make seed.gluu.org the "test XDI server" since it already has the test tool deployed.

There was much discussion about the best way forward on this, including doing a network of test servers.

# MARKUS, JOSEPH, AND MIKE to meet offline and come back to the TC with a recommendation for how best to proceed with the test server.

4) SPEC REPOSITORY REPORT

Bill reported that he has set up the Open DITA toolkit. OASIS does not have a current DITA template but Bill has created one.

The workflow is:

An author makes a change to thier own GIT repository.

It gets committed to Github.

Github sends a JSON message to the relay server.

The relay server extracts the information from the message, processes it to prepare it for the OASIS SVN, and then commits it to the OASIS SVN.

Bill said the remaining tasks are:

Deploy solution to hosting provider, doing provider specific hardening and cert

Get public keys from each TC member and add as committer

Publish documentation (User guide, CM guide, Guide for Offline builds)

Get baseline set of XDI docs

Extract content from baseline docs into DITA topics (could use help on this), one doc is done, probably three docs total.

Bill needs each author to send him your public SSH key so he can set up an account. Bill says there will be a key for each machine you are using.

5) XDI ARTICLE FOR PERSONAL DATA JOURNAL

Markus is writing an article about XDI for the PDEC journal. One thing he would like to do is get a quote from each active XDI TC member that provides one detail of what XDI provides that is unique and really useful.

6) XDI QUERY

Mike made the following proposals:

1. Propsoal for $onelevel to specify depth of search in XDI Messaging

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$()/(@!4444)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$d!/(data:,2012-05-18T15:15:34.429Z)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$do/@!4444$do

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/{JWT-0.6}$token!/(data:,eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczpcL1wvc2VlZC5nbHV1Lm9yZyIsInVzZXJfaWQiOiJtaWtlIiwiYXVkIjoiQCExMTExITAwMDghQTY0QyE0NzVDIiwiZXhwIjoxMzM3MzU3NzM0MTE4LCJveEludW0iOiJAITExMTEhMDAwMCFENEU3Iiwib3hWYWxpZGF0aW9uVVJJIjoiaHR0cHM6XC9cL3NlZWQuZ2x1dS5vcmdcL294YXV0aFwvc2VhbVwvcmVzb3VyY2VcL3Jlc3R2MVwvb3hhdXRoXC9jaGVja19zZXNzaW9uIiwib3hPcGVuSURDb25uZWN0VmVyc2lvbiI6Im9wZW5pZGNvbm5lY3QtMS4wIn0.joij9FsQMofajlERFILyV4G-up0cx_Kc9MUzs1trVHk)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$onelevel/@!4444

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$onelevel/@!1111

2. Proposal for curly brackets to specify filter; proposal for $literal, $relational, $contextual, $binary in XDI messaging

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$()/(@!4444)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$d!/(data:,2012-05-18T15:15:34.429Z)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/$do/@!4444$do

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0/{JWT-0.6}$token!/(data:,eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczpcL1wvc2VlZC5nbHV1Lm9yZyIsInVzZXJfaWQiOiJtaWtlIiwiYXVkIjoiQCExMTExITAwMDghQTY0QyE0NzVDIiwiZXhwIjoxMzM3MzU3NzM0MTE4LCJveEludW0iOiJAITExMTEhMDAwMCFENEU3Iiwib3hWYWxpZGF0aW9uVVJJIjoiaHR0cHM6XC9cL3NlZWQuZ2x1dS5vcmdcL294YXV0aFwvc2VhbVwvcmVzb3VyY2VcL3Jlc3R2MVwvb3hhdXRoXC9jaGVja19zZXNzaW9uIiwib3hPcGVuSURDb25uZWN0VmVyc2lvbiI6Im9wZW5pZGNvbm5lY3QtMS4wIn0.joij9FsQMofajlERFILyV4G-up0cx_Kc9MUzs1trVHk)

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/{lit=*mike*}$get$literal/@!4444

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$literal$onelevel/@!1111

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$literal$relational$onelevel/@!1111

@!1111!0000!D4E7$msg!e2bdc4de-f129-4d84-9009-3572c37b04d0$do/$get$literal$binary/@!1111

Drummond and Markus both brought up the issue of separating the semantics of scope/depth restriction and the depth of the restriction.

Bill proposed the following (subject to analysis, specific options are from the hip, options mechanism is implmented):

I propose ...$get+level$3

Or even better for parsing purposes ...$get(+depth/$3)(+format/$json)

For not following referrals: $get(+depth/$3)(+format/$json)(+follow/$no)

For limiting to no binaries or other filtering:

$get(+depth/$3)(+format/$json)(+follow/$no)(+filter($include$binary/$false))

# MIKE to list query proposals on the XDI TC wiki together with proposed syntax

# MIKE AND DRUMMOND to document the token format on the TC wiki.

6) NEXT CALL

The next call is next week at the regular time.

xdi message