Minutes: 11/4 XRI TC Telecon

["Drummond Reed" <drummond.reed@cordance.net>]

Following are the minutes of the unofficial XRI TC telecon held from
8:30-10:00AM Pacific on Friday, Nov. 4, 2005.

Present:

Gabe
Mike
Peter
Les
Victor
Dave
Drummond
Steve
Bill
Marty
Owen

1) REVISIT OF YESTERDAY'S AGENDA ITEMS TO DETERMINE/CONFIRM CONSENSUS

a) SOAP-style vs. URI-style XRIDS

First we checked consensus on whether everyone agrees either style will
work. There was consensus on this.

We then checked for preferences.

SOAP-style preference:
Bill Barnhill
Mike
Gabe (mild)


URI-style preference:
Victor
Steve
Drummond
Peter
Les
Dave
Owen

We therefore will prepare the next Working Draft using the URI-style format.

b) Spec refactor discussion

Because much of the work has already been done to prepare a refactored spec
that uses mostly the URI-style format, we will incorporate that refactoring
into the Working Draft.

c) HXRI format

Gabe made the point that HXRIs would need to use the path rather than the
query style to be compatible with "microformat" initiatives such as the
rel-tag syntax (http://microformats.org/wiki/Main_Page). 

Mike felt that the query format was preferable, and Dave also prefers it
because it may require less escaping. However upon further discussion the
collective wisdom of the group was that it would be best to define only one
HXRI format, and the path format meets a broader set of requirements. 

Drummond suggested that he and Dave discuss it and come back with a specific
recommendation about the escaping rules.

2) CONTINUE DISCUSSION OF PROXY RESOLUTION RULES AND PATTERN MATCHING

Dave again explained his suggestion about adding a <Pattern> element
specifying its use in selecting a service element. Currently there only way
to choose a Service element which is by type and priority. Dave's suggestion
would add an optional element that contains a regular expression. If the XRI
has a path component, upon completing authority resolution the client would
selects the appropriate service by seeing if the XRI path matches the regex
in the Pattern element, if any.

No consensus was reached. Drummond suggested that he work with Dave to
prepare a specific proposal as part of the Working Draft.

3) EDITORS AND WORKING DRAFT SCHEDULE

Drummond has already volunteered to help Gabe edit the next Working Draft
(and since Gabe's time is limited, he'd like the help). 

Dave and Les also volunteered to help as editors.

Since considerable work has already been started, the goal is to produce the
next draft in time for TC members to review it prior to the next call (next
Friday).

4) ADVANCEMENT OF XRI SYNTAX 2.0 COMMITTEE DRAFT 02

The public review period for XRI Syntax 2.0 Committee Draft 02 has closed.
One public comment was received from Norm Walsh at Sun. He referenced the
W3C TAG feedback and said that he didn't feel the TAG's concerns were
addressed.

There was consensus that, while the TAG comments resulting a huge amount of
work being done to XRI resolution to make it fully backwards compatible with
HTTP URIs (which will be apparent shortly in the new Working Draft of XRI
Resolution), it had no effect on XRI Syntax.

Therefore there was consensus to immediately begin the ballot to advance XRI
Syntax 2.0 Committee Draft 02 to a Committee Specification and submit it by
November 15 for vote as an OASIS Standard. 

Drummond will contact XRI TC Administrator Mary McRae and ask her to open an
online ballot today so it can close by Friday, November 11. Everyone is
asked to vote as soon as possible after this ballot opens.

We will also need to begin preparing the TC member attestations of
implementation and interoperability. Drummond will send email to the list
about this.

5) NEXT MEETING

We will continue to hold meetings at 8:30am Pacific Fridays until we finish
the XRI 2.0 suite. The exception will be Friday November 25 due to the
Thanksgiving holiday in the U.S.

=Drummond