SeirdyWAI-ARIA's role="comment" seems basically equivalent to microformats2 comments except more powerful, since it's easy to make a comment and id semantically linked in a bi-directional manner.
Seirdyi implemented them for displayed webmentions on seirdy.one. example page: https://seirdy.one/2020/11/23/website-best-practices.html. Now I just have to also display webmentions that point to in-page anchors and make those semantically linked to just the sections they reference.
Seirdylowkey thinking that we should at some point make microformats3 and make it use "aria-details" and `role="comment"` for comments, reactions, etc.
[tantek]except what's the consuming use-case? in particular, what mf2 does is identify the different *parts* of a comment (content, author, published) which is the more interesting part because that's what consuming code needs to make sense of a comment.
Seirdyrole=comment isn't actually doing much on its own, it only exists to describe the relationship declared by aria-details as a "comment" since aria-details is pretty generic
Seirdyessentially, it's the first step towards moving from "what things are" to "how things relate to each other" beyond the standard parent/child relationships.
Seirdyso you can use "labelledby" for a short text label, "describedby" for a longer text alternate, and "details" for rich markup. but this begs the question "what is the relationship between the rich markup and the described content".
@erikkroes↩️ I am actually adding some non-semantic HTML (it's all semantic right now!) with the goal of... adding more semantics. Not sure how I can fit in microformats otherwise. (twitter.com/_/status/1524998289229324290)
@KevinBankston↩️ You don't think that has to do with the fact that it is a blogging rather than microblogging platform? Bot-tweeting is a lot easier than bot-blogging... (Or are you arguing that intentionally designed platforms should avoid microformats?) (twitter.com/_/status/1525168779558125569)