#gRegorh-feeds definitely can have child h-* since the parsers will work with it by default, but yeah formalizing it in the spec will guide publishers and consumers better
#capjamesg[d]I agree. I am sure there are plenty of examples in the wild too.
#capjamesg[d]Feeds of events, h-cards, products, etc. all make sense in the real world.
#capjamesg[d]Example: list of events one plans to attend, an open contacts list / “following” list, a feed of products one is offering.
#capjamesg[d]I actually think Shopify adds RSS feeds for products.
#gRegorYeah, I think handling h-event alone would be a good starting point, whether it's in a feed or not
#capjamesg[d]Is there an example use case in the wild?
#KartikPrabhunot sure. I was simply thinking of the fact that mf2 parsing does not special case any sub-object of h-feed
#gRegorUsing h-feed as an indicator to recrawl the URL more often is a cool idea, though
#capjamesg[d]Yeah. It is super helpful. I do the same with RSS, Atom, and WebSub too.
#capjamesg[d]Just so that I don’t have to recrawl a whole site to find new links.
#[tantek]capjamesg[d], can you file an issue for anything you need "clarity on this in the spec" for now? I have trouble following / keeping track of issues in chat when I'm not actively editing the particular spec 🙂
#[tantek]also comment on existing GH issues if you have further questions on them or suggestions / preferences for how you'd like to see them resolved!
aranjedeath, jamietanna and ur5us joined the channel