Minutes: XRI TC Telecon 8-9AM PT Tuesday 2009-01-13

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

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

Date:  Tuesday, 13 January 2009 USA
Time:  8:00AM - 9:00AM Pacific Time (16:00-17:00 UTC)

ATTENDING

Peter Davis
John Bradley
Eran Hammer-Lahav
Breno de Medeiros 
Drummond Reed
Brian Eaton 


AGENDA

1) HTTP-BASED RESOURCE DESCRIPTOR DISCOVERY (HRDD) - FIRST PUBLIC DRAFT

Eran provided the following update (also includes discussion of /site-meta):

Feedback:

* Switch to using the term "descriptor discovery" instead of "resource
discovery".

* W3C TAG posted feedback on /site-meta:

	http://lists.w3.org/Archives/Public/www-tag/2009Jan/0024.html 

Open issues:

* http: URIs - what are the requirements? Should there be an "HTTPS
/site-meta" for https: URIs?

* DNS authority issue - Eran is leaning towards just turning this into an
informative section and defer to applications. OpenID, as an example, can
just specify its own policy for authority use.

* /site-meta: what resource does it describe? This is currently addressed in
a section of the HRDD draft. We discussed that SemWeb folks may be looking
for a URI-fragment based interpretation using a well-known fragment, but
that's an editorial decision.

Next steps:

# ERAN to put out a new draft of HRDD (estimate: an O1 by Friday).
# ERAN to work with Mark Nottingham to put out a new draft of /site-meta (no
date yet).


2) DNS-BASED RESOURCE DESCRIPTOR DISCOVERY

Peter hasn't had a chance to get much progress done on either the base
resolution or the trust profile yet. He will get to it as soon as he can.

# PETER to do second draft of DNS proposal.
# PETER to do DNS trust profile.


3) XRD 1.0 - SCHEMA SECTION - FIRST WORKING DRAFT

Eran is planning to start drafting on Thursday with a preview on Friday.
Drummond noted that Mary McRae will attend the first part of our Thursday
telecon to provide advice on OASIS spec template usage.


4) XRD 1.0 - TRUST MODEL

Brian does not yet have a trust profile from Peter for DNS and Nat for
OpenID CX. Brian is planning to work on the trust profile for what he thinks
OpenID will use.

John pointed out that the OpenID community has a key decision in terms of
deciding on the canonical identifier. This is a difficult issue that appears
not to have consensus within the OpenID community. He suggested there are
two basic options: 1) verifying all identifiers in the chain of redirects,
or 2) verifying the CanonicalID in the final XRD.

Brian believes that if our specs offer a good design for how delegation can
be handled in OpenID, this could solve a number of problems for the OpenID
community.

Peter brought up two other potential trust profiles:

* SAML. Peter is not sure but thinks this could be relevant. XRD could be a
way to perform dynamic metadata discovery for SAML federations and IdP
discovery (the WAIF problem).

* OAuth. This is also something Brian has been thinking about.

John also mentioned that XRD can potentially play a role in the current web
services harmonization effort.

# NAT to post a wiki page on the OpenID CX trust profile.
# BRIAN to propose an OpenID trust profile.


5) CANONICALID ISSUE

Brian summarized a problem that he's been discussing offline with Drummond.
The problem is if you do discovery on Alice and find an XRD that says the
CanonicalID is Bob, Brian's current draft says you should fail. Drummond
pointed out the CanonicalID verification process specified in XRI Resolution
2.0, which he believes verifies synonym between the identifiers Alice and
Bob and establishes that it is safe to use the XRD as metadata for both.

We ran out of time to discuss it but agreed:

# BRIAN to start public list discussion with an accompanying wiki page on
the topic.
# DRUMMOND to help with the above.


5) XRI 3.0 - SYNTAX UPDATE

Drummond noted that there is a special telecon aimed at closing on the
current proposals at 2PM this afternoon:

	http://lists.oasis-open.org/archives/xri/200901/msg00066.html

# DRUMMOND to send a summary email before the telecon.

6) NEXT CALL

Standard time slot: 2-3PM PT (22:00-23:00 UTC) on Thursday.