#microformats 2018-02-16
2018-02-16 UTC
[kevinmarks], KartikPrabhu, [eddie], tantek, [shurcool], [prtksxna], barpthewire, gRegorLove_, nitot, [gerwitz], nitot_, MeanderingCode, [cleverdevil] and vivus joined the channel
#
Zegnat It looks like tantek, aaronpk, and I are all in agreement on the p-name resolution. See last proposal in this comment: https://github.com/microformats/microformats2-parsing/issues/6#issuecomment-366298739

#
Loqi [Zegnat] Documenting from yesterday’s chat, because nobody could remember this and I can’t find it elsewhere:
* @tantek would like to [keep parser changes conservative](https://chat.indieweb.org/dev/2018-02-15/1518732086447100) but [is “amenable to e...

#
KartikPrabhu Zegnat: will take a look this weekend and see

[kevinmarks] joined the channel
#
[kevinmarks] I would like to move mf2py into microformats - what would be the best way to integrate it with the tests repo? Last time I spent a chunk of time on this being bale to iterate on the tests and the parser I'm parallel was really handy

#
[kevinmarks] Unless we can pesatas them other bridgy

#
[kevinmarks] ;)

#
KartikPrabhu is very bad at tests

[eddie] joined the channel
#
gRegorLove Re: php-mf2 semver, this merged commit (still unreleased) is a breaking change, so it would probably be good to get the implied p-name in the same release since it's also breaking. I'll work on it soon.

#
gRegorLove For clarity, are there any objections to how Zegnat stated it here: https://github.com/microformats/microformats2-parsing/issues/6#issuecomment-366298739

#
Loqi [Zegnat] Documenting from yesterday’s chat, because nobody could remember this and I can’t find it elsewhere:
* @tantek would like to [keep parser changes conservative](https://chat.indieweb.org/dev/2018-02-15/1518732086447100) but [is “amenable to e...

#
gRegorLove If not I'll do that, otherwise I'll do the more conservative option.

#
gRegorLove I interpret the original as the more conservative option: https://github.com/microformats/microformats2-parsing/issues/6#issuecomment-355632808

#
gRegorLove The other one is where you're "amenable" to expanding to e-*

#
gRegorLove Now I'm getting confused, heh.

#
gRegorLove The original proposal is "p-name MUST NOT be implied if there are any explicit p-* properties or any nested microformats"

#
gRegorLove A newer alternative is "p-name MUST NOT be implied if there are any explicit p-* or e-* properties, or any nested microformats."

#
gRegorLove So if no objections to the newer alternative, I'll work on that in php-mf2.

#
gRegorLove Aha

#
gRegorLove I thought your objection to Zegnat's original proposal was the preference for more conservative parser changes, so I didn't think it was an option currently.

#
gRegorLove Zegnat on gh: "I have not been able to document any cases where more than this is necessary either.

#
gRegorLove "

#
gRegorLove "this" being the newer alternative.

[cleverdevil] joined the channel
#
Zegnat Currently voting on the proposal as iterated in aaronpk’s latest comment: “the current proposal of having p-* and e-* and h-* stop the implied name” https://github.com/microformats/microformats2-parsing/issues/6#issuecomment-366308533

chrisaldrich joined the channel
#
gRegorLove +1'd

barpthewire, eddie, tantek, [kevinmarks], [eddie], [cleverdevil], KartikPrabhu, gRegorLove and [mifga] joined the channel