2 KiB
| title | date | replyURI | replyTitle | replyAuthor | replyAuthorType | replyAuthorURI |
|---|---|---|---|---|---|---|
| WAI-Adapt fallbacks to equivalent microformats | 2022-09-13T11:28:15-07:00 | https://github.com/w3c/adapt/wiki/Comparison-of-ways-to-use-vocabulary-in-content | Comparison of ways to use vocabulary in content | WAI-Adapt Task Force | Organization | https://www.w3.org/WAI/APA/task-forces/adapt/ |
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 live h-card implementations on the IndieWeb Webring directory.
w3c/coga Issue 69 also references overlap between "destination" vocabulary and rel values. Microformats leverage rel attributes like rel="license" and rel="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.
Syndicated to the GitHub w3c/adapt bug tracker and indieweb.xyz/en/accessibility.