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
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.
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)
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
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
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."
@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
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__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
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__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.
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_...
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.