@ochtendgrijs↩️ Ondertussen draait Apache op Drupal. Mogelijk probeer ik nog om op basis van de homepage m’n eigen RSS te genereren. Dat zou makkelijker zijn als er voor microformats was gekozen. (twitter.com/_/status/1407234126072225792)
[KevinMarks]Nothing stands out from this year, though that's true in a broader sense too. The idea of adding CI tests to check that your microformats still work may be worth emphasising
barnaby, [jgmac1106] and rockorager joined the channel
barnabyI assume there was discussion about it at some point, and a reason not to migrate. possibly due to wanting to support existing accounts, and mediawiki not supporting multiple authentication options? but I don’t know exactly
rockoragerWorking through the authorship-spec and the representative-h-card algorithm...I noticed that at no point does the authorship spec say to use a top-level h-card from the page in question
rockoragerSo on example.org/page, if there is a top-level h-card but no other reference to an author, you wouldn't *technically* define that top level as the author
rockoragerWhich I guess makes sense for sites with many authors, the top level would be the org's h-card and not the author's. But presumably they'd have an authorship reference *somewhere* else
rockoragerAnyways, it seemed like as a last ditch effort...after checking h-entry.author, h-feed.author, rel=author, then a top-level h-card on that page could be used
barnabyrockorager: “7.4 if the h-entry's page has 1+ h-card with url == author-page URL, use first such h-card, exit.” is close but still relies on there being an explicit author URL somewhere
[tantek]I omitted a “plain” top level h-card like that because we found too many false positives at the time (top level h-cards that did NOT represent the author
[tantek]it's going to be a hard one to "get right", as the way timezones work in vcard/ical is very weird, and timezones as a whole are an iffy thing to denote (quite the disconnect between complexity, automated processing ability, actually representing what a user would want to show/display or already does on their homepage, and actually representing something useful to parse and do something with)
barnaby^^^ [tantek] if you have similar comments about why the other reserved properties have that status, feel free to add or let me know here. I have my suspicions about why they weren’t used, but wasn’t part of the mf1->mf2 migration so don’t want to write something inaccurate
barnabywaltersedited /h-card (+771) "/* Implementations */ added some of the more notable indieweb software which publishes/consumes h-card" (view diff)
barnabyis there a summary of current mf2 pronoun markup anywhere? there are many different proposals, examples and discussions spread across the MF and IW wikis
ZegnatI am not sure there is a "current mf2 pronoun markup", other than running with any of the many proposals. Does not feel like the community as a whole has landed anywhere yet, last I checked.
[tantek]Zegnat, looks like /pronouns currently redirects to that section, which has grown large enough that it's likely worth moving to its own page (replacing that redirect with the actual content), leaving perhaps a 2 sentence summary in the brainstorming page
[tantek]we do also have a separate /gender page which has even more specific pages if you'd like to see a model of how the content could be split up according to microformats process methods
[tantek](I did that a while ago (on the video page) as part of trying to see if the markup used was consistent enough to help advance the u-video property)
[tantek]this is why I directed you to the /gender page for a structure to consider copying for /pronouns (top level), /pronouns-examples (documentation of real world publishing of pronouns content), /pronouns-formats (any existing attempts to provide formal structured formats either in plaintext or in markup), and /pronouns-brainstorming
barnabywe also mention on the wiki that any proposed h-card properties should also be proposed to vCard, how seriously are we taking that at the moment?
[tantek]the *-examples documented on the microformats wiki are more often from *anywhere* (not just personal websites), and very often not from folks in the community, more of a "anything on the web" reach
[tantek]yes the higher level goal there is to not diverge (e.g. have different approaches) from vCard. it's ok if there are vCard properties that we don't make "official" in h-card (because a lot of vCard is aspirational tbh, having participated there), and it's ok if we have h-card additions which aren't in vCard yet
[tantek]yes the individual examples would be in -examples (the key aspect is that they are publishing the *information* about pronouns; the markup is irrelevant to whether they are an example or not)
[tantek]no the different "approaches" to markup are not -formats, there is no spec! what they could be taken as is *-brainstorming, since they're *experiments* (at best), which is very far from any kind of actual format (though is useful input *for* a format)
barnabyokay, and -formats is for existing formats with implementations containing pronoun info, and the currently published experimentation is in -brainstorming
barnabywalterscreated /pronouns-examples (+2450) "Created page with "This page documents specific examples of how pronoun information is currently published on the web, as well as UIs which support pronoun fields. == Sites and Services == Exam..."" (view diff)