tantek__, [jgmac1106], jwheare12, averell26, mattfo0, [chrisaldrich], PaulCapestany, tripleslash2, KartikPrabhu and [asuh] joined the channel; vivus left the channel
#gRegorLoveMerged the implied tests updates after willnorris and ben_thatmustbeme gave the thumbs up.
#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/
#ben_thatmustbemea lot of the tests that are failed on things are whitespace related
[jgmac1106], Typhon23, cylon512_, MyIgel, [kevinmarks], pj23, Random9, wols, [keithjgrant], [xavierroy], [grantcodes], GWG, willnorris, Guest72310, rkta, Madbrad20018 and eldritch12 joined the channel
#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
#willnorriswow, uh thanks Loqi. Two year old message, eh? Better late than never I guess :)
#willnorrisguess that shows how long I've been out :(
#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?)
#willnorrisOr if they should be expanded, I don't think that's clear in the spec
#KartikPrabhuwillnorris: yeah exactly . I don't think they should be but the tests have those expanded out
#willnorrisYep. Was going to send a PR for that later, but happy to have someone else beat me to it
#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.
#KartikPrabhubut currently the lean has been towards not "disturbing" the authored html
#KartikPrabhubut this seems like a valid exception. we could either leave it to the consumer or do it in the mf2 parsing
MJ9410 joined the channel
#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
#gRegorLovedecides to not think about it too much for now :)
#KartikPrabhugRegorLove: hmm yeah the <base> case is tricky
#KartikPrabhuwillnorris: gRegorLove: maybe open an issue on the parsing repo?
Miron28, ws2k326, dimi34ka13, gRegorLove, [kevinmarks] and [tantek] joined the channel
#[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
#aaronpkIf the parser doesn’t do it, the consumer has to later
#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
#[tantek]Yeah better to move such smarts upstream to be in fewer places
supercool10, tantek__, [iambismark], tantek and [kevinmarks] joined the channel
#[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
#[kevinmarks]glen's code in the repo is another version of this
milkii, [grantcodes], [keithjgrant], mattfo0, sam28, u1dzer026, [tantek] and [dougbeal] joined the channel