OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Minutes: XDI TC Telecon Thursday 2012-01-05


Following are the minutes of the unofficial telecon of the XDI TC at:

Date:  Thursday, 05 January 2012 USA
Time:  1:00PM - 2:30PM Pacific Time (21:00-22:30 UTC)

ATTENDING

Mike Schwartz 
Joseph Boyle
Markus Sabadello
Drummond Reed

REGRETS

Giovanni Bartolomeo


THE IDEARPAD LINK FOR TODAY IS:
     http://xdi.idearpad.org/50



1) IDTRUST BUDGET

No further word yet.


2) OPENXDI UPDATE

Mike said they are done with the .2 version and will have a zip distribution next week.

The focus of the next release is optimizations, particularly $get (see agenda item below).

The other change is that OxGraph has added a third field for directing messages. This field accepts an XRI used to identify the physical network endpoint ("physical graph") at which a logical XDI graph is located.

Drummond pointed out that this should not actually require two XRI fields, because the first XRI represents the XDI identity of the physical graph to query, and the second XRI represents the target node in the logical XDI graph stored at that network location. These two XRIs should should be expressible together as a single XRI, with the second XRI in the context of the first.

Drummond explained the solution of modeling all representations of physical graphs as XRI cross-references (i.e., in parentheses). This allows the logical XDI graph to self-describe the network endpoints at which sections of it are stored. This enables XDI discovery to be used across the entire distributed XDI network.

# DRUMMOND to do a writeup and diagram of how physical and logical XDI graph modeling works in both XRI syntax and in the visual representation of the XDI graph model.

Mike also showed a new utility called OxServer Build that builds the OpenXDI components for an LDAP server.


3) SELF-CONTRACT ISSUE ($self$do)

We briefly continued discussion of the bootstrap permissioning issue. See:

  http://lists.oasis-open.org/archives/xdi/201112/msg00010.html

Mike showed how self-contracts now work in the OpenXDI implementation.

Drummond explained how he would simplify them at the root level to just ()$do (i.e., drop $self). 

# DRUMMOND to write this up.


4) MESSAGE ORIGINATION ISSUE

Drummond said that the combination of physical/logical graph modeling and self-contracts solves the message bootstrap issue he has been working on, and now he just has to write it up. He is going to work hard to do that before next week's call.

# DRUMMOND to write this up.


5) PROPOSALS FOR OPTIMIZING $GET

Mike has sent several suggestions to the list over the break about  optimizing $get queries with $filter, $scope, etc. to get more of the  kind of graph query functionality provided by LDAP and SQL. He has written up his suggestions at:

  http://ox.gluu.org/doku.php?id=xdi:get

He explained that in LDAP, query scope is controlled by specifying:
    •    The starting point
    •    The scope
    •    The filter

Mike went through his writeup to explain his proposals for $filter, $scope, and $type.

Drummond mentioned that earlier discussions about XDI query capabilities (of which there have been a number) resulted in ideas put forth by Giovanni and Bill for variables and $words for qualifying variables. That proved to be relatively modest yet quite powerful -- it was implemented by Markus in his XDI Query utility.

Joseph pointed out that what we need is essentially the XDI equivalent of SPARQL (http://www.w3.org/TR/rdf-sparql-query/ ). He said there are also other languages for graph databases like https://github.com/tinkerpop/gremlin/wiki. Gremlin has native Java suppert, so you would only need to implement a Blueprints interface to the XDI graph and then Gremlin could work on it.

# ALL - Read through Mike's wiki pages.

# MIKE, DRUMMOND, OTHERS: Find/consolidate any pages on the XDI TC wiki on XDI queries and add Mike's new proposals.


6) 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]