[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xri] Minutes: XRI TC Telecon 2-3PM PT Thursday 2009-11-12
Apologies for missing the call. My parents arrived from Israel today. EHL From:
drummond.reed@gmail.com [mailto:drummond.reed@gmail.com] On Behalf Of Drummond
Reed Following are the minutes of the unofficial telecon of the
XRI TC at:
Nat Sakimura Scott Cantor Drummond Reed Nika Jones Markus Sabadello Nat made the suggestion that the TC compile a FAQ in order
to answer the questions of why we made certain design choices. We also agreed
that developing responses to the Comment list is a good way to start this FAQ. We discussed how we should be dealing with Comments. Given
the volume, we will need to pick out the specific comments received and respond
to them. The wiki would be a good tool for doing this. We did not have either editor present on today’s call, so we
were not able to answer the question of how many other changes are still
necessary to add based on comments received so far. Will’s last message to the
list had several action items for Eran. Scott raised the issue of whether the rel attribute should
be optional, given that Link selection is primarily rel-based. # SCOTT to send a message to the list on this issue. The URI of the new draft 4 is:
http://www.ietf.org/id/draft-hammer-hostmeta-04.txt Eran was not on the call so we just agreed on the following: # ACTION – ALL TC MEMBERS please review the new host-meta
draft and send any feedback to the list or Eran. Eran has expressed the view that this work did not need to
happen here, nor in fact at any standards org if it was not necessary. Drummond
queried those on the call whether this is something the XRI TC wants to
undertake. John pointed out that we don’t need to tackle it until there
is confirmed demand, about which there was consensus. We deferred further discussion until others from the IIW
session could attend the call. In this respect a XRI local resolver is now a very thin
layer over a standard XRD consumer. An XRI proxy resolver should also behave
just like any other server producing an XRD. The behavior of a “default
service” that was provided in XRI Resolution 2.0 is no longer needed because
the XRD itself is linked to the bound XRI and not the resource identified by
the bound XRI. Instead the bound XRI can be a locator for the default resource,
such as a contact page. Drummond and John volunteered
to work on the actual spec but not until closer to the holiday period due to
current workloads. The next call is next week at the regular time. Drummond
noted he will be at the Impact Conference in Salt Lake City and may not be able
to attend. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]