[uf-discuss] more hatom rambling - detection

[David Janes -- BlogMatrix]

That looks about right! I.e. hentry elements belong to the 
closest-ancestor hfeed element, otherwise they belong to the implicit 
feed for the page.

This could probably be clarified for 0.2.

The meaning of nested hfeeds is not defined but interesting 
possibilities abound.

Regards, etc...
David

Dimitri Glazkov wrote:
> Chris,
> 
> How about this:
> 
> * look for hentry
> * if found, traverse ancestors to see if there's an hfeed
> ** if found, add hfeed to list of feeds
> ** otherwise, add page to list of feeds, stop looking for hfeeds
> * repeat
> 
> :DG<
> 
> On 6/20/06, Chris Casciano <chris at placenamehere.com> wrote:
>>
>> Let me continue my hatom spec/issue rambling by piggy backing on the
>> recent hcard detection / class "hijacking" thread...
>>
>> Given [1]:
>>
>> "the Feed element is optional and, if missing, is assumed to be the
>> page"
>>
>> What are the rules for detecting that an hatom feed exists in a page?
>> Like the other thread, I'm thinking less about the context of actually
>> parsing the document with an hatom capable parser, but more in the
>> detection context where you may have some other application (browser or
>> plugin) detecting that the feed exists and preparing to hand off the
>> document to another (feed reading) application.
>>
>>
>> [1] http://microformats.org/wiki/hatom#Feed