tantek__, [jgmac1106], jwheare12, averell26, mattfo0, [chrisaldrich], PaulCapestany, tripleslash2, KartikPrabhu and [asuh] joined the channel; vivus left the channel
gRegorLovephp-mf2 fails 30 tests, but some are just things like URLs not being made absolute. microformats/tests assumes you pass in a base url of http://example.com/
willnorrisben_thatmustbeme: I've got a couple of patches for mf2-tester whenever you've got a minute to review. First to add a license to the repo, and second to add the go parser to the table
Loqiwillnorris: tantek left you a message on 2016-07-06 at 2:30pm UTC: as someone who has participated in microformats2-parsing issue discussions / resolutions in the past year at least, could you offer your opinion, even if just a summary +1/0/-1 on my documenting of our existing rough processes here: https://github.com/microformats/microformats2-parsing/issues/1#issuecomment-230912142
willnorrisThere are also some cases of e- properties "html" value getting urls expanded, but I don't think they're supposed to (only the "value" should, right?)
willnorrisWasn't there discussion somewhere about updating the spec to actually say they *should* be expanded? I can't find it now, so may have just imagined that.
gRegorLoveMy first thought is that should be part of a sanitization process by the consumer, but also once it's parsed you no longer have the <base>, if it exists
[tantek]Worth filing an issue on considering base / resolving relative urls inside e-* markup. Not sure how consuming code would make sense of them otherwise. Though how hard is that for parsers
ben_thatmustbemehmm, i don't see why you couldn't set it up for informational reasons, seems sort of weird in my brain that you are running the test suite against parsers to make sure the tests make sense while writing the parsers to test against the test suite
[kevinmarks]well, what ben just built (and aaron kind of did before, and so on) is a kind of CI results page, so using one integrated into github makes some sense