W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

RE: Input on request for link relation

From: Eran Hammer-Lahav <eran@hueniverse.com>
Date: Wed, 16 Sep 2009 19:02:47 -0700
To: Brett Slatkin <brett@haxor.com>
CC: Atom-Syntax Syntax <atom-syntax@imc.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343784D57E68@P3PW5EX1MB01.EX1.SECURESERVER.NET>

> -----Original Message-----
> From: bslatkin@gmail.com [mailto:bslatkin@gmail.com] On Behalf Of Brett
> Slatkin
> Sent: Wednesday, September 16, 2009 6:03 PM

> My concern is discovery. The link relation declares to machines that
> the PubSubHubbub protocol may be used with the resource and indicates
> that the publisher of the resource has delegated publish/subscribe
> responsibility to another URI (the Hub in the href).
> If "hub" does not indicate the protocol, then how will machines
> determine if PubSubHubbub is supported? Probing the URI endpoint to
> see what it returns? Doing some kind of XRD lookup? All of these
> solutions *could* work, but they are vastly more complex than the
> simplicity of declaring the endpoint outright. This is why we have
> links in the first place!

I (obviously) share your concerns. I have recently spent months looking into the use of 'describedby' vs. other protocol-specific relation types for WebFinger, OpenID, generic resource descriptor discovery, etc. If you are looking for a simple and predictable solution, a URI extension relation type is the best solution.

But it is also worth asking:

* Is anything bad will happen if someone tries to talk PSHB to an endpoint linked as 'hub', which doesn't support it?
* Are there currently other protocols likely to use this? Are they likely to operate side by side for the same feed?
* How often does the protocol requires the processing of hub links? What would be the comparative cost of an additional discovery roundtrip?

I also want to point out that we really need to work on our messaging and perception that URI extension relation type are in any way inferior or "less cool" than the short registered ones. The sooner protocol authors accept this as a perfectly valid choice for their protocol needs, the better the link framework will be.

Received on Thursday, 17 September 2009 02:04:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:51 UTC