XDI TC Agenda

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

Date: Friday, 20 September 2013 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

AGENDA

NEWS & UPDATES

Report from Privacy/Identity/Innovation 2013

Drummond will report on some key trends and feedback coming out of the conference this week in Seattle.

PRESENTATIONS/DISCUSSIONS

Progress on Working Drafts

Confirm our decision on the spec change commit progress.

Report on progress on XDI Core and XDI Messaging.

Signatures

Drummond has written a proposal for cryptographically signing XDI graphs.

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

Although there are many use cases for signed graphs, the initial use case this is needed for is verification of XDI messages.

Transactional Integrity in XDI Messaging

This topic was raised in last week’s telecon when we discussed nesting of collections. It is critical for defining interoperable, predictable behavior of XDI servers.

Link Contract Initiation

If there is time, continue our discussion of link contract initiation, focusing on the structure of the three related versions of a link contract:

A link contract template.
A link contract instance.
A meta link contract.

See https://wiki.oasis-open.org/xdi/LinkContractPattern

DECISION POINTS FOR THIS CALL

Dictionary Syntax

As Drummond works on the XDI Core spec, one inconsistency that has been bothering him is that, after our syntax simplication last spring, all XDI context functions used exclusively bracket syntax EXCEPT dictionary definitions.

(=markus) <== root

[+passport] <== collection

<+tel> <== attribute

{foo} <== variable

$(+passport) <== definition

It would be cleaner and easier if there was also a uniform bracket syntax for definitions. One option would be to use double brackets:

[[+passport]] <== definition

Markus suggested another option of using pipes:

|+passport| <== definition

And one more thought is not to use brackets at all but define the a dictionary context by using a single instance of a class context symbol. This could be either + or $, i.e.:

++passport <== definition

$+passport <== definition