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: Minutes: 11/2 XRI TC Telecon & Reminder 11/3 8:30AM PT Telecon



Following are the minutes of today's XRI TC Telecon (and a reminder of
tomorrow's morning telecon, 8:30AM PACIFIC, same number).

Date:  Friday, 04 November 2005
Time:  08:30am - 10:00am PT

Dial-in number: 218-936-6666
Access Code: 2647893

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

Present on today's (11/03) call:

Dave McAlpin
Mike Lindelsee
Gabe Wachob
Drummond Reed
Peter Davis
Nick Ragouzis
Les Chasen

1) RESOLUTION SPEC REFACTOR STRAWMAN DISCUSSION
See the strawman email at:

http://lists.oasis-open.org/archives/xri/200511/msg00019.html

The general feeling was that a spec refactor would be nice but must be
weighed against the amount of work/review it takes. Drummond has already
started this process so that may offset some of that.

The consensus was to delay this decision based on the outcome of the other
key decisions.


2) XRID STRUCTURE STRAWMAN DISCUSSION
See the strawman email at:

http://lists.oasis-open.org/archives/xri/200511/msg00020.html

The two different strawmen ("SOAP-style" and "URI-style") were contrasted.
Dave pointed out that URI-style was really SOAP-style with fewer defined
blocks, and could be extended the same way as SOAP-style.

There was consensus that both approaches meet all the requirements. Bill
Barnhill expressed via email a preference for the SOAP-style approach; Peter
and Les and Drummond expressed a preference for the URI-style approach; and
everyone else was ambivalent.

It was agreed we'd all sleep on it 24 hours and make a decision on
tomorrow's call.

3) HXRI FORMAT STRAWMAN DISCUSSION
See the strawman email at:

http://lists.oasis-open.org/archives/xri/200511/msg00021.html

It was clarified that the proposal applies to both HTTP and HTTPS. There was
agreement that the query form should be more explicit so that it can support
additional parameters if needed. There was agreement that two forms, one
simple for people and one more robust for machine generation, would be okay.
Dave made the point that both would require a definition of the necessary
escaping.

4) PROXY RESOLUTION RULES DISCUSSION
No strawman was posted, but we had a good discussion of the potential need
for pattern matching of paths in order to determine the correct HTTP server
to which to send a local access request.

5) PROPOSED AGENDA FOR TOMORROW'S CALL

a) Revisit of today's agenda items to determine/confirm consensus.

b) Continue discussion of proxy resolution rules and pattern matching.

c) Determine next step of outstanding issues/decisions.

d) Assign action items for commencing the drafting stage.

e) Agree on proposed finish date and continued call schedule.



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