Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2014-09-05

XDI TC Agenda

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

Date:  Friday, 5 September 2014 USATime:  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 

AGENDANEWS & UPDATESPRESENTATIONS/DISCUSSIONSReport from XDI editors subcommitteehttps://wiki.oasis-open.org/xdi/XdiOneSpecshttps://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook

Link contract instantiation

Let’s continue to discuss link contracts, templates, instantiation, community contracts, requester contracts, etc.

Let’s first figure out how this topic of link contract instantiation should be covered by the XDI specs, maybe a new separate spec called “XDI Authentication and Authorization”?

Dan has uploaded a new version of the XDI Policy draft spec:

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

Notes from a related call on Aug 19 2014 can be found here:

https://www.oasis-open.org/committees/download.php/53921/LinkContractInstantiation17Aug2014.pdf

Notes from a 3 day face-to-face “deep dive” on Aug 27 2014 can be found here:

https://www.oasis-open.org/committees/download.php/53986/xdi%20deep%20dive%202014-8-27.pdf

https://www.oasis-open.org/committees/download.php/53985/linkcontractExamples.pdf

Some topics related to this:

Should the standard practice be to save a copy of the link contract template along with the link contract instance, and send a signed copy of both to the RA, so they are always paired, and an audit trail can see the link contract template display info that was shown to the user?

Template versioning - what if the Template Authority changes a template? How does this affect existing link contract instances?

Are community and requester link contracts required for link contract instantiation to work, or are they “good to have” extras?

Variables and variable collections
We have been using variables such as {$from} or {$msg} or {$do}.

Let’s review the topic of variables in general—which spec should this be covered in?

Let’s discuss variable collections and their syntax. We have seen two options:

[{$do}]!:uuid:1234

and

[{$do}]{!:uuid:1234}

Let’s also discuss how variables actually “work”? What can they stand for, how are they used, what behavior do they trigger, etc?
Transactional integrity
We have discussed the topic of transaction integrity a number of times in the past without reaching a conclusion. This seems to now have new relevance in conjunction with link contract instantiation.

The following document has a section titled “XDI Message Transactional Integrity Notes”, let’s review and discuss:

https://www.oasis-open.org/committees/download.php/53921/LinkContractInstantiation17Aug2014.pdf

(note that this is the same document as the one that covers link contract instantiation)

NEXT CALL
The next call is next week at the regular time.