Minutes: XDI TC Telecon Friday 9:00-10:00AM PT 2012-02-24

[Drummond Reed <drummond.reed@xdi.org>]

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

Date:  Friday, 24 February 2012 USA

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

ATTENDING

Giovanni Bartolomeo 

Bill Barnhill

Mike Schwartz

Drummond Reed

Markus Sabadello 

Joseph Boyle 

GUEST

Jim Fournier 

THE GOTOMEETING FOR TODAY IS:

     https://www2.gotomeeting.com/join/969244355

THE IDEARPAD LINK FOR TODAY IS:

     http://xdi.idearpad.org/55

Please preface each of your comments with your name to facilitate

transcription into the minutes.

AGENDA

1) SPECIAL GUEST: JIM FOURNIER

Jim recently joined the board of XDI.org and is leading an initiative at Planetwork that will heavily depend on XDI. Jim is interested in building on XDI infrastructure and is working with several entities on proposals for NSTIC.

2) XDI LINK CONTRACT PROPOSAL

Mike shows two graphs for controlling access to part of the tree. One graph shows one link contract per operation (current standard); second graph shows one link contract with multiple segments per operation.

# MIKE to send copies of the diagrams to the list.

3) IDTRUST BUDGET PROPOSAL

We discussed the need for some TC members to be able to travel to events like EIC or IIW, however OASIS does not fund personal travel.

Markus is still willing to set up a demo server. Bill is willing to help with that. So is Joseph. The server could run on something like EC2 so the hosting costs would be relatively minimal.

We also discussed using funds for marketing, including various industry events.

On Feb 10, Dee wrote

-----Original Message-----

From: Dee Schur [mailto:dee.schur@oasis-open.org] 

Sent: Friday, February 10, 2012 4:10 PM

To: 'Michael Schwartz'

Cc: 'Markus Sabadello'; 'Scott McGrath'; 'Drummond Reed'; 'Jane Harnad'; 'Sabo, John T'

Subject: RE: new IDTrust proposal for XDI?

Importance: High

 

 So I am clear -- do you want me to run a StC ballot for a fee of 4.5K USD to cover the cost associated with:

 

> One of the ideas (which we already briefly talked about during the

> call) was to set up a server (e.g. http://demo.xdi.org) where anyone 

> could see how XDI works, try out different XDI implementations, and 

> run their own code against them. I.e. this would be a public XDI 

> server rather than the private inter-op that we originally proposed.

There was a consensus that we should properly scope the proposal.

Bill asked to include EzXDI, and open source server to be hosted ezxdi.com.

# MARKUS to contact Dee Schur to see about completing this proposal.

4) OPEN SOURCE PROJECT UPDATES

# MARKUS will post some questions on the wiki and send a note to the email list.

Mike said that the OpenID Connect interop is next Friday after IIW; he will be attending. This has been the focus of the OpenXDI team recently. Mike is hoping that by supporting OpenID Connect, customers who want OpenID Connect will help bring revenue to support other XDI development.

Drummond said that he is lining up commitments to the integrated KRL/XDI server that Phil Windley and Kynetx will be developing, and that he expects the work to begin in March.

5) SPECS REPOSITORY

Bill published a page on the wiki with his proposed process for spec drafting:

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

This lets us distribute the process of editing and having all edits sync to the OASIS SVN repository handling the canonical copy.

6) NEXT CALL

Proposed standard agenda item, ongoing: 

• State of the Repos: Bill gives a report on Github activity, including pull requests in process, pull requests merged, and new repos under TC organization on GitHub

  

Initial repos planned:

• XDI-Graph-Model

• XDI-Query

• XDI-Dictionary

• XDI-Link-Contracts

Mike suggested the following work topics in priority order:

• Query

• Graph model enhancements (literal contexts, nested roots)

• XDI discovery definition

• Link contract enhancements

• Dictionary

Drummond suggested that we create a page on the wiki that reflects our current priority list - he will try to do this before the next call.