XDI TC Agenda

Following is the agenda for the unofficial telecon of the XDI TC at:

Date: Friday, 17 April 2015 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)

THE LINK TO THIS AGENDA AND LIVE MEETING MINUTES IS:

https://docs.google.com/document/d/1t5Mx0ITqJdLwo8wM5GD9lcqehgbgnrhk-k2sERwc7J0/edit

THE WEBEX INSTRUCTIONS FOR THIS MEETING ARE:

1. Go to https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&RT=MiMxMQ%3D%3D

2. If requested, enter your name and email address.

3. If a password is required, enter the meeting password: 5474

4. Click "Join".

5. Follow the instructions that appear on your screen.

To view in other time zones or languages, please click the link:

https://neustar.webex.com/neustar/j.php?ED=203186612&UID=1364257662&PW=NN2Y2NzAxZTVj&ORT=MiMxMQ%3D%3D

IRC Channel: irc://irc.freenode.net:6667/xdi

AGENDA

NEWS & UPDATES

PRESENTATIONS/DISCUSSIONS

Review of the XDI Core Spec

Drummond uploaded another draft section of XDI Core 1.0—the Collections section (which is NOT marked with Track Changes because it’s all new). There are also a few text revisions to earlier sections marked with Track Changes.

https://www.oasis-open.org/committees/document.php?document_id=55472&wg_abbrev=xdi

You can see where this fits in the full outline of XDI Core 1.0:

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

XDI Messaging and Bindings

We will review Markus’ latest work on XDI Messaging 1.0 WD03 and XDI Bindings 1.0 WD03:

http://xdi.org/xdi-spec-docbook/xdi/xdi-messaging-1.0/xdi-messaging-1.0-wd03.xml

http://xdi.org/xdi-spec-docbook/xdi/xdi-bindings-1.0/xdi-bindings-1.0-wd03.xml

Local Name Syntax Issue

At last week’s F2F meeting at Internet Identity Workshop in Mountain View, CA, the TC members present discussed but did not reach consensus on the local name syntax issue. Drummond has done a writeup on this issue to help us move to closure:

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

$push Instead of $copy?

In recent discussions on the XDI2 open source project call, it was suggested that $push might be a better dollar word than $copy for the XDI data synchronization operation.

Websocket Binding, Publish/Subscribe, $push

If there is time, Markus can show a proof-of-concept of a Websocket binding. There are several topics to discuss:

Is there agreement that we should publish a Websocket binding? In which spec?
Will this require defining more about the $push operation? In which spec?
What will push (pub/sub) connections require in terms of additional link contract semantics?

NEXT CALL

The next call is next week at the regular time.

xdi message