[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Agenda: XDI TC Telecon Friday 09:00 - 10:30AM PT 2015-03-06
Following is the agenda for the unofficial telecon of the XDI TC at:
Date: Friday, 6 March 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:
IRC Channel: irc://irc.freenode.net:6667/xdi
Drummond would like to review a new draft of the XDI Graph Model section of XDI Core with TC members. He will upload it Kavi before the call. You can see that section in the outline:
https://wiki.oasis-open.org/xdi/CoreSpecOutline
As Drummond and Joseph and Markus work on the ABNF for the Core spec, they are considering a new way of standardizing immutability that they want to discuss with all TC members.
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 $copy operation? In which spec?
What will push (pub/sub) connections require in terms of additional link contract semantics?
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:
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
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
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]