Minutes: XDI TC Telecon Friday 2012-10-12

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

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

Date:  Friday, 12 October 2012 USA

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

ATTENDING

Markus Sabadello

Giovanni Bartolomeo

Les Chasen

Joseph Boyle

Drummond Reed

Phil Windley

REGRETS

Bill Barnhill 

THE ETHERPAD LINK FOR TODAY IS:

     http://piratepad.ca/Ur8QCujCAm

***** NEWS & UPDATES *****

--- PREP FOR UPCOMING INTERNET IDENTITY WORKSHOP

We'll discuss XDI-related sessions we are planning.

• Markus is planning to show the personal cloud desktop as a demo for Demo Day, and also as a conference session

• Markus may also do a dedicated session on the XDI2 connector architecture

• Markus is also planning a Freedom Box demo

• Phil is planning a cloud desktop session too

• Drummond may do an XDI dictionary and connector session

• Drummond is also planning a Respect Network Founding Partners session

***** PRESENTATIONS *****

None scheduled.

***** DECISION POINTS FOR THIS CALL *****

This week's decision queue is the following set of proposals:

--- MULTIPLICITY (DRUMMOND)

   https://wiki.oasis-open.org/xdi/XdiMultiplicity

   https://wiki.oasis-open.org/xdi/XdiMultiplicity/Discussion

We are still closing the loop with Bill, who was not able to attend today's call. Markus and Drummond will try to have a dedicated call with him next week.

--- XDI MESSAGING PATTERNS (MARKUS)

   https://wiki.oasis-open.org/xdi/XdiMessagePatterns

This is the formal proposal for the structure of XDI messages that we have long been using this wiki page to document.

Open issues that we discussed today:

• Which lines of the message pattern ABNF are required?

• Will message and operation ordering be required?

Discussion of ABNF lines required

• First line - needed for auditing - OPEN ISSUE

• Second line - OPTIONAL (if server URI is known)

• Third line - datestamp - OPEN ISSUE (may be needed for security)

• Fourth line - link contract reference - REQUIRED

• Fifth line - message operation - REQUIRED

Note that if a client does not know the link contract (fourth line), it can use the well-known public link contract ($public$do).

Discussion of message and operation ordering:

• Markus proposes that message and operation ordering be OPTIONAL for the client and REQUIRED for the server (i.e., if a client orders messages or operations, the server MUST follow the order)

• If the client does not specify ordering, the rules currently on the wiki page apply.

***** DECISION POINT QUEUE REVIEW *****

No change - the priority is still to completely close on Multiplicity, and then on Message Patterns, followed by each Message Operation.

***** NEXT CALL *****

The next call is next week at the regular time.