[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Minutes: XDI TC Telecon Friday 2013-12-06
Following are the minutes for the unofficial telecon of the XDI TC at:
Date: Friday, 06 December 2013 USA
Time: 09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)
Joseph published XDI Core 1.0 Working Draft 01.
Animesh shared thoughts on how one could do efficient queries on an XDI graph. Assuming a graph containing a large amount of e-mails plus metadata (from, to, subject, timestamp, etc), one might want to retrieve let’s say all e-mails sent by Markus within the last 7 days. In the graph, the e-mails would probably be modeled as entity members of a large collection, e.g. [+email]. With the $get operations, it would only be possible to retrieve ALL e-mails, or a single e-mail (if its address in the graph is known). There is no efficient way to perform the query described above. However, it would be possible to add auxilliary “index” collections to the graph, which could contain $ref links to all the e-mail entities sent by Markus. This way a query to retrieve all e-mails sent by Markus would simply be a $get on the “index” collection, and the XDI server would process the $ref links. We also noted the concept of message policies, which can be used to attach client-side conditions to an XDI operation and therefore resemble a query language.
Everybody on the call expressed their excitement about the first published XDI spec draft since the inception of the TC. Although nobody on the call had had time to read through the whole draft, we conducted a quick walk-through and discussed certain sections in more detail.
Andy had a question about the difference between contextual statements and relational statements. Markus explained that contextual statements are usually considered “implied” and therefore not serialized.
Markus asked what in Joseph’s opinion would be areas of the draft that still need work, if any. Joseph answered it may still be required to add an ABNF rule to describe relational predicates. Joseph also explained that the sections on serialization formats may need more work. For example, the multi-line version of the XDI DISPLAY format, which has been used a number of times on wiki pages etc., is not covered.
This resulted in a longer discussion on “short notations” of XDI inner roots in the various serialization formats, which might also require adjustments to the ABNF.
We also talked about MIME types. We agreed the Core spec should define MIME types and their parameters for the various serialzation formats, whereas the Messaging spec should specify how these MIME types are used in XDI Messaging.
After publication of the draft, Markus had submitted a Git pull request to correct a typo in the Core spec, and Joseph has fixed minor issues in the Messaging spec. We discussed the Git collaboration process and how it suits our needs, and we agreed we were happy with the current set up.
# ALL to do a close read of the draft and provide Joseph and Drummond with feedback.
We decided to postpone discussion of this topic to next week, to get Drummond’s input.
We decided to postpone discussion of this topic to next week, to get Drummond’s input.
We did not have time to discuss this topic.
We did not have time to discuss this topic.
None scheduled.
The decision queue stack is shown on the following three auto-generated Category pages:
https://wiki.oasis-open.org/xdi/CategoryLastCall
https://wiki.oasis-open.org/xdi/CategoryCurrent
https://wiki.oasis-open.org/xdi/CategoryHighPriority
See also this list of proposals that need to be developed:
https://wiki.oasis-open.org/xdi/XdiPendingIssues
The next call is next week at the regular time.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]