Re: [webfinger] Automated Service Configuration now uses webfinger

["Markus Lanthaler" <[e-mail]>]

On Tuesday, July 09, 2013 6:25 AM, Paul E. Jones wrote:
> Cyrus,
> 
> I had a quick look over the new draft.  I do think it's good that this
will
> utilize WebFinger in order to retrieve service discovery information.
> 
> I am curious about one thing.  When issuing a query to the WF server, the
> server returns a link relation of type "service-configuration".  The
> associated URL in the Appendix B example is
> "https://example.com/service-config".  Since the response from the WF
server
> is for a specific identifier (user), I believe this URL should point
> directly to the service config document for the user.
> 
[...]
>
> 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?

I think doing the opposite to make it consistent might be better. The
service-configuration document doesn't contain any information depending on
the user. So, returning *and* requesting https://example.com/service-config
would be better in my opinion.


--
Markus Lanthaler
@markuslanthaler