XDI TC Notes

Following are the notes of the unofficial telecon of the XDI TC held on:

Date: Monday, 30 November 2015 USA
Time: 10:00AM - 11:30AM Pacific Time (17:00-18:30 UTC)

The TC operates under a standing rule approved 17 July 2008 under which the TC does not hold regular official meetings and conducts all business by electronic ballot only. Unofficial weekly meetings are held to enable discussion among members but no business is conducted nor actions taken.

ATTENDING

Peter Davis
Markus Sabadello
Les Chasen
Drummond Reed
Joseph Boyle
Kapil Vats

REGRETS

Update on Publishing XDI Core 1.0 Committee Specification Draft 01

Chet and Paul have sent a list of all the changes needed to transform Working Draft 06 into CSD 01.

https://lists.oasis-open.org/archives/xdi/201511/msg00011.html

Drummond and Joseph reviewed the changes and agreed to work together to implement them.

# ACTION ITEM: DRUMMOND AND JOSEPH to produce the CSD01 files for Chet and Paul to review.

XDI Messaging, Bindings, Push, Connections

Markus will continued his report on progress in the XDI Messaging, Bindings, Push, and Connections drafts.

Markus covered a number of updates he made since the last TC call:

Changed the terminology “light messaging response” and “full messaging response” to “result graph” and “response message”
Added section on variable assignment. We discussed whether this should be part of XDI Messaging or XDI Core, since it may not be specific to messaging.
Added basic outline to XDI Connections
Added some content to XDI Push
Added section “Nested Messages” to XDI Messaging
Added section “<$deref>” to XDI Messaging. We discussed the relation between this section and similar sections in XDI Core.
Added section “correlation statement” to XDI Messaging. We discussed how both request messages and response messages can be correlated. We also discussed whether there can be only one or multiple correlation statements per message, and whether they can be specialized.

Markus then explained that the $connect, $send, and $push operations share some common functionality and are related to each other. While there are separate specification documents for $connect (XDI Connect) and $push (XDI Push), there is no separate specification for $send. Instead, this is covered by the “Nested Messages” section in XDI Messaging.

We discussed this and came up with three possible alternatives:

Not change anything, and leave the spec structure as described above
Move $send / “Nested Messages” to a separate spec
Move $connect and $push into the XDI Messaging spec, and delete XDI Connections and XDI Push

Markus said the problem with the third alternative could be that $connect and $push are closely related not only to XDI Messaging, but also to XDI Policy (link contracts).

NEXT REGULAR CALL