#microformats 2021-10-13

2021-10-13 UTC
aranjedeath, ur5us, angelo, [jacky]1, [Justin_Walsh]1, [fluffy]1, hendursaga, [Ed_Beck]1, sebbu, hendursa1, JSharp, milkii and yolk joined the channel
#
capjamesg[d]
GWG I just saw a year old issue on the h-feed two about moving the h-feed spec to stable.
#
capjamesg[d]
I’d love to discuss this more. Maybe this is a topic for a pop up if not already discussed in a recent pop up?
hala-bala[m], diegov, mambang[m] and [Justin_Walsh] joined the channel
#
GWG
capjamesg[d]: We cancelled that pop-up
#
GWG
So not recently
gRegor, [schmarty] and hendursaga joined the channel
#
[tantek]
capjamesg[d] yeah I think there's a bunch more work necessary on h-feed to get it to stable.
#
[tantek]
h-event is closer on that front
KartikPrabhu joined the channel
#
GWG
[tantek]: Is there an advantage to stabilization in your experience?
#
capjamesg[d]
I am curious what that work is.
#
capjamesg[d]
I am still learning the process.
#
GWG
capjamesg[d]: So am I and I've been embedded for a while now
#
[tantek]
GWG, as an implementer, do feel any differences between draft and stable?
#
GWG
[tantek]: Other than outstanding issues, no
#
[tantek]
There’s a pretty big difference in process / change control
[schmarty] joined the channel
#
capjamesg[d]
Can you elaborate?
gRegor and gRegorLove_ joined the channel
#
capjamesg[d]
I see.
#
capjamesg[d]
There are still a number of issues to work through.
#
capjamesg[d]
A pop up may be in order to dive deeper.
#
capjamesg[d]
And some issues are quite critical like answering whether h-feeds can contain markup like h-event.
#
[tantek]
capjamesg compare the headers of h-card vs h-event for example
#
[tantek]
KartikPrabhu I should update the /process page to note the more detailed change control process in stable specifications
#
gRegor
That stage-to-stage page could probably use some review. Still mentions the mailing list for example.
#
gRegor
jinx? heh
#
capjamesg[d]
+1 tantek.
#
gRegor
h-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.
#
capjamesg[d]
*product listings
#
gRegor
Yeah, I use h-feed of h-event
#
capjamesg[d]
So I think it is logical to support such behavior and document it in the spec.
#
capjamesg[d]
Yep!
#
capjamesg[d]
I am building a search engine and clarity on this in the spec would be useful.
#
capjamesg[d]
I don’t currently do anything with feeds of events etc. but I can see imminent use cases for such implementations.
#
capjamesg[d]
Example: reading a feed of h-events and recrawling them all often.
#
gRegor
Do you do anything with the h-events?
#
capjamesg[d]
Right now?
#
KartikPrabhu
specializing h-feeds on what they contain does not seem like a good idea
#
capjamesg[d]
Generally, I render them in featured snippets.
#
KartikPrabhu
h-feed can contain any h-*
#
capjamesg[d]
KartikPrabhu now I think about it I don’t need to.
#
capjamesg[d]
Because I read for URLs and then crawl each url.
#
capjamesg[d]
So the aforementioned use case is not necessary. But this means I implicitly support feeds of anything.
#
KartikPrabhu
h-feed can even contain a mix of differnt h-*
#
capjamesg[d]
As long as a URL is present.
#
capjamesg[d]
I had no idea you could do that.
#
gRegor
Yeah, 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?
#
KartikPrabhu
not sure. I was simply thinking of the fact that mf2 parsing does not special case any sub-object of h-feed
#
gRegor
Using 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]
(as in open in an editor)
#
[tantek]
thanks!
#
capjamesg[d]
I think the issues in the spec cover everything for now. I’ll actively add issues when I have them to add.
#
capjamesg[d]
*issues filed in the spec GitHub Issues page
[Ana_Rodrigues], [chrisaldrich] and hans1963[d] joined the channel
#
[tantek]
sounds good!
#
[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
#
tantek
edited /Template:cc0-owfa-license (+25) "updated OWFa link, see https://wiki.mozilla.org/OWFa for history / verification that it's literally the same license text"
(view diff)
gRegor, Seirdy and [snarfed] joined the channel