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

XDI TC Agenda

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

Date:  Friday, 19 December 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 

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

XDI/RDF

Update from Hubert, Peter, Les?

Can we come up with a proposal for the name and maybe an outline/abstract for this spec?
Graph Model Structure
Drummond and Joseph have worked more on the GraphModelStructure wiki page and the tree view of node types:

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

Let’s discuss if all constructs in the tree view are actually needed.

Markus has some thoughts on requirements for syntax and use of variables.

XDI Policy and Connections

Let’s continue to discuss XDI connection requests, connection invitations, link contracts, templates, community contracts, requester contracts, etc.

Open topics:

Review what happens when a connection invitation is processed.

What do “deferred” connection requests look like, and how are they processed? How do we handle cases where user interaction is required?

Template versioning - what if the Template Authority changes a template? How does this affect existing LC instances? Should versioning for LC templates be mandatory?

Topics discussed previously:

Discuss different ways for an RA to receive a copy of a new link contract instance

Challenge of correlating message requests and responses

Issue related to having multiple link contract instances based on one link contract template (how to algorithmically determine the address?)

Insight: A link contract instance may be used by many authorities that can satisfy a policy _expression_ (e.g. groups, roles, organization membership)

Insight: Just like there can be a connection invitation, there can also be invitations for any other operation, e.g. $get

Collection of Documents:

XDI Policy draft spec:

https://www.oasis-open.org/committees/download.php/54276/XDIPolicyDraft%20v8.docx

XDI Connections draft spec:

https://www.oasis-open.org/committees/download.php/54279/XDI%20Connections%20V1.docx

Link Contract Instantiation:

https://www.oasis-open.org/committees/download.php/54205/LinkContractInstantiation25Sep2014.pdf

Community Link Contracts:

https://www.oasis-open.org/committees/download.php/54287/Community%20link%20contracts%20-%20Google%20Docs.pdf

Berkeley Deep Dive notes:

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
Transactional integrity
We have discussed the topic of transactional 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
NEXT CALL
The next call is next week at the regular time.