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: Re: [xdi] Minutes: XDI TC Telecon Friday 2014-01-17

Hi Dan,

On Fri, Jan 24, 2014 at 8:14 PM, Dan Blum <dan@respectnetwork.net> wrote:
Hi Markus,
Sorry that some of us are missing the XDI call today :-)

No problem, I think we made pretty good progress with Peter's help today on the two main topics we had on the Agenda.

I wanted to give you some feedback on part 2 of the tutorial which I saw from last week's minutes.
Overall, it looks good and is pretty easy to follow.
I have the following suggestions:

1) Use a larger font, the text is very small and there's lots of white space on the screen.

I'd like to keep the text size consistent, so that it doesn't get bigger and smaller between pages that have more or less content.
It probably also depends on the screen resolution, I think I didn't make the CSS flexible enough.

2) On step 3, in the narrative on the right, when you say the diagram has an "entity collection" add in parentheses the name of the node that is the collection *alice[+event] and perhaps comment that it is the [ and ] that indicate presence of a collection

Thanks, but the [ and ] symbols are explained on step 2, and I think on step 3 it's pretty obvious what the collection is :)


On Thu, Jan 23, 2014 at 3:28 PM, Markus Sabadello <markus.sabadello@xdi.org> wrote:

XDI TC Minutes

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

Date:  Friday, 17 January 2014 USA
Time:  09:00AM - 10:30AM Pacific Time (16:00-17:30 UTC)


Drummond Reed
Les Chasen
Markus Sabadello
Phil Windley
Joseph Boyle


Andy Dale



XDI Tutorial

Markus has completed Part 2 of the XDI Tutorial:


Drummond was ecstatic about seeing Part 2. His only feedback was for the diagrams to use the new notation format, which Markus had in fact done for Part 1.


Next Steps on Working Drafts

We will discuss the additions/corrections we want to make to produce XDI Core 1.0 Working Draft 02, including:

  • MIME types for serialization formats.

  • Formatting improvements.

  • Adding missing sections.

    • Equivalence Relations ($is, $ref, $rep)

    • Graph notation format

  • Improved Github merging process.

First, we talked about whether we can have a browser-ready version of the spec that can be referenced from the OASIS servers.

#JOSEPH will follow up with Chet to see if we can get a browser-ready version on OASIS servers.

We next discussed the division of the Equivalence Relations section between XDI Core and XDI Messaging. We agreed that the basic rules belong in XDI Core, and that the equivalence rules for operations belong in XDI Messaging.

We then discussed the graph notation format. Drummond said that he wants to include the information from the XDI graph model document front matter—he showed an example. There was consensus we should add this section. Joseph noted that we can include SVG graphics format.

#JOSEPH will review and make a recommendation about where the graph notation format definition section should go.

Drummond summarized that once we perform the action items above, we should be ready to publish Working Draft 02. Our goal should be to have Working Draft 02 be functionally complete.

The “Unauthorized $ref Problem” and “Unbounded $set Problem”

We have talked about these many times but not reached a definitive solution. Let’s review the approaches we have considered so far, with a special focus on the new authority-relative link contract patterns.

“Forwarding” of Messages by a Server

If the target peer root specified by a message does not match the peer root that is authoritative for the graph the message is sent to, the message can be “forwarded” to the authoritative server for the peer root. See the following two lines from the XdiMessagePatterns page:

#1:  FROM                  <--from-peer-->/$set/<--from-->[$msg]<--msg-id-->
#2:  TO                    <--from-->[$msg]<--msg-id-->/$is()/<--to-peer→


None scheduled.


The decision queue stack is shown on the following three auto-generated Category pages:




See also this list of proposals that need to be developed:



The next call is next week at the regular time.

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