ZegnatLast php-mf2 release was in 2018. I see no problem with cutting a new release with the work that has been done since then, even if there are still a couple issues open
hairykitty, KartikPrabhu, [LewisCowles], [mapkyca], Sajesajama, [jgmac1106], [KevinMarks] and Sajesajama_ joined the channel
[KevinMarks]I recursively walk the example json and compare with the returned and give a compressed json structure with green tick marks when the subtree matches.
GWGTry to remember...why does the PHP-MF2 parser replace images in the e-content with the alt-text and with the alt text being parsed out, should that stop?
[jgarber]Quick search on GitHub (microformats/microformats2-parsing repo) for picture, audio, and video doesn’t yield any obvious previous discussions.
[jgarber]There are some parsing rules for audio/video elements in the u- properties portion of the spec. Nothing for the picture element and no mentions of handling `srcset` attribute (discussion ongoing on GitHub) or mention of parsing `<source>` / `<img>` child elements.
ZegnatI would stick it on the wiki, especially if you have no idea what shape it would take yet or have no prior art / use-case yet. I think the microformats/microformats2-parsing issues function best when they are actual proposals
sknebelright. the srcset issue has been laying around for so long because people said "oh, interested", but nobody even said anything how they'd want to consume the data
[chrisaldrich], [snarfed], [tantek], vesper11, [benatwork], mauz555, [tw2113], [KevinMarks], LisaMorales, KartikPrabhu and gRegorLove joined the channel