Version 0.4 will not mention RSS and Atom at all.
I don't think either of the specs should link to the other and PubSubHubbub
0.4 shoiuld apply to any web accessible resource... Atom and RSS being just
examples! Sitemaps is another one... etc

Thanks,



On Fri, May 25, 2012 at 4:29 PM, Roman <[email protected]> wrote:

> Thanks, Julien, this is very helpful.
>
> Do I understand it correctly that 0.5 spec won't mention RSS or Atom at
> all? If so, do you expect RSS and Atom specifications to mention
> pubsubhubbub instead of the other way around?
>
> Roman.
>
>
> On Fri, May 25, 2012 at 4:15 PM, Julien Genestoux <
> [email protected]> wrote:
>
>> I understand better;
>>
>> I'm afraid the only way to go is then to support version 0.4 of the spec,
>> because 0.3 is tied to RSS and Atom feeds...
>> 0.4 will be the first version of the spec that decouples the the data
>> type from the protocol.
>>
>> The problem is that version 0.4 of the spec is not yet implemented
>> anywhere and probably still has some points to be cleared/fixed.
>> To help, you could check that it applies to Sitemaps without any
>> limitation?
>>
>> I am sorry I can't provide a better answer at this point.
>>
>> Thanks,
>>
>>
>> On Fri, May 25, 2012 at 4:04 PM, Roman <[email protected]> wrote:
>>
>>> Hi Julien,
>>>
>>> Our goal isn't to extend a single hub but to make Sitemaps a first class
>>> citizen in the pubsubhubbub ecosystem. We want all hubs to support Sitemaps
>>> just like they support Atom or RSS. To make this happen, we need to extend
>>> the pubsubhubbub specification.
>>>
>>> We've been using pubsubhubbub for a long time but have never been
>>> exposed to the specification processes. Hence we are asking how can we make
>>> Sitemaps to be a part of the pubsubhubbub spec. What's the procedure?
>>>
>>> Roman.
>>>
>>>
>>> On Fri, May 25, 2012 at 3:54 PM, Julien Genestoux <
>>> [email protected]> wrote:
>>>
>>>> Kate,
>>>>
>>>> I dont think 0.3 will be extended for a specific sitemap support. Now,
>>>> I think you can take some freedom around 0.3 and do what you described
>>>> previously!
>>>> Ideally, make sure you also support 0.4 and you should be good for
>>>> future versions of the spec!
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> On Fri, May 25, 2012 at 3:47 PM, Kate Volkova <[email protected]> wrote:
>>>>
>>>>> Julien,
>>>>>
>>>>> What should be our next step to extend 0.3 then to add a note about
>>>>> Sitemaps support?
>>>>> Or can this be done only for 0.4?
>>>>>
>>>>> Thanks!
>>>>>
>>>>>  --
>>>>> Kate
>>>>>
>>>>> On Fri, May 25, 2012 at 1:39 PM, Julien Genestoux <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Kate,
>>>>>> Yes, the discovery can still be performed as per 0.3.
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 25, 2012 at 12:58 PM, Kate Volkova <[email protected]>wrote:
>>>>>>
>>>>>>> Julien,
>>>>>>>
>>>>>>> I'm trying to understand the whole procedure behind switching to the
>>>>>>> new version of the spec...
>>>>>>> Is it still an option to add <atom:link rel="hub" href="
>>>>>>> http://myhub.example.com/endpoint"/> support for Sitemaps to 0.3
>>>>>>> draft?
>>>>>>> As we would like to implement this for our hub (and maybe others
>>>>>>> would do the same for their hubs) but this needs to be specified 
>>>>>>> somewhere
>>>>>>> first =)
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> --
>>>>>>>  Kate
>>>>>>>
>>>>>>> On Fri, May 25, 2012 at 10:07 AM, Julien Genestoux <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> Kate,
>>>>>>>> I have to confess that I'm running out of daylight time :)
>>>>>>>> But I hope the spec 0.4 will soon be public. I want to get feedback
>>>>>>>> from the folks at Instagram, Github or Facebook who implemented their 
>>>>>>>> own
>>>>>>>> version of the 0.3 spec to see if 0.4 fits their needs... Then, it 
>>>>>>>> will be
>>>>>>>> time to start updadting the existing hubs!
>>>>>>>>
>>>>>>>> Julien
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, May 24, 2012 at 4:57 PM, Kate Volkova <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> Thanks for the reply, Julien!
>>>>>>>>>
>>>>>>>>> Yes, <loc> tag uniquely identifies an entry within a Sitemap, so
>>>>>>>>> keeping track of it should suffice.
>>>>>>>>>
>>>>>>>>> Thanks for pointing to the new spec! What's the status of it?
>>>>>>>>> When approximately it'll be released?
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Kate
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, May 24, 2012 at 3:07 PM, Julien Genestoux <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> Kate,
>>>>>>>>>>
>>>>>>>>>> Thanks for emailing the group!
>>>>>>>>>> I do agree Sitemaps would be an amazing thing to add.
>>>>>>>>>>
>>>>>>>>>> The diffing mechanism you describe can be implemented by the hub
>>>>>>>>>> itself (in any way that makes sense for it). I believe just keeping 
>>>>>>>>>> track
>>>>>>>>>> of the <loc> elements would be enough?
>>>>>>>>>>
>>>>>>>>>> Also, have you looked at spec 0.4
>>>>>>>>>> https://superfeedr-misc.s3.amazonaws.com/pubsubhubbub-core-0.4.html
>>>>>>>>>>
>>>>>>>>>> I don't see any reason which would prevent from using this!
>>>>>>>>>>
>>>>>>>>>> Julien
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, May 24, 2012 at 10:52 AM, Kate Volkova 
>>>>>>>>>> <[email protected]>wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello PubSubHubbub developers and users!
>>>>>>>>>>>
>>>>>>>>>>> We would like to add PubSubHubbub support for 
>>>>>>>>>>> Sitemaps<http://www.sitemaps.org/> to
>>>>>>>>>>> make it even more similar to Atom and RSS feeds.
>>>>>>>>>>>
>>>>>>>>>>> A Sitemap <http://www.sitemaps.org/> is an XML file that lists
>>>>>>>>>>> several entries each in its own <url> tag. Each entry has a URL
>>>>>>>>>>> associated with it (under <loc> tag), which can be used as an entry 
>>>>>>>>>>> id.
>>>>>>>>>>> Each entry may also contain additional metadata about the URL (when 
>>>>>>>>>>> it was
>>>>>>>>>>> last updated, how often it usually changes, etc.). Here is an 
>>>>>>>>>>> example of a
>>>>>>>>>>> Sitemap from http://www.sitemaps.org/:
>>>>>>>>>>>
>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>
>>>>>>>>>>> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
>>>>>>>>>>>
>>>>>>>>>>>    <url>
>>>>>>>>>>>
>>>>>>>>>>>       <loc>http://www.example.com/</loc>
>>>>>>>>>>>
>>>>>>>>>>>       <lastmod>2005-01-01</lastmod>
>>>>>>>>>>>
>>>>>>>>>>>       <changefreq>monthly</changefreq>
>>>>>>>>>>>
>>>>>>>>>>>       <priority>0.8</priority>
>>>>>>>>>>>
>>>>>>>>>>>    </url>
>>>>>>>>>>>
>>>>>>>>>>>    <url>
>>>>>>>>>>>
>>>>>>>>>>>       <loc>
>>>>>>>>>>> http://www.example.com/catalog?item=12&amp;desc=vacation_hawaii<http://www.example.com/catalog?item=12&desc=vacation_hawaii>
>>>>>>>>>>> </loc>
>>>>>>>>>>>
>>>>>>>>>>>       <changefreq>weekly</changefreq>
>>>>>>>>>>>
>>>>>>>>>>>    </url>
>>>>>>>>>>>
>>>>>>>>>>> </urlset>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The same Sitemap with PubSubHubbub support would look like this:
>>>>>>>>>>>
>>>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>>>>>
>>>>>>>>>>> <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"* **
>>>>>>>>>>> xmlns:atom="http://www.w3.org/2005/Atom*";>
>>>>>>>>>>>
>>>>>>>>>>>    *<atom:link rel="hub" href="**
>>>>>>>>>>> http://myhub.example.com/endpoint"/>*
>>>>>>>>>>>
>>>>>>>>>>>    <url>
>>>>>>>>>>>
>>>>>>>>>>>       <loc>http://www.example.com/</loc>
>>>>>>>>>>>
>>>>>>>>>>>       <lastmod>2005-01-01</lastmod>
>>>>>>>>>>>
>>>>>>>>>>>       <changefreq>monthly</changefreq>
>>>>>>>>>>>
>>>>>>>>>>>       <priority>0.8</priority>
>>>>>>>>>>>
>>>>>>>>>>>    </url>
>>>>>>>>>>>
>>>>>>>>>>>    <url>
>>>>>>>>>>>
>>>>>>>>>>>       <loc>
>>>>>>>>>>> http://www.example.com/catalog?item=12&amp;desc=vacation_hawaii<http://www.example.com/catalog?item=12&desc=vacation_hawaii>
>>>>>>>>>>> </loc>
>>>>>>>>>>>
>>>>>>>>>>>       <changefreq>weekly</changefreq>
>>>>>>>>>>>
>>>>>>>>>>>    </url>
>>>>>>>>>>>
>>>>>>>>>>> </urlset>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Diffs between previous and current version of the feed will be
>>>>>>>>>>> computed the same way as it’s done for Atom and RSS feeds:
>>>>>>>>>>>
>>>>>>>>>>>  - For each entry sha1(entry) is computed and compared with the
>>>>>>>>>>> old hash value for the same entry_id.
>>>>>>>>>>>  - If the hash value has changed or there is no old hash value
>>>>>>>>>>> for this entry_id (an entry is new), the entry is added to the list 
>>>>>>>>>>> of
>>>>>>>>>>> items to publish for this topic (feed_url)
>>>>>>>>>>>
>>>>>>>>>>> Any comments on this?
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Kate Volkova,
>>>>>>>>>>> Software Engineer, Google.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to