Re: [xri] Agenda:Joint XRI & XDI TC Telecon 10AM PT Thursday 2007-09-27

["Markus Sabadello" <markus.sabadello@xdi.org>]

It hurts but I won't be able to be on the call today. Here's a quick summary of what I think about this:

1) Dropping authority Refs in favour of default-SEP-Refs feels a bit uncomfortable, but why not.

2) Following only lower priority Refs, ignoring the equal ones, sounds good. The equal priority ones would still be tried in case of a network error, right? I think the resolver should report an error back to the application, if "for any given priority for which at least one Ref exists none of the Refs of this priority could be followed". So if you have ONE Ref with priority 5, and cannot follow it, you report an error. If you have THREE Refs with priority 5, and can follow none of them, you also report an error.

3) New way of nesting XRDSes also sounds ok.

4) Try all Refs to find a SEP (breadth AND depth).

5) Turning the refs parameter into an int sounds good. I especially like the possibility of finding ALL matching SEPs, that's a nice idea. What if I wanted no limit there? Would I put 999999 into the parameter? To make life easier for implementers, maybe minimum / maximum values should be specified (such as -32768 to 32767).

Markus

On 9/27/07, Drummond Reed <drummond.reed@cordance.net> wrote:

Following is the agenda for a joint unofficial telecon of the XRI and XDI
TCs at:

Date:  Thursday, 27 September 2007 USA
Time:  10:00AM - 12:00PM Pacific Time

Event Description:
Weekly unofficial joint call of the XRI and XDI Technical Committees.

TO ACCESS THE AUDIO CONFERENCE:
    Dial In Number: 571-434-5750
    Conference ID: 5474


AGENDA

1) REVISED REF PROCESSING PROPOSAL
Based on the very active email thread, followed by in-person discussions
between XRI TC members and XRI resolver implementers at Digital ID World, a
page summarizing all proposed changes to ref processing has been posted to:

         http://wiki.oasis-open.org/xri/XriCd02/RefProcessing

Please review it before the call if you have time -- coming to closure on
this so it can be revised in ED06 is our highest priority.

2) CLOSURE ON XML NAMESPACING FOR XRD ATTRIBUTES

The proposal is to NOT declare namespaces for XRD attributes (which is what
the spec currently says normatively but does not show correctly in
examples). We will confirm there is consensus on this.


3) SCHEDULE FOR XRI RESOLUTION 2.0 WD11 ED06 AND COMMITTEE DRAFT VOTE

We will review the remaining action items at...

        http://wiki.oasis-open.org/xri/Xri2Cd02/ResWorkingDraft11

...and assign tasks to complete ED06 ASAP so we can prepare for a Committee
Draft vote.