Search results

Jump to navigation Jump to search
  • == when using both h-card and vcard which should be first and why == Another example: should "h-event" be first (before the "vevent") in the class attribute?
    10 KB (1,569 words) - 21:32, 26 July 2023
  • * Actual hostility towards using names/terms from other standards === human nature ===
    12 KB (1,783 words) - 16:30, 18 July 2020
  • ...longside/with an [[adr]], and/or as part of an [[hcard|hCard]]. See also [[hcard-brainstorming]]. ...ttps://twitter.com/jkprime/status/233778329340223488 Tweet permalink] with hyperlinked embedded map view and city/state/country.
    17 KB (2,558 words) - 16:22, 18 July 2020
  • * https://github.com/microformats/microformats2-parsing/issues ...e consuming application wants to display that u-* property as an img, they have to either omit or synthesize a fake text alternative.
    42 KB (6,235 words) - 16:29, 18 July 2020
  • ...ns"), then do so, but always redirect them to [[IRC]] for discussion. E.g. here's an email template you may use: Hi,
    31 KB (4,800 words) - 16:23, 20 October 2021
  • {{DISPLAYTITLE: namespaces considered harmful }} In particular namespaces for '''content''' are considered harmful (e.g. XML namespaces, QNames in attributes etc.). Namespaces for cod
    13 KB (1,918 words) - 16:30, 18 July 2020
  • == How To == ...recent updates you post there. For your individual permalink pages, use [[h-entry]].
    34 KB (5,453 words) - 05:18, 9 October 2023
  • {{DISPLAYTITLE: hAtom issues }} ...issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some
    30 KB (4,760 words) - 16:23, 18 July 2020
  • To focus the discussion, please add use cases below that will help show what problems the citation microformat will be solving. Use cases for both publishing and consuming citation information can help to focus citation brainstorming on efforts that provide real world utili
    44 KB (6,231 words) - 21:11, 26 July 2023
  • Use the [[HTML5]] time element for all use-cases that the Datetime Design Pattern was c The abbr use for datetimes in particular has been dropped due to [[#accessibility_issues | accessibility issues]].
    42 KB (6,379 words) - 16:21, 18 July 2020
  • This page collects ideas on how to use semantic XHTML to represent unambiguously [[measure]]s. == HTML proposals ==
    56 KB (8,114 words) - 21:06, 26 July 2023
  • This document will help guide you through the steps to take towards achieving these goals. The microformats process has been cited as inspiration for other standards groups and efforts such as
    29 KB (4,410 words) - 19:10, 29 November 2022
  • Ceci est une page pour explorer un pattern de design pour la date et l'heure. ...ttern]] pour faire que les dates et heures puissent être lisibles pour des humains et aussi lisibles formellement par des machines.
    42 KB (6,350 words) - 16:21, 18 July 2020
  • {{DISPLAYTITLE:hCalendar 1.0}} {{latest|h-event}}
    20 KB (2,906 words) - 16:24, 18 July 2020
  • {{DISPLAYTITLE:hCalendar resolved issues}} [[hCalendar]] <span id="Resolved_Issues">issues that are resolved but may have outstanding [[to-do]] items.</span>
    41 KB (6,454 words) - 16:24, 18 July 2020
  • ...[[h-card]] which supersedes hCard and add to [[h-card#Examples_in_the_wild|h-card examples in the wild]] accordingly. Thank you.</p>}} {{DISPLAYTITLE:hCard Examples in the wild}}
    135 KB (20,460 words) - 16:25, 18 July 2020