XDI TC Agenda

Drummond’s document describing the four key differences between the RDF and XDI graph models has resulted in a lot of feedback. Based on this feedback, let’s come up with an outline for a second draft:

https://docs.google.com/document/d/1pkrbCGTbBfyspFu64-DxLiSlvqa_0xCurZx4YZeTARc/edit?usp=sharing

Variables

Continue to discuss variable syntax in order to complete the XDI ABNF as a part of the XDI Core 1.0 spec.

TC call minutes where Les, Markus, and Drummond discussed this:

https://lists.oasis-open.org/archives/xdi/201501/msg00002.html

Markus’ overview of the use of variables in different situations:

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

Drummond’s proposal on differentiating between “simple” and “complex” variables:

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

Also see Drummond’s and Joseph’s recent work on the GraphModelStructure wiki page and the tree view of node types:

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

Also see the 2014-12-19 XDI TC minutes and action items:

https://lists.oasis-open.org/archives/xdi/201412/msg00013.html

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.

xdi message

XDI TC Agenda

AGENDA

NEWS & UPDATES

PRESENTATIONS/DISCUSSIONS

Report from XDI editors subcommittee

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

https://github.com/OASIS-XDI-Technical-Committee/xdi-spec-docbook

Variables

Transactional integrity

NEXT CALL