sknebelI mentioned MathML for completeness/context because it and SVG are the formats that are explicitly called out for parsing in the HTML5 parsing spec after Zegnat asked if a HTML parser would put them in the DOM
sknebeland given that its explicitly mentioned I would expect an HTML parser to produce a DOM for it, and thus a microformats parser to find classes and everything to work
sknebel(there is always some risk that not all parsers are always using HTML5 parsers and might do different things, but it answers "what do I expect" to me)
btremWell, it *appears* that Google is doing something useful with it. It does show the street-address, locality, etc. Those are on html elements. It also shows the name of the business that is definitely coming from the svg text element.
sknebelmight be worth testing with PHP and python when they are not using HTML5 parsers - I'd vote for explicitly making them support SVG if they happen to fail it in that case
btremHmm, I did just notice something odd, though: the logo is an svg inside `<h1 class="e-logo">`. So in the JSON there's logo.0.html is the embedded svg markup, as it should; and logo.0.value, which is "Greenbank Plant Nursery Greenbank Plant Nursery".
btremThe `title` element does offer accessibility. But maybe it isn't needed in this case, since the text is visible and accessible to e.g. a screen reader.
@aaronpk↩️ Nice! The thing that does most of the work for me is all in a library XRay:
https://github.com/aaronpk/xray
It normalizes content from Microformats feeds as well as Twitter and other stuff. Then it's a matter of reformatting the resulting JSON into a nice feed using some templates (twitter.com/_/status/1379990018911993856)
KartikPrabhu, Seirdy, mxd, [tw2113_Slack_], [jeremycherfas], hendursaga, [Murray], [KevinMarks], [snarfed], [scojjac], [tantek], [kimberlyhirsh], [schmarty], tomlarkworthy, [Rose], [aciccarello], IWSlackGateway and indy joined the channel