xdi message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Minutes: XDI TC Telecon Friday 2012-11-09
- From: Drummond Reed <drummond.reed@xdi.org>
- To: OASIS - XDI TC <xdi@lists.oasis-open.org>
- Date: Tue, 13 Nov 2012 00:58:57 -0800
Following are the minutes of the unofficial telecon of the XDI TC at:
Date: Friday, 09 November 2012 USA
Time: 9:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)
THE WEBEX INSTRUCTIONS FOR TODAY ARE:
ATTENDING
Bill Barnhill
Phil Windley
Joseph Boyle
Markus Sabadello
Drummond Reed
GUESTS
Animesh Chowdhury
THE ETHERPAD LINK FOR TODAY IS:
***** NEWS & UPDATES *****
--- INTERNET IDENTITY WORKSHOP AND SIBOS REPORT
* Phil did a screencast of the KRL personal cloud desktop and an in-depth session on KRL/XDI integration featuring the KRL XDI module developed by Mark Horstmeier
* Markus suggested that we should do more focused screencasts
* Drummond talked about the Forever cloud address book mobile app prototype that he presented at Sibos.
--- XDI IMPLEMENTERS CALL
Markus shared that he and the Neustar team has set up a weekly open telecon for XDI implementers. It will be Tuesday at 11AM PT/2PM PT. He sent info to the list:
We also discussed the need to keep all XDI spec issues in the province of the XDI TC.
***** DECISION POINTS FOR THIS CALL *****
--- $IS RESOLUTION
We discussed the $is and $xis proposal that Drummond and Markus raised on the list as defining two different forms of equivalence statements in the graph, one that is transparent and one that is opaque.
Phil brought up the point that it would be better to extend the $is predicate rather than have two predicates. Drummond strongly agreed with this suggestion.
Markus explained that there are actually 3 different use cases from the client perspective:
- Requesting that the server follow $is statements and return them in the response ("transparent" or "expanded" responses)
-
Requesting that the server follow $is statements but not return them in the response ("opaque" or "compressed" responses)
-
Requesting that the server not process any $is statements ("no-follow" responses)
Markus preferred the terms "public" and "private" instead of "transparent" and "opaque".
***** DECISION POINT QUEUE REVIEW *****
The decision queue stack is now shown on the following three auto-generated Category pages:
See also this list of proposals that need to be developed:
We agreed that we need to resolve the $is resolution issue first, then we will move back to the Messaging proposal.
***** NEXT CALL *****
The next call is next week at the regular time.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]