← Prev in month ← Prev in thread
Next in thread → Next in month →

Minutes: XDI TC Telecon Friday 2012-03-23

From
Drummond Reed <>
Date
2012-03-24T05:01:17+00:00
ID
CAAgCPQfF4xTznj1f2NZrgDeo0ti1Sn2FUQhzHhP=wv=
Thread
Minutes: XDI TC Telecon Friday 2012-03-23
Following are the minutes of the unofficial telecon of the XDI TC at:

Date:  Friday, 24 February 2012 USA

Time:  9:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)

THE ETHERPAD LINK FOR TODAY IS:

     http://xdi.idearpad.org/57

ATTENDING

Mike Schwartz

Drummond Reed

Joseph Boyle

Markus Sabadello

GUESTS

Kari Lippert

Cameron Hunt

1) IDTRUST BUDGET PROPOSAL

Drummond
 had a call with the OASIS IDTrust member section staff.  This resulted 
in revisions to the proposal which we need to review:

  http://wiki.oasis-open.org/xdi/IdTrustProposal

Drummond said the key revisions needed were:

Clarification that deployment of the public test servers was a key step towards finishing the XDI 1.0 spec suite.

Clarification on the breadth of involvement of TC members.

Setting
 a deliverable date of the end of 2012, producing a final report at that
 time, and then optionally applying to renew in 2013.

There was a consensus that the proposal was ready to submit.

# DRUMMOND to send email to Dee.

2) OPEN SOURCE PROJECT UPDATES

Mike
 reported that the OpenXDI Project implemented binary storage, so that 
if a datatype is specified in the value of the data: URI, then it is now
 stored in a binary LDAP node. 

Mike
 also reported that no code change to OxServer or OxGraph is necessary 
to support literal contexts. It will result in a change to OxModel. The 
nested roots work is still waiting.

Markus
 reported that he's been doing some work on XDI Squared, and is next 
looking at implementing it on the Freedom Box, as there is a thread on 
the VRM mailing list about p2p usage of VRM.

Drummond
 said Phil Windley has published a blog post about how KRL (Kinetic 
Rules Language) is going to add XDI support, so that KRL will be operate
 on a consistent semantic data interchange layer.

  http://www.windley.com/archives/2012/03/krl_data_and_personal_clouds.shtml

This
 is very encouraging from both an adoption and engineering standpoint, 
as Phil is very well recognized as a technology pioneer.

# MARKUS, MIKE, DRUMMOND to create a page on the XDI TC wiki with a directory of the XDI open source projects.

3) UPDATED XDI GRAPH PATTERN DOCUMENT

Drummond uploaded a new version that solves one additional key issue:

  http://www.oasis-open.org/committees/download.php/45530/xdi-graph-patterns-2012-03-22.pdf 

The
 key issue was how to semantically distinguish single-valued contexts 
from multi-valued contexts. This not only makes it possible to 
algorithmically compose XDI addresses, but makes XDI dictionary  
construction much easier. Drummond showed examples of both single-valued
 and multi-valued contexts, and the initial reaction was positive.

4) NESTED ROOT CONTEXTS

Mike asked about the use cases for nested root contexts. Drummond clarified the constraints:

Root nodes can only be subcontexts of other root nodes.

Every local graph still has only one local root node whose XDI address is (). All other root nodes must be nested under this.

The
 primary use case is XDI discovery, i.e., the ability to ask one local 
graph for metadata about another local graph, e.g., its URI(s). Such 
metadata could be considered cached, or it could be fully subscribed, 
since it is essentially a remote copy of self-description data.

5) XDI QUERY

Mike
 Schwartz and Yuriy Zabrovarnyy sent an email outlining why they  don't 
believe XML Path & JSON Path are good models on which we should 
based XDI Query:

  http://lists.oasis-open.org/archives/xdi/201203/msg00036.html

Mike
 clarified that having an XDI Path capabiility could be very useful, but
 on the client side, not on the server, i.e., it is much more feasible 
to implement on a return graph. 

It also needs to as efficient as possible on the network.

#
 MIKE will post a proposal on the XDI TC wiki and send an email to the 
list with a link for discussion. We will make this the focus of next 
week's call.

6) NEXT CALL

The next call is next week at the regular time.
← Prev in month ← Prev in thread
Next in thread → Next in month →