#microformats 2023-11-10

2023-11-10 UTC
plantroon and Kaja joined the channel
#
[KevinMarks] Found via that old Mark Pilgrim post https://web.archive.org/web/20110717125354/http://evan.prodromou.name/RDFa_vs_microformats
#
[jacky] We didn't GWG
#
[jacky] I'm down to suggest some times!
#
GWG [jacky]: Meetable supports tentative statuses
gRegorLove_ joined the channel
#
GWG But when we did the roundtable, we had too many issues trying to pack the agenda.
#
GWG I think having a... let's set agenda based on attendees would work better for success
[tantek], [snarfed] and [catgirlinspace] joined the channel
#
[jacky] ah (I missed the roundtable)
#
[jacky] that sounds like a good idea (in the sense that'll prioritze participation over getting through it all)
#
GWG What we need is 3 people who commit to showing up at a specific time to schedule it, I believe
#
[tantek] GWG, it's a mix. We also need people to step up and make comments to move issues along the process
#
[tantek] Without at least some of that async participation, then it takes too long to rediscuss an issue from scratch in a sync meeting
#
[tantek] these kinds of (standards related) meetings are most effective/efficient when participants do some work first in preparation, on the issues, their implementations, test cases etc.
#
[tantek] otherwise there's not much actionable that comes out of them, and they turn into more general informative/discussion sessions. that's fine for an indiewebcamp, but if your goal is to actually make progress on a spec, then that's not the way to do it
#
GWG I know... but I think once we establish this, after meeting 1, we'll have async if we schedule them regularly
#
[tantek] GWG, we just had session/meeting 1 at IWC NUR, and haven't seen much additional async activity afterwards
#
[tantek] at the current "pace" of issues and issue comments, I wouldn't recommend anything more often than once a quarter at most
#
GWG I was thinking of it more as a mindset tool
neceve joined the channel
#
[tantek] GWG, it could be useful as a general microformats Q&A / support forum, to help answer questions and document new issues
#
[jacky] okay how about this
#
[jacky] I'm down to do something around rsvps and push conversation there
#
[jacky] or look at a list of open things
#
[jacky] on a "adopt a bench" kind of thing (heh
#
[jacky] and each of us could try that
#
GWG [jacky]: We did some RSVP and status speculation a while back I'd love to iterate on
#
[jacky] i'll read https://indieweb.org/2023/Nuremberg/mf2 and I'll come back to that
#
GWG These statuses https://github.com/microformats/h-entry/issues/18#issuecomment-624994221
#
[tantek] GWG, I think the key thing is to start with documenting your permalinks of such "status" posts, before trying to speculate or brainstorm about markup
#
[tantek] without a record of folks publishing such "status" information, there's very little reason to invest any time in inventing markup for it
#
[tantek] nevermind also consuming code use-cases
#
GWG I know... I'm saying I'd like to pursue that myself
#
GWG And the merge review into entry conversation.
#
GWG I would do that on my site with an experimental review-of property today
#
GWG Anyone want to post experimental h-entry reviews with me?
#
[tantek] GWG what do you mean by an "h-entry review"?
#
[tantek] are you talking about this issue? https://github.com/microformats/h-entry/issues/32
#
GWG [tantek]: Yes.
#
Loqi [preview] [barnabywalters] #32 Consider merging h-review properties into h-entry
#
GWG [tantek]: Reviews have been on my list for a while... but my design didn't support anything but h-entry so I put it off.
#
[tantek] GWG, that's worth adding as a comment on that issue, that the design of your software at least being based on h-entry means it would make it easier for you to support, rather than having to support a new top level microformat
#
GWG It's also why I don't do events
#
GWG It would require a bunch of tweaks
#
[tantek] events are very different than posts so I think it's ok that they still keep their own microformat type
#
[tantek] I definitely had to write a bunch of custom code to make events work, with RSVPs and such. the microformats type (h-event) was the least of the work
#
gRegor In addition to the Nuremburg mf2 session, it's worth reviewing https://indieweb.org/pop-up#Prerequisites and the last popup's notes https://indieweb.org/2020/Pop-ups/Microformats, some which may be resolved after Nurbemburg of course.
#
gRegor I've only skimmed the Nuremburg mf2 session so far
#
[tantek] I still have a bunch of follow-up to do after that session 😕
#
gRegor Agreed, quarterly seems like a reasonable pace
[schmarty] joined the channel
#
t​haidaree quick question. I'm a single author on my page on the domain that I control. all the articles are written by me. If I put rel="me" somewhere in the footer, do I need to mark authorship on "h-entry" content as well?
#
[tantek] that's not what rel="me" is for
#
[tantek] it's always better to explicitly markup your authorship on your h-entry microformats
#
gRegor Do you have your name and photo marked up somewhere on your site with h-card already?
#
[tantek] also this might be better for the #indieweb-dev channel since it is a how to use microformats question in the context of marking up a blog post, rather than about discussing issues/changes in microformats themselves
#
[snarfed] thaidaree also see https://indieweb.org/authorship and https://microformats.org/wiki/representative-hcard
#
t​haidaree Thanks. Authorship link clears up the confusion for me.