Blaine, Not sure what you mean, but I had previously updated the file there : http://superfeedr-misc.s3.amazonaws.com/pubsubhubbub-core-0.4.html
Feel free to send your changes here, and I'll make sure I reflect them there :) Ju On Wed, May 2, 2012 at 5:15 PM, Blaine Cook <[email protected]> wrote: > On 2 May 2012 14:01, Julien Genestoux <[email protected]> wrote: > > All, > > I just pushed an updated version of this draft. > > It now includes the following (minor) points: > > - Comments/Fixes by Walter Groix, > > - Symetric "accepted" and "denied" when the hubs validates the > subscription > > - Use of From header (based on Blaine's feedback) > > - Use of Location header when "denied" to indicate that another > > - Allowing for discovery thru host-meta well known url. > > > > Please, feel free to review and submit any change that is appropriate. > > This sounds awesome, Julien! > > My comments: > > – I'd suggest the following text for §4❡2 (major change is to use > RFC6415 explicitly): > > "In the absence of HTTP Link headers, subscribers SHOULD fall back to > other methods to discover the hub(s) and the canonical URI of the > topic. If the topic is a Atom or RSS feed, the publisher MAY provide > embedded link elements as described in Appendix B of Web Linking > [RFC5988], and the subscriber SHOULD use those links as per Appendix B > of [RFC5988]. Similarly, for HTML pages, the publisher MAY use > embedded link elements as described in Appendix A of Web Linking > [RFC5988], and subscribers SHOULD use those links as per Appendix A of > [RFC5988]. Finally, publishers MAY also use Web Host Metadata > [RFC6415] to include the <Link> element with a rel-value equal to > "hub" as with the other approaches; publishers SHOULD provide the JSON > variant of [RFC6415]. Subscribers SHOULD support this method for > discovery. > > OOPS. > > I started reading the spec at the link you posted and realised that > it's not the updated one at all. I don't know if the above comment > stands, but I'll hold off until the link is updated. :-) > > b. >
