XDI TC Notes

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

Date: Tuesday, 13 December 2016 USA
Time: 9:00AM - 10:00AM 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

Markus Sabadello
Drummond Reed
Joseph Boyle
Les Chasen

NOTES

Beginning Work on XDI Core 1.0 Committee Draft 02

Since XDI Core 1.0 Committee Draft 01 was passed in October of 2015, we have kept a list of proposed revisions at:

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

Drummond just updated the wiki page to add the three new normative revisions (the “Any” entity type, the DID scheme, and changing serialization to JXD) that we have discussed in the past few weeks. We will discuss the steps needed to move to Committee Draft 02.

Markus has published a document about JXD format that describes it and includes many examples, but is not yet a formal spec definition:

https://www.oasis-open.org/committees/download.php/58945/jxd%20v3.pdf

XDI Link Contracts

Per his action item from last week’s meeting, Markus posted a first draft of the Link Contract spec:

http://xdi.org/xdi-spec-docbook/xdi/xdi-link-contracts-1.0/xdi-link-contracts-1.0-wd01.xml

It is still an early draft, however Markus walked us through the content and there is a huge amount that is covered, including both simple and complex link contract templates and examples. Some of the sections however need more work, e.g. sections on permissions and details on the link contract evaluation process.

Drummond noted that we need to define the time-based properties, such as a created timestamp and expires timestamp.

Drummond also noted that all the examples are currently in XDI statement format, so there is considerable work to be done to include them all in JXD.

We also noted several places where the examples are out of date, but those will be easy to fix.

Besides the JXD examples, the biggest chunks of effort will be to:

Fully specify the rest of the link contract vocabulary around usage (currently the $for branch—Drummond is thinking we might want to rename it the $usage branch).
Add examples that walk through typical link contract scenarios.
Add at least a few visual diagrams of link contracts.

As with XDI Messaging, Link Contracts still has a dependency on Core, in particular on the specification of JXD serialization, so as discussed above, that has to be considered in our staging of specs. Messaging and Link Contracts also reference each other, e.g. when it comes to specifying $connect operation or deferred messages.

NEXT REGULAR CALL

WE ARE TAKING A HOLIDAY BREAK FOR THE NEXT TWO WEEK. The next call will be Tuesday January 3 2017 at the usual time (9AM PT). The link to where agenda items can be posted for the next meeting is: https://docs.google.com/document/d/19oDl0lbb56Grehx2a5flZnhrgnua5l8cVvC_dJ8fTXk/edit?usp=sharing

xdi message