[jgmac1106], TehNut, [pfefferle], tantek, barpthewire, profall0, drot21, strugee and barpthewire1 joined the channel
#ben_thatmustbemeHmm make s ticket for every issue I find with the test set?
#ben_thatmustbemeFor every test that is. Several have implied name/url issues
#sknebelnah, make a summary issue for similar issues. or submit a PR fixing it :D
barpthewire, tantek__, Sebastien11, [eddie], Humbedooh17, barpthewire1, vivus, planetmaker25, drakythe24 and Sitri17 joined the channel; vivus left the channel
#ben_thatmustbemehmm, you aren't supposed to imply name when a back-compat root right?
#aaronpkwell step 1 is inventory all the extensions used and see if they are available in the current MW version. then figure out whether the theme is compatible.
#sknebelthere should be a list of extensions on the wiki
#aaronpkupgrading MW will almost certainly require upgrading PHP (which should happen anyway), but that means we need to also upgrade the wordpress that's there (which should also happen anyway)
#sknebeland the question if preserving the theme is more important than having a functioning site
DarkMukke14 joined the channel
#aaronpkright, we made the call on the indieweb wiki that it was not worth it
#sknebelnot going to play software-archeologist and try to run outdated, possibly dangerously broken versions of software I barely understand on a modern system :D
strugee, arooni20 and [kevinmarks] joined the channel
#sknebelben_thatmustbeme: the name thing is interesting... I would have interpreted the parsing rule such that a name shouldn't be implied, but parsers seem to do it
iwaim_ joined the channel
#gRegorLoveIn that instance, looks like php-mf2 isn't keeping track when geo gets updated to p-geo h-geo, so it thinks that's an explicit h-geo
#gRegorLove"If an <abbr> element is used for a property, then the title attribute of the <abbr> element is the value of the property, instead of the contents of the element, which instead provide a human presentable version of the value."
#ZegnatThe spec says to parse class="geo" as a "p-geo h-geo", but the example in the test case does not contain any property elements at all
rogue2, gRegorLove and jackjamieson joined the channel
#@taravancil↩️ Yeah we’ve done a deep dive on ActivityPub, JSON-LD, microformats, and all the other attempts to standardize on that front, and we didn’t come out on the other end feeling confident in any one of them. (twitter.com/_/status/1028008463165804544)
cebor, [eddie], t0ne9, j12t, tantek__ and [kevinmarks] joined the channel
#tantek__so if folks wanted to they could just pass around mf2json, and thus be compatible with everyone else consuming mf2 via a JSON parser
#tantek__zegnat, yes, improving that page (and maybe name)
#aaronpkyeah there's a lot of value in the microformats vocabulary even if you don't use it with HTML
iwaim joined the channel
#ZegnatThat page was written to explain the format of the JSON, not really as a usecase page. But there was a use at the time because more people started with micropub and microsub and were running into mf2 JSON
#tantek__yes that page needs lots of improvements in order to be a "first stop" reference
#tantek__simpler / better / more "real world" examples to illustrate each feature
#tantek__the need to do that (write *separate* parsing for hcalendar) was one of the nits that stuck in my head motivating subsequent brainstorming, design, iteration of microformats2 the next May
#gRegorLoveso hCalendar 1.0.1 and 1.1 were brainstormed but didn't make it to full specs?
#tantek__right, so they remained as errata / patches to 1.0
#tantek__there's probably some value in going through existing hCalendar implementations, seeing what got adopted from brainstorming etc., and formalizing those into a "frozen" version of those specs to document implementation interop
#tantek__and similar if people are publishing using those patterns, those can feed into back-compat parsing section in /h-event
#tantek__gRegorLove: that "frozen" version of hCalendar would be either 1.0.1 or 1.1 depending on the kind/number of changes accepted from brainstorming etc.
#tantek__would love to do a longer brainstorming session on that with you, since you've implemented a bunch of h-event processing code
#tantek__and publishing too vis-a-vis the indieweb /events page templates
#Loqi[gRegorLove] This is currently awaiting examples in the wild of hReview with `fn`, `photo`, or `url` properties that are _not_ nested in an `item`. I've been working through [hReview Examples in the wild](http://microformats.org/wiki/hreview-examples-in-wild#New_...
#gRegorLovetantek__, Yeah, let me go through these other hReview pages more
#[kevinmarks]Indentation and whitespace is possibly an even bigger religious war than json vs html
[schmarty], barq13 and dh128 joined the channel
#gRegorLoveFrom hcalendar-brainstorming, I think we can add Tabular event calendars to the spec. hCard locations/attendees/organizers is already on the spec page as "may", so I think that's good.
#gRegorLoveShould add the <time> authoring to the spec