#microformats 2018-08-23

2018-08-23 UTC
ben_thatmustbeme, KevinMarks_ and [iambismark] joined the channel
#
tantek__ hmm don't remember seeing this when it came around: https://twitter.com/Lucid00/status/1021564891960946688
#
Loqi [@Lucid00] @jimpick @ThisIsMissEm @BeakerBrowser I think they got the idea from this. The spec is identical. http://microformats.org/wiki/rel-payment
#
ben_thatmustbeme why do i feel like willnorris and I are in the acid test race
#
ben_thatmustbeme :D
#
ben_thatmustbeme updates https://ben.thatmustbe.me/mf2tests/
tantek__ joined the channel
#
willnorris Hah! Let's go!
#
tantek__ 🍿
dmcweeney joined the channel
#
ben_thatmustbeme with v1/hcard/single test, the rev value removes T
#
ben_thatmustbeme it should be keeping the T correct?
#
tantek__ don't recall offhand
#
ben_thatmustbeme looks like there is a PR for it already
#
ben_thatmustbeme https://github.com/microformats/microformats2-parsing/issues/12
#
Loqi [tantek] #12 should dt-* parsing do date and time parsing for all values?
#
ben_thatmustbeme its back to that
Garbee_ joined the channel
#
tantek__ we decided yes right?
#
tantek__ and the result should omit the T for easier readability?
#
@nagahitoyuki ブログの #Google検索 での #表示回数 が二倍近く跳ね上がったのは #Microformats の #hentry を取り入れたのと重なっている。#構造化データ はGoogle推奨の #JSONLD だけでは勿体なさそうだ。#サイト内容 を #サイト構成 から示すには #htmlタグ に記載する形式が向いている。https://www.nagahitoyuki.com/ (twitter.com/_/status/1032456089290203136)
strugee, tantek, [eddie], [tantek] and [shaners] joined the channel
#
[shaners] [ben_thatmustbeme] Thanks! Would you mind transferring your forked gh repo to the mf org please? And then I’ll wire up the Heroku auto-deploy parts.
#
[shaners] When Glenn comes back around, maybe he’ll accept a PR and/or transfer his repo to the mf org for ongoing stewardship.
tantek__, [aaronpk] and frmus25 joined the channel
#
frmus25 __
barpthewire, barpthewire1, Zegnat, KevinMarks and mrdata9 joined the channel
#
mrdata9 _.--"""""--._
[kevinmarks] joined the channel
#
Zegnat gRegorLove interesting catch on the implied photo on h-app! aaronpk was there a reason why h-app uses a logo property instead of a photo property?
#
Zegnat Also re: a discussion I just saw in #indieweb-dev about rel-icon `sizes` parsing in the mf2 parser; I brought that up completely separate from the indieauth client discovery thing. We include rel parsing in mf2, and if people want to use mf2 parsers to also parse link relationships it makes sense to me to not give them useless results (like a list of icons without a way to select the right one)
#
[kevinmarks] That makes sense to me.
#
Zegnat I’ll update the GitHub issue in a bit to capture that
#
Zegnat issueify all the things!
#
Loqi http://meme.loqi.me/m/4w61Ro5W.jpg
HackMaster18 joined the channel
#
@CadizMarbella https://waterpigs.co.uk/services/microformats-to-atom/?url=https://www.facebook.com/Clinica.Micropigmentacion.Capilar.Marbella mejor clinica capilar marbella, en sotogrande tattoo cejas pelo & pelo cordoba eyebrows perfect. Sotogrande Bolsas y Ojeras Marbella. En Benalmadena tatuaje cejas pelo por pelo en nerja eyebrows blameless Vitiligo Tratamiento. (twitter.com/_/status/1032568133251416064)
KevinMarks and [jgmac1106] joined the channel
#
ben_thatmustbeme who has access to transfer a repo to microformats org? i do not
#
Zegnat Hmm. I never know exactly what rights that needs. But if you don’t have them, I am guessing I don’t have them either
#
ben_thatmustbeme you and I oare only memebers
#
ben_thatmustbeme has to be an owner
#
ben_thatmustbeme https://github.com/orgs/microformats/people
#
ben_thatmustbeme i'll add aaron, though i'm sure he's sleeping now
#
Zegnat Loqi: is aaronpk sleeping?
[kevinmarks] joined the channel
#
[kevinmarks] I'm an owner
Cbcj joined the channel
#
@CadizMarbella https://waterpigs.co.uk/services/microformats-to-atom/?url=https://www.facebook.com/Clinica.Micropigmentacion.Capilar.Marbella Tratamiento contra la celulitis Marbella, valencia micropigmentacion cejas pelo a pelo motril eyebrows blameless. Sevilla quitar flacidez piernas Marbella. En Torremolinos dermopigmentacion cejas pelo & pelo, sevilla eyebrows finished Quitar cicatrices (twitter.com/_/status/1032590778269356034)
barpthewire, [pfefferle], Garbee_ and [jgmac1106] joined the channel
#
@brennanyoung @microformats Hey, is your site down? (twitter.com/_/status/1032603350922084353)
#
[jgmac1106] anyone know the address to @sknebel's mirror site for ^^
#
@HeNeArXn ↩️ appears so, having server troubles again ... As a fallback, you can find a mirror of the wiki at https://microformats.org.mirrors.sknebel.net (twitter.com/_/status/1032607139762765824)
barpthewire and [pfefferle] joined the channel
#
ben_thatmustbeme KevinMarks: sent an invite to you as well
#
ben_thatmustbeme https://github.com/dissolve/microformat-node/invitations
barpthewire and boars joined the channel
#
boars | _..._
barpthewire and [metbril] joined the channel
#
ben_thatmustbeme KevinMarks: you should be able to transfer it in to the microformats org now
#
ben_thatmustbeme i think
#
ben_thatmustbeme or do i have to tranfer it directly to you first so you are the owner then you can transfer it to microformats org?
#
ben_thatmustbeme ugh
barpthewire and [scottgruber] joined the channel
#
aaronpk good morning
#
aaronpk still need the repo moved?
#
aaronpk ben_thatmustbeme: I accepted the invite but it's not showing the settings tab so i'm guessing i didn't get added with the right permissions
#
ben_thatmustbeme i don't see an option to give more permissions than this, i think because its not in an organization
#
aaronpk i don't think that matters
#
ben_thatmustbeme it does
#
aaronpk oh gosh it does
#
ben_thatmustbeme ugh... so hmm
#
aaronpk can you move it to indieweb and then i can move it to microformats?
#
Zegnat “Users must have repository creation permissions within the receiving organization before they can transfer a repository that they individually own. If Allow members to create repositories for this organization has been disabled in the receiving organization, only organization owners can transfer repositories into the organization.”
#
Zegnat https://help.github.com/articles/transferring-a-repository-owned-by-your-personal-account/
#
ben_thatmustbeme i'm not an owner of indieweb either is seems
#
ben_thatmustbeme so, no, i cannot
#
aaronpk weird i thought like everyone was an owner of the indieweb org
#
aaronpk let me try this "allow members to create repositories" setting
#
sknebel turn on creation rights at microformats for a minute?
#
ben_thatmustbeme oh, its allowing me
#
aaronpk try now
#
ben_thatmustbeme i just hit to move it to indieweb
#
aaronpk oops
#
ben_thatmustbeme lol, and now i can't even get to the settings on it
#
ben_thatmustbeme https://github.com/indieweb/microformat-node
#
Loqi [indieweb] microformat-node: Microformats parser for node.js
#
aaronpk alright here it is https://github.com/microformats/microformat-node
#
Loqi [microformats] microformat-node: Microformats parser for node.js
#
ben_thatmustbeme grows impatient with github
#
Zegnat This org stuff can be really frustrating
#
ben_thatmustbeme now that i've used gitlab for work
#
ben_thatmustbeme i like it a lot better
#
ben_thatmustbeme can blame mattl for that one
#
sknebel ben_thatmustbeme: does that mean we now consider your fork the canonical home of the parser?
#
aaronpk what happened to glenn's version?
#
ben_thatmustbeme https://chat.indieweb.org/microformats/2018-08-23#t1534996492676700
#
Loqi [[shaners]] [ben_thatmustbeme] Thanks! Would you mind transferring your forked gh repo to the mf org please? And then I’ll wire up the Heroku auto-deploy parts.
#
ben_thatmustbeme https://chat.indieweb.org/microformats/2018-08-23#t1534996504994400
#
Loqi [[shaners]] When Glenn comes back around, maybe he’ll accept a PR and/or transfer his repo to the mf org for ongoing stewardship.
#
ben_thatmustbeme great, now i'll have to add the node parser to mf2-tester
#
aaronpk wait, is that project both the parser *and* the website at node.microformats.io?
#
ben_thatmustbeme i think so... its... odd
#
ben_thatmustbeme but i don't know well enough how to detangle the two
#
aaronpk that's weird
#
sknebel app.js is the web server, everything else is the parser I think
#
ben_thatmustbeme no wait, i think it just uses microformat-shiv to do the parsing
#
sknebel which again builds on microformats-shiv
#
aaronpk if this is just the website, then let's rename it to say that
#
sknebel it's not
#
ben_thatmustbeme its like... half the parser
#
aaronpk 🤔
#
sknebel microformats-shiv is the javascript parser
#
sknebel relying on browser APIs
#
ben_thatmustbeme but it seems like it does some additional bits around that
#
sknebel microformats-node is the parser for node JS, providing node replacements for the browser bits -shiv needs
#
sknebel and it contains the demo website for it
#
ben_thatmustbeme slowly backs away
#
ben_thatmustbeme i've done enough
#
sknebel /lib is the parser
#
sknebel so we now have a parser nobody feels like maintaining in the microformats org?
#
Zegnat Yikes
#
ben_thatmustbeme sigh... i'm going to end up maintaining this too aren't i?
#
Zegnat Well, if it is just to get node.microformats.io going again, that might not be the biggest problem? But then we should rename it not to advertise the repo as a standalone parser
#
sknebel has anyone talked to glenn in the past year?
#
sknebel about e.g. adding people that can at least in principle review and merge PRs?
#
sknebel I have an open one or two for ages
#
sknebel although it's probably lagging quite a bit, so not sure I'd recommend it without a bigger effort
#
sknebel so if it's not maintained, I'm not sure it makes sense to promote/list it
#
sknebel (I'd contribute the occasional bit if I can rely on patches not sitting around for a year, but outside sturdy-backbone I don't use it)
#
Zegnat Would be interesting to know who is depending on the node parser. Some of voxpelli’s stuff perhaps? Omnibear?
#
sknebel https://www.npmjs.com/browse/depended/microformat-node for things that have packages
#
sknebel https://github.com/search?l=JSON&p=2&q=microformat-node&type=Code for a few more
#
Zegnat Cool! That might warrant some looking into. If any actively developed project is using the parser, those are the people most likely to possibly start maintaining a fork
KevinMarks_ joined the channel
#
ben_thatmustbeme :https://ben.thatmustbe.me/mf2tests/
#
ben_thatmustbeme updated with node parser results
#
ben_thatmustbeme what this really calls in to question is, who maintains microformat-shiv ?
#
Zegnat Also just glenn, I believe
#
sknebel as above
#
@CadizMarbella https://waterpigs.co.uk/services/microformats-to-atom/?url=https://www.facebook.com/Clinica.Micropigmentacion.Capilar.Marbella Sonrisa de Hollywood #Marbella, estepona micropigmentacion cejas pelo por pelo sevilla eyebrows ideal. en Nerja Tratamiento de colageno para el cabello Marbella. La Linea micropigmentacion de cejas pelo a pelo, velez-coin eyebrows finished Aumentar labios (twitter.com/_/status/1032648163788771329)
jackjamieson and k6ka25 joined the channel
#
k6ka25 _.--"""""--._
gRegorLove and KevinMarks joined the channel
#
ben_thatmustbeme more imporantly, how much of a pain are these test-set changes being on firefox devs?
KartikPrabhu joined the channel
#
sknebel ?
barpthewire joined the channel
#
ben_thatmustbeme trying to find the comment
#
ben_thatmustbeme but there was something about firefox uses the microformats/tests repo for some automated testing
#
ben_thatmustbeme since it has microformat-shiv in the browser
#
ben_thatmustbeme https://github.com/microformats/tests/issues/74
#
Loqi [glennjones] #74 Changes to tests can block updates in Firefox
#
Zegnat I don’t know anything about the tests being used internally at Mozilla. Probably need to ping tantek to confirm anything about that.
#
Zegnat But as mf-shiv isn’t really getting updates at the moment anyway, I don’t know if it would matter that us updating tests may block Mozilla from updating mf-shiv?
#
ben_thatmustbeme on another note should we not ask willnorris to about moving the go parser to the microformats org?
#
Zegnat That has just him writing it right? Not sure if that qualifies as a community project? Though we haven’t set any real guidelines for being included in the org yet, I thought something about that was mentioned
#
gRegorLove "Fatal error: Out of memory" on the wiki
manish6 joined the channel
#
manish6 ___
[shaners] joined the channel
#
[shaners] I think that we should rename the repo from `microformat-node` to `microformats-parser-website-node`, for consistency.
#
[shaners] In time, if someone wants to, they can separate out the two things: website, parser
#
[shaners] [aaronpk] I don’t have mf org permissions to rename a repo. Can you do it please?
#
gRegorLove merged a few more microformats/tests PRs
#
aaronpk from what i understand that repo is not just the website tho
#
Zegnat gRegorLove, nice. I should go and rebase the PHP PR that runs them :)
#
[shaners] I agree that it’s not just the website. But for our purposes, we’re using that repo as just the website.
#
[shaners] a note can be added to the README explaining what’s happening
#
aaronpk 🤔 there is no "Parsers" header in this TOC http://microformats.org/wiki/microformats2
#
gRegorLove Implementations header iirc (can't get it to load)
#
aaronpk oops weird
#
aaronpk out of memory again
#
aaronpk aaronpk@microformats:~$ ls
#
aaronpk -bash: fork: Cannot allocate memory
#
[shaners] I also agree that this should really be split out into its own repo, but until then, I think the naming consistency is worth it.
#
Zegnat Implementations header it is: https://microformats.org.mirrors.sknebel.net/w/index.php?title=Microformats2#Implementations
#
Zegnat Has a parsers subheading though: https://microformats.org.mirrors.sknebel.net/w/index.php?title=Microformats2#Parsers
#
aaronpk i was looking at the wrong page because the browser hadn't loaded yet lol
#
sknebel the split should be easy-ish, can give it a try later
#
[shaners] thanks @sknebel
#
sknebel as in, make a repo with the website that pulls in the parser package as a dependency
#
[shaners] sure!
#
willnorris ben_thatmustbeme: regarding the go parser, I'm no opposed to moving it into the microformats org. The thing I care more about is the go import path. In go, import paths are effectively URLs, and use a "go-import" meta tag to point to the source control repo (e.g. view source of https://willnorris.com/go/microformats and search for "go-import"). This provides a level of indirection that would let us move the repo
#
willnorris without affecting the import path. Or alternately, we could change the import path to something under microformats.org, though with the recent instability of the site, I worry about that, since when the site is down, you can't easily install the package using `go get`. The thing I don't want to do is have an import path of "github.com/....", since that's just another form of sharecropping.
KevinMarks and [pfefferle] joined the channel
#
willnorris gRegorLove: if you still happen to be around... https://github.com/microformats/tests/pull/104
#
Loqi [willnorris] #104 sort types in v1 tests
[jgmac1106] and Mr_Sheesh joined the channel
#
Mr_Sheesh ))))))))(__/~;;\
NvpkD1y7Ez joined the channel
#
NvpkD1y7Ez | __
#
ben_thatmustbeme totally understandable, was just a question really
#
ben_thatmustbeme https://ben.thatmustbe.me/mf2tests/
#
ben_thatmustbeme much more compact view now
#
willnorris i'm having trouble with the additional "dist/" you added to the links.
#
ben_thatmustbeme yeah, i just fixed that
#
ben_thatmustbeme it should be gone
#
KartikPrabhu ben_thatmustbeme: would be good to have the "x of y passed" up on the top for a quick summary
#
ben_thatmustbeme *blinks* sigh, gotta make extra work for me huh?
#
willnorris could you also update the README to reflect the reorganization? (and add the `npm install` step for node)
#
willnorris :)
#
ben_thatmustbeme willnorris: done
#
willnorris thanks!
#
ben_thatmustbeme super easy to add another language now too
#
ben_thatmustbeme i want to add a link for the parsers as well, i'll get to it
#
KartikPrabhu ben_thatmustbeme: yes! maybe from microformats.io
tantek__ joined the channel
#
KartikPrabhu it might get difficult to keep all the versions synced
[dougbeal] joined the channel
#
KartikPrabhu ha! lol at new PR ben_thatmustbeme ;)
#
KartikPrabhu s/PR/commit
#
ben_thatmustbeme :P
#
ben_thatmustbeme udpated KartikPrabhu
#
ben_thatmustbeme https://ben.thatmustbe.me/mf2tests/
#
KartikPrabhu soooo much better :P
#
ben_thatmustbeme if you want to add a parser https://github.com/dissolve/mf2-tester/tree/master/languages its just adding a folder with 5 things here
#
KartikPrabhu actually, now I think PHP and Python are just failing random things like ordering and whitespace
#
ben_thatmustbeme ordering no
#
ben_thatmustbeme the test suite is fixing that
#
ben_thatmustbeme whitespace it could be, yes
#
KartikPrabhu hmm ok will take a more detailed look
#
ben_thatmustbeme although given the new PR, i may take out the ordering of array eventually
MetBril joined the channel
#
aaronpk I see a bunch of pending php-mf2 PRs. let's see if I can have a look
#
KartikPrabhu I just don't like that Go and Ruby are beating Python :P
tantek joined the channel
#
MetBril System Info: Model: iPad Air 2 · iOS: 11.4.1 · RAM: 1,94 GB · Disk Space: 59,6 GB · GPU: PowerVR GXA6850 · Screen Resolution (Portrait): 2048x1536 · Battery: 100% · Uptime: 23d · Client: Mutter 1.27 (Build 1815618)
#
KartikPrabhu eh!?
#
MetBril Just testing my iOS client
#
MetBril Didn't know it would be posted online
#
ben_thatmustbeme KartikPrabhu: wait until the next version of ruby drops
#
KartikPrabhu or the tests are fixed :P
#
ben_thatmustbeme i think its up to 107
#
sknebel "fixing" the tests requires making a decision on whitespace
#
KartikPrabhu sknebel: true
#
ben_thatmustbeme i thought a decision had been made
#
sknebel no
#
sknebel the decision is "the current state is bad"
#
KartikPrabhu the whitespace stuff is pretty "cutting edge" in PHP and Python on purpose
#
KartikPrabhu to see if it works
#
ben_thatmustbeme this is "trimming starting and ending spaces" in html results?
#
sknebel aaronpk drafted some cases, Zegnat made an algorithm proposal, php and python have variations of that implemented
#
sknebel no
#
sknebel p- properties
#
KartikPrabhu and e-*>value
#
ben_thatmustbeme oh, that i have not been following
#
sknebel so every test case with e- is almost expected to be broken in those
#
KartikPrabhu yup
#
ben_thatmustbeme well, is that a released version?
#
sknebel yes
#
ben_thatmustbeme weird, experimenting publicly
#
KartikPrabhu because real world USE-CASES
#
KartikPrabhu like bridgy, and aperture
#
KartikPrabhu or x-ray, one of those
#
ben_thatmustbeme fair
#
ben_thatmustbeme just seems odd at first though
#
KartikPrabhu both php-mf2 and mf2py have been on the bleeding edge for a while now
#
KartikPrabhu actually, mf2py might fail a lot more tests if you turn on the alt-parsing stuffs
#
sknebel oh right, we should progress that
#
KartikPrabhu yeah. that and lang-parsing which isn't in mf2py yet
#
KartikPrabhu but is in php-mf2
#
sknebel does anything consume that yet?
#
sknebel bridgy uses the alt stuff
#
KartikPrabhu yes, bridgy use alt. not sure about consumers of lang
#
sknebel also the question: does everyone put the alt= behind a flag?
#
sknebel for how long?
#
KartikPrabhu sknebel: my original thought was that since it is a "breaking" change it should be under a flag and hopefully by v2.0.0 it will be in the spec
#
KartikPrabhu or if it goes into the spec then jump to v2.0.0
#
sknebel so we say every parser does a major release and consumers adjust at that point
#
sknebel ?
#
KartikPrabhu yes
#
KartikPrabhu or at least that is how I thought "semantic versioning" worked
#
KartikPrabhu <shrug>
#
KartikPrabhu IANAD ;)
[pfefferle] joined the channel
#
willnorris what is the alt= stuff you're referring to? is that https://github.com/microformats/microformats2-parsing/issues/2 ?
#
Loqi [aaronpk] #2 image alt text is lost during parsing
#
KartikPrabhu yup
#
KartikPrabhu willnorris: mf2py does the thing mentioned in https://github.com/microformats/microformats2-parsing/issues/2#issuecomment-392360481
#
Loqi [kartikprabhu] as proof of concept, this has been implemented in experimental version of mf2py for **explicit** `u-photo` parsing. ## Example 0 ```html <div class="h-entry"> <p class="p-name e-content"><span>Hello World</span></p> <img class="u-photo"...
#
KartikPrabhu but it is under a flag that needs to be explicitly turned on
#
KartikPrabhu as documented here : https://github.com/microformats/mf2py#experimental-features
#
Loqi [microformats] mf2py: Python Microformats2 parser
#
willnorris behind a flag, but in the main released branch? I've been trying to figure out how to handle that... implementing proposed changes that have not yet been accepted. I was considering doing it in a separate, unreleased git branch. I don't yet have a great way to pass flags to the parser, though it wouldn't be hard to add
#
KartikPrabhu sknebel: is this still accurate https://github.com/microformats/mf2py#faq ?
#
Loqi [microformats] mf2py: Python Microformats2 parser
#
KartikPrabhu willnorris: yes, behind a flag in the released version
#
KartikPrabhu mostly since bridgy is a big user of mf2py
#
KartikPrabhu otherwise this would have only been in some epxerimental branch
tantek joined the channel
#
aaronpk ugh, struggling to find the actual markup that's causing this error
#
KartikPrabhu aaronpk: context for this channel?
#
aaronpk https://github.com/microformats/php-mf2/issues/196
#
Loqi [aaronpk] #196 [error] PHP Fatal error: Cannot use object of type stdClass as array
#
KartikPrabhu huh! that is a weird bug
#
aaronpk I have a fix for it, i'm just trying to write a test case
#
KartikPrabhu doesn't any element with no mf2 properties work?
#
aaronpk nope
#
KartikPrabhu hmm PHP is werid
#
aaronpk has something to do with the fact that it's nested
#
Zegnat The problem is that we are forced to use a class instance just to get {} in the final JSON. PHP is weird in that there isn't a dictionary type we can use.
#
Zegnat But if we transform the empty list to a class instance too early, the rest of the code is going to fail :(
#
KartikPrabhu sounds annoying
tantek joined the channel
#
aaronpk Zegnat: I think the bug was fixed in some of the PRs I just merged, but I don't understand how
#
aaronpk i'm narrowing down this markup that's failing until I can find the particular bit to understand more
#
Zegnat I'm busy this evening. If you can't pinpoint it exactly, tag me in the issue and I'll have a go at it tomorrow.
#
Zegnat We may just want to see if we can't move the conversion to empty objects right before we json_encode. We might be doing it too early and it could come back to bite us later.
#
Zegnat If it still works how I remember it.
#
aaronpk tracked down the most minimal example that triggers it
#
aaronpk <div class="h-entry"> <li class="h-cite u-comment"> <div class="vcard"></div> </li> </div>
#
aaronpk the vcard is the thing that triggers it
#
KartikPrabhu hmmm is the mf1 property essential?
#
KartikPrabhu oh!
#
aaronpk the good news is enough of the backcompat stuff changed between the current release and current master that this is no longer a problem
#
KartikPrabhu weird. removing the <li> makes it work again
#
aaronpk yeah it has to do with the nesting
#
gRegorLove aaronpk, which line in current master? #1412 has changed with the merges.
#
aaronpk ah shoot
#
aaronpk now 1399 https://github.com/microformats/php-mf2/blob/master/Mf2/Parser.php#L1399
#
aaronpk what's annoying to me is that now I can't figure out how to write a test to trigger the error
KevinMarks joined the channel
#
aaronpk since the actual place the error occurred didn't change
#
gRegorLove aaronpk, Added that comment to PR #189
#
aaronpk thx
#
aaronpk for your review https://github.com/microformats/php-mf2/pull/197
#
Loqi [aaronpk] #197 check that properties is an array before accessing
#
gRegorLove Is this with the HTML5 lib only?
#
aaronpk oh I didn't think about that
#
aaronpk I don't think that would matter?
#
gRegorLove I couldn't duplicate with your snippet above
#
aaronpk it fails on 0.4.5 but not in current master
#
gRegorLove I wouldn't think so, not sure.
#
aaronpk I figured i'd add the test and fix anyway
#
aaronpk I think something about backcompat parsing means `properties` is never set instead of set to an empty object?
#
willnorris just added support for the include-pattern in the go parser, bringing it up to 114/117 tests passing. Only remaining three are awaiting issues in test suite or parsing spec to be resolved (https://github.com/willnorris/microformats/blob/master/testsuite_test.go#L42-L46)
#
KartikPrabhu is there even a spec for the include-pattern in backcompat parsing!?
#
KartikPrabhu not sure why it is in the tests in the first place
#
@stephaniehobson ↩️ I remember microformats blowing my mind back in 2007. I'd like to have updated info on the state of microformats/microdata/schema and who and how they're consumed. (twitter.com/_/status/1032714998139650048)
#
willnorris not 100% sure. But there were tests for it, so I implemented it :)
#
willnorris it was definitely the weirdest thing to implement
#
willnorris https://github.com/willnorris/microformats/commit/aa06c7b85e1a6b488d2609ee5036144ff70acc2c
#
@kevinmarks ↩️ Microformats are still going; they got rethought to not require each parser to have specific vocabularies included http://microformats.org/wiki/microformats-2 and are used for #Indieweb now https://indieweb.org/microformats (twitter.com/_/status/1032716586883395585)
#
tantek__ re: include-pattern, interesting willnorris, didn't even realize we still had that in tests!
#
tantek__ I'm not aware of anyone currently using it in real world publishing
#
tantek__ I guess it's good that it's still implementable in the context of mf2!
#
tantek__ but is it what we want?
#
willnorris Yeah, I can't imagine it's widely used, though I suppose the use case still exists?
#
tantek__ worth re-exploring / re-analyzing
#
tantek__ I vaguely remember hResume driving the use-case originally
#
tantek__ and I don't know many people who are publishing h-resume yet: http://microformats.org/wiki/h-resume#Examples_in_the_Wild (just a couple there)
#
tantek__ should probably update his accordingly, dogfooding as editor and all
#
tantek__ kevinmarks++
#
Loqi kevinmarks has 3 karma in this channel over the last year (30 in all channels)
#
Zegnat https://petermolnar.net/about.html is also h-resume (via https://indieweb.org/resume)
#
tantek__ Zegnat, feel free to add it to ^^^
#
tantek__ !tell kevinmarks here's another one you may want to respond to in that thread: https://twitter.com/dgwyer/status/1032628574585536513
#
Loqi Ok, I'll tell them that when I see them next
#
Loqi [@dgwyer] @jensimmons Right now trying to deciding how best to implement http://Schema.org, and whether to use RDFa, Microdata, JSON-LD etc. 😕
#
Zegnat Not at PC, editing wikis would be annoying. Can do in a bit though
MetBril, KartikPrabhu and KevinMarks joined the channel
#
zegnat edited /h-resume (+140) "/* Examples in the Wild */ Add petermolnar" (view diff)
#
tantek__ Zegnat++ thank yoU!
#
Loqi Zegnat has 18 karma in this channel over the last year (146 in all channels)
#
tantek__ now the question is, does petermolnar's h-resume use the include-pattern or not?
#
Zegnat Probably not. I don’t think anyone implements that and I seem to recall he checked his markup with the modern mf2 parser
#
Zegnat But I just added it to the wiki now right before shutting off and going for bed. Can confirm in the morning
#
Zegnat Have a good one!
#
tantek__ good night!
#
Loqi see you in the morning!
[kevinmarks] joined the channel
#
[kevinmarks] I remember the include pattern use case being calendar grids so you can get the place and time from the row and column heads.
#
Loqi [kevinmarks]: tantek__ left you a message 49 minutes ago: here's another one you may want to respond to in that thread: https://twitter.com/dgwyer/status/1032628574585536513
#
tantek__ kevinmarks, table th td parsing was a different thing
#
tantek__ from include-pattern
#
gRegorLove I started (very briefly) looking for any include-patterns that were still published. Didn't find any yet.
#
gRegorLove Should we leave Glenn's live parser on this list with a note about the https cert, or remove it temporarily? http://microformats.org/wiki/microformats2#Live_Textarea_Input
#
gRegorLove I'm bumping pin13 up in that list
#
gRegorLove or maybe just the microformats.io ones
[manton] joined the channel
#
aaronpk thx gRegorLove
#
aaronpk nice little chunk of improvements there, guess it's time for another release!
#
voxpelli Zegnat: sknebel: I’m using the node parser, yes
#
voxpelli If you need help, can you maybe open an issue at my WebMention repo? I still haven’t really got back time to track these channels well :/
#
gRegorLove I might have another PR tonight for <img> in implied p-name
#
aaronpk cool, i'll wait
KartikPrabhu, [tantek] and [dougbeal] joined the channel
#
gRegorLove Submitted, just awaiting CI
[cleverdevil] joined the channel
#
KartikPrabhu the include pattern is quite the anomaly because it it "non-local" i.e. depends on the entire document. It would totally fail if someone used a part of the HTML which is valid mf1 but the included bit is no longer in that part
#
KartikPrabhu nothing else in microformats does this
#
willnorris KartikPrabhu: it really is an anomaly. given that we can't seem to find any use of it in the wild, do we just remove the tests entirely? Is it worth specifically excluding from mf2 backcompat parsing? Or is that implied given that its never explicitly called out for inclusion?
#
KartikPrabhu willnorris: I thought since it never is mentioned in backcompat it shouldn't be parsed. But I only found about the include-pattern a few days ago!
#
willnorris I only found out about through the test suite. I'd never heard of it before
#
KartikPrabhu for instance the value-class-pattern is always explicitly mentioned in places where it is used I think
#
KartikPrabhu but had never heard of the include-pattern
#
KartikPrabhu since, it is on people's radar now, we should wait for consensus and a spec edit/explicit mention
#
KartikPrabhu maybe then alter the tests
#
willnorris nodes
#
willnorris nods*
davidmead joined the channel