Re: [webfinger] Automated Service Configuration now uses webfinger

[Cyrus Daboo <[e-mail]>]

Hi Paul,

--On July 9, 2013 at 12:24:35 AM -0400 "Paul E. Jones" 
<[e-mail]> wrote:

> I believe for all examples we've considered with WF so far, there was no
> need for the client to perform any manipulation on the URI for the
> specific link relation.  The examples in this document are the first to
> do that.  Is there a reason?  Can I persuade you to put the user-specific
> URL right into the WebFinger response?

Yes, that seems like a better approach.

One question that has come up is whether webfinger should be the only HTTP 
service config document discovery mechanism. One suggestion has been to 
have a separate .well-known resource for direct access to the document. My 
feeling is that at this point I think we should stick solely with webfinger 
- partly to help promote use of webfinger itself, but also because there 
might be a whole bunch of other useful information that webfinger could 
provide. e.g. the service config client might also want to get the user's 
vCard in addition to service information and that could be accomplished in 
a single webfinger lookup. I will try adding an example to the spec to 
illustrate that.

-- 
Cyrus Daboo