ZegnatI am not sure the mf2 parsing spec defines an expected outcome of mf2 inside svgs embedded in HTML. But I would not be surprised if some parsers support it
ZegnatIt is more that I think HTML5 spec does not define how elements within <svg> are parsed. So there is no guarantee they are even part of the domtree that mf2 is looking at
tantekedited /RelMeAuth (+256) "/* detailed algorithm */ check for IndieAuth before performing rel-me discovery (because no one implemented checking a user's own site for OAuth, also OAuth lacked sufficient discovery mechanisms to implement that), explicit should reject silo profiles, may accept 1-2 for testing/demo purposes" (view diff)
[tantek]aaronpk ^ switched RelMeAuth to require IndieAuth discovery on personal sites rather than "OAuth discovery" which was never well defined (at all?) on its own anyway
aaronpkOAuth discovery was finally published in 2018, but as far as i have seen is mainly only implemented in enterprise use cases, not even consumer APIs like GitHub https://tools.ietf.org/html/rfc8414
btremI'd think it would mostly be `<svg><text/>`. I'm using `<text>` for a `p-name` and `<svg>` for the logo. It's conceivable that someone might want to use `<svg>` for a photo property. The solution that jumps to my mind is `e-photo` instead of `u-photo` (which is what I did for the logo, using `e-logo`instead of `u-logo`).