Re: discovering an authority endpoint

On 11/19/2014 07:08 PM, Kingsley Idehen wrote:
>> The benefit of this approach is that you can embed the services in 
>> the HTML document as JSON-LD or RDFa, or you can content negotiate 
>> for it. You also don't have to have special .well-known URL 
>> registries and the solution can be re-used for any sort of REST
>> API web services on the site (and extended dynamically instead of 
>> having to go through IETF or W3C).
> 
> Re. HTML are you going to use <link/> and @rel in <head/> to expose 
> key relations?

I think it's a good idea. I'm not sure most Web developers will do it.

Why not just content negotiate for the root document instead of having
all those link @rels in HEAD? Wouldn't that be simpler?

> With <script/> based structured data islands an additional mechanism 
> for relations discovery?

This seemed to be the most likely thing that Web developers would do. So
if we had to pick one thing, I think this should be it. It's worked out
quite well for schema.org markup and the Actions stuff in Gmail for JSON-LD.

> In addition to the above you can create HTTP renditions of all the 
> <link/> and @rel based relations via "Link:".

Yes, also a good idea, but I don't think we have a good track record of
getting Web developers to do that.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Marathonic Dawn of Web Payments
http://manu.sporny.org/2014/dawn-of-web-payments/

Received on Thursday, 20 November 2014 05:11:17 UTC