#microformats 2018-04-17

2018-04-17 UTC
tantek, [miklb], [eddie], [jeremycherfas], pniedzielski[m], [pfefferle], CaseD[m], schmarty, KartikPrabhu, [unoabraham] and [kevinmarks] joined the channel
#
@MisterKapowski Spent last night adding microformats and initial #indieweb support to my pseudo-abandoned Jekyll-based blog. I think the next step is going to be writing a Micropub server to interface with it (twitter.com/_/status/986145735107399683)
[snarfed], [unoabraham], [kevinmarks], adactio and [jgmac1106] joined the channel
#
@jgmac1106 ↩️ I am currently thinking about microformats and my online classes. I am trying to encourage #highered peers (since we all teach the same classes) to apply #indieweb technologies to a #GoOpen philosophy and share and remix our courses. Trying… http://quickthoughts.jgregorymcverry.com/2018/04/17/altmetric-i-am-currently-thinking-about-microformats-and-my-online (twitter.com/_/status/986196913635471360)
[jgmac1106], [kevinmarks], [miklb], KartikPrabhu, [pfefferle], TallTed and tantek joined the channel
#
tantek aaronpk: re: https://chat.indieweb.org/dev/2018-04-16/1523890280323500 - No. mf2 parsing requires JSON output specifically so that parsers are unambigously testable
#
Loqi [aaronpk] mf2 parsing doesn't result in JSON, it results in a native data structure in whatever language the parser is written in. it just happens that JSON is a convenient way to output that especially when sharing examples between languages.
kaushalmodi joined the channel
#
tantek something like "native data structure in whatever language the parser is written in" is not testable for interop across languages
#
aaronpk huh, I'm not actually sure all the parsers actually do that
#
tantek then how are they tested?
#
tantek if a parser doesn't output JSON, then you're gonna have a bad day testing it
#
tantek and if you can't test it, it will have regressions over time
#
aaronpk certainly the output of the php parser is a native data structure
#
tantek it can *also* output a native data structure, but that's not what the spec requires
#
aaronpk and the tests test against the native data structure, not json
#
aaronpk e.g. https://github.com/indieweb/php-mf2/blob/master/tests/Mf2/ParseUTest.php#L37 "assertArrayHasKey"
#
tantek so it has its own tests then
#
aaronpk there isn't even a "toJSON" function in the parser
#
Zegnat PHP definitely doesn’t output JSON, no. Just happens to be that it outputs native structures that PHP can turn into JSON. I am not even sure that is true for that new Perl parser
#
aaronpk the test suite tests decode the JSON from the test data
#
aaronpk https://github.com/indieweb/php-mf2/blob/master/tests/test-suite/test-suite.php#L107
#
tantek I remember the ruby parser was a pain to deal with because of native data structure assumptions / conventions
#
aaronpk that was more about ruby object conventions
#
aaronpk once it got turned into returning plain arrays and hashes it's fine
#
aaronpk but it was doing stuff like ".entry" vs ".entries" returning single values vs arrays
#
tantek that sounds like a framework
#
aaronpk yes, that's why it was annoying
#
Zegnat Perl one does not return plain arrays either, instead it has “Web::Microformats2::Item” objects: http://prepan.org/module/nYhnPU5b9bY#module-synopsis
#
Zegnat Instead it offers “as_json” and “new_from_json” methods for interoperability.
#
tantek hey we should resolve 9 and 10 as I think there's enough consensus to do so (and at least one implementation of each)
#
tantek 10 depends on 9 so https://github.com/microformats/microformats2-parsing/issues/9
#
Loqi [sknebel] #9 "return the normalized absolute URL" for invalid URLs?
#
tantek commented
#
tantek onto https://github.com/microformats/microformats2-parsing/issues/10 which upon reconsideration I don't think should depend on 9
#
Loqi [Zegnat] #10 u- parsing should always do relative URL resolution
#
Zegnat I’ll check after dinner :)
#
Zegnat Would be nice to get some issues resolved for sure
#
tantek I seriously thought 10 was already resolved
#
tantek adding as proposed to the spec right now as my older comment said I would
#
tantek edited /microformats2-parsing (+554) "add proposed issue 10 inline to parsing a u- property for in-spec consideration, editorial improvements to that section to minimize the diff to accept proposal while preserving existing normative" (view diff)
#
tantek ah I should have mentioned the use-case of <data class="u-url" href=""></data> for permalink pages that don't already have some linking / display of their own permalink
[kevinmarks] joined the channel
#
[kevinmarks] https://twitter.com/misoks/status/985509981716959232?s=19
#
Loqi [@misoks] My idea for fixing Facebook: shut down Facebook and everyone goes back to the weird niche fan site forum they were on in 2001, where they then form a really deep friendship with a teen who lives in Poland
#
[kevinmarks] Oops wrong channel
[xavierroy] joined the channel
#
tantek lolwut
[pfefferle], [miklb], [kevinmarks], tantek, Tom, [cleverdevil] and Kaja__ joined the channel