#microformats 2020-04-27

2020-04-27 UTC
[prtksxna], gRegorLove_ and [LewisCowles] joined the channel
#
Zegnat
Hmm, not sure I would make me having read a book a (by necessity backdated?) event
[mapkyca], mauz555, jeremycherfas_ and [KevinMarks] joined the channel
#
[KevinMarks]
Also whether nesting makes more sense than 2 types like that
Philippe, jamietanna and [jgmac1106] joined the channel
#
[jgmac1106]
seems to be what most people do, though the debate of my read posts as an h-review or a an h-entry with an h-reviews as nested is interesting. Give me the option to rate the book or not
#
[jgmac1106]
I am not wrapping any author's in an h-card given there is really nobdy doing aanything with the read posts anyways, but may start
[prtksxna], [grantcodes], [tw2113], [chrisaldrich], [LewisCowles], KartikPrabhu, dougbeal|mb1, [mapkyca], [benatwork], indy_, Sajesajama__, vesper11, omz13, globbot, joshghent, cjw6k, [snarfed], ChanServ, [KevinMarks], [Aaron_Klemm] and [jansauer] joined the channel
#
[jansauer]
Hi, everybody 👋 I’m a little stuck with my microformats parses handling of e- properties. My test for https://github.com/microformats/tests/blob/master/tests/microformats-v2/h-entry/urlincontent.html is failing as i do not resolve relative urls.
#
[jansauer]
The strange part is that i do not find any requirement for this in the spec (https://html.spec.whatwg.org/multipage/parsing.html#serialising-html-fragments)
#
[jansauer]
and now i feel like i can’t see the wood for the trees.
#
[jansauer]
Does anyone know what part i’m missing?
#
sknebel
welcome back [jansauer]!
#
sknebel
nice to see we haven't entirely lost you, even though your PR rotted longer than planned (sorry...)
#
sknebel
If I understand correctly, what you are looking for is here: microformats.org/wiki/microformats2-parsing#parsing_an_e-_property
#
sknebel
ah wait no
#
sknebel
looked at the wrong thing
[jeremycherfas] joined the channel
#
sknebel
[jansauer]: no, I think you aren't missing anything actually, and this isn't defined that way
#
[jansauer]
Yes I almost forgot that project but after geting a mail that my mr was merged .. 😅
#
sknebel
(and existing parsers appear to disagree in how to do it ...)
#
sknebel
lets see if Zegnat or someone else will point out in a bit what I missed :D
#
[jansauer]
it totally makes sense for the usability of microformats. But i wanted to check the spec before implementing it
#
sknebel
so the php parser appears to do it, the python one does not
#
sknebel
(it == resolve the relative url)
#
sknebel
and I agree the spec does not require it for the "html" value
#
sknebel
gotta run, but thank for stopping by!
#
[jansauer]
by
#
Loqi
[willnorris] #38 resolve relative URLs in e-* html
#
willnorris
yeah... looks like that issue stalled out. I did end up changing the Go library to resolve relative URLs, fwiw
#
[jansauer]
Think i will to the same; Having working urls when embading the html in a new site makes it so much usefuller.
#
[jansauer]
And i definitely will have a look at your implementation in order to see what attributes i forgot
#
sknebel
ah good find
#
sknebel
yes, then clearly go ahead and do it
#
sknebel
seems clear consensus that the parsers want to do that, just dropped it
#
sknebel
[jansauer]++
#
Loqi
[jansauer] has 4 karma over the last year
#
Zegnat
[jansauer]: hiya long time no talk! (Missing all the usual Germany events :( ) If you take any action with that, please do comment on that parsing issue. Might be just the push needed to get it to land in the spec
#
sknebel
actually, Zegnat had a long list of all the properties that contain urls somewhere
#
Zegnat
Linked in that issue
#
Zegnat
Actually linked from my proposed text, because I wanted to be clear what links would need to be resolved by parsers
#
sknebel
[jansauer]: ^^^ there is a list of attributes in the issue
#
sknebel
seems like php-mf2 also already does resolve
#
sknebel
at least for the example I looked at
#
sknebel
so 2 parsers already have implementations
[cleverdevil], [snarfed], [chrisaldrich], gRegorLove and mauz555 joined the channel