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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

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


Subject: RE: [xri] XRI TC Telecon Friday 12/16 10AM-11:30AM Pacific


Minutes of the XRI TC telecon 2005-12-16

Date:  Friday, 16 December 2005
Time:  10:00am - 11:30am PT

Event Description:
XRI TC Unofficial Telecon to finish Committee Draft 02 cycle.

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

PRESENT

Dave
Gabe
Drummond
Les
Victor
Steve

AGENDA

1) COMMENCEMENT OF XRI SYNTAX 2.0 VOTE
We had a long discussion about our shared concerns that since the voting
period does not extend into the new year, and since voting typically happens
at the very end of the period, it is likely to put us in a very difficult
position to "get out the vote" right before the New Year holiday.

We discussed whether it was possible to delay the vote until January, and
agreed to check into this immediately with Mary McRae, our TC administrator.

# ACTION ITEM: Drummond to contact Mary and ask her what our options are.

2) XRI RESOLUTION OPEN ISSUES
We intended to close on remaining open issues that need to be addressed in
the drafting of XRI Resolution 2.0 Working Draft 10, however because Dave
was able to join us for the first time in about six weeks, we instead
focused on covering the most recent proposal at:

http://www.oasis-open.org/committees/download.php/15849/xri-res-flowchart-wd
02.pdf

Reviewing it for the first time, Dave pointed out that the proposal does not
enable separation of the use of the Type element for service identification
and the use of the Type element for path matching. In other words, the
proposal does not enable a Service of a particular Type to be selected for a
particular path; only one of the two options can be supported.

It was agreed that this is a outcome of the constraint of only having two
resolution inputs (QXRI and MediaType). If a third resolution input,
ServiceType, is added, then the ability to match on these separately would
be feasible.

A new proposal and flowchart needs to be generated to meet this requirement
ASAP, with the goal of reaching consensus so that Working Draft 10 can be
drafted and published.

=Drummond 



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