Open Seirdy opened 2 years ago
Hi @Seirdy. Thank you for your feedback and suggestions. I have am looking into this for the group, and we plan to discuss it soon. We'll post an update on this thread when we've discussed it.
We discussed microformats on our call today (draft minutes). We have some concerns about accessibility, and will look into those, but we will be adding microformats to the wiki page, in order to ensure we have a thorough comparison. I'll be working on this soon.
@matatk Regarding the accessibility considerations: I believe these have been solved by HTML5 elements such as data
and time
.
I noticed that the Comparison of ways to use vocabulary in content page on the personalization-semantics wiki didn't mention Microformats. Microformats add semantic meaning to individual HTML elements; this is in contrast to document-level semantic formats like Microdata, RDFa, and JSON-LD.
There's a 1-1 mapping between many microformats and values in the WAI-Adapt Content Module. Several values under section 4.3.4 (values for "purpose") are already specified in
h-card
microformats2, for instance. You can find plenty of liveh-card
implementations on the IndieWeb Webring directory.w3c/coga Issue 69 also references overlap between "destination" vocabulary and
rel
values. Microformats leveragerel
attributes likerel="license"
andrel="home"
; these seem equivalent to the "terms" and "home" values for destination attributes.I propose the addition of microformats2 to the comparison wiki page, and would support either merging the content module with microformats or specifying a mapping for fallback.
POSSE note from https://seirdy.one/notes/2022/09/13/wai-adapt-fallbacks-to-equivalent-microformats/