Date: Thursday, 15 December 2011 USA
Time: 1:00PM - 2:00PM Pacific Time (20:00-21:30 UTC)
ATTENDING
Mike Schwartz
Markus Sabadello
Drummond Reed
Joseph Boyle
THE IDEARPAD LINK FOR TODAY IS:
http://xdi.idearpad.org/49
1) IDTRUST BUDGET
Mike reported that the initial feedback was positive, but nothing definitive yet.
2) OPENXDI UPDATE
Mike gave an update that several more key tasks we accomplished last week, including normalizing XRIs to lowercase and streamlining addressing in the LDAP persistence. He also discussed upcoming features.
3) BOOTSTRAP PERMISSIONING ISSUE
Mike explained that one issue the OpenXDI team has been debating is how to bootstrap the root link contract. Mike favors allowing self-referential link contracts implicitly. Drummond pointed out that while this may make sense for root nodes, it doesn't work for deeper nodes because there are too many examples where the XRI used to identify a node inside another context would not give the authority represented by that XRI permission to edit that branch of the graph.
For example, if =drummond graph stores an =mike node (contextually producing the XDI address =drummond=mike), that does not mean =mike has permission to edit the branch at that node. That branch may simply be storing =drummond's notes about =mike, which can edit (or give a link contract to edit).
Drummond does favor a compact form of link contract that expresses a $all or $do$all permission for the authority identified by a context node.
# ALL: Work on suggestions for how to express such a compact self-referential link contract.
4) MESSAGE ORIGINATION
Drummond shared some thoughts about how to track the graph originating a message. His example when an XDI server wants to track the messages sent to it by an XDI client that might represent the same XDI authority (for example, a person sending an address book update from their own XDI client to their own XDI server). In that case, the server needs to know the {from-endpoint} for the message, not just the sender (which is the user). The server also needs to be able to associate this {from-endpoint} with the message itself, which is not currently supported on
http://wiki.oasis-open.org/xdi/XdiMessagePatterns, because there the {from-endpoint} is expressed as a relation to the root of the message graph, not to the message.
Drummond explained that this is really another instance of the bootstrap problem, because the message itself is an implicit operation ($add) on the target graph for the message itself if the target graph is auditing messages.
So what we need to add to the XDI message template is a way to express the originating graph of an XDI message as part of the message itself.
#DRUMMOND to work on this and email a proposal to the list.
5) NEXT CALL
We decided to take a two-week break due to the next two Thursdays being so close to Christmas and New Years. The next call will be Thursday January 5 at the regular time.
Happy Holidays to everyone on the TC.