2022/Pop-ups/Microformats

⚠️ This pop-up was originally scheduled for 2021-07-31 but eventually cancelled for procedural reasons (chat logs). Eventually this page was moved to 2022 but no consensus on a date was reached. Please visit pop-up#Microformats_Roundtable to express your interest and date preference if you're interested in making this pop-up happen!

2022 Microformats Roundtable was a proposed IndieWebCamp Pop-up 2022 session.

Details

• facilitators: Barnaby Walters
• Date: See 2022/Pop-ups/Sessions#Microformats_Roundtable for possible dates and add which dates work (or don't) for you!
• Time: 11:00 Pacific
• event: TBD once there’s a clear critical mass on the dates poll
• hashtag: #microformats2022
• https://etherpad.indieweb.org/Microformats-Popup

Agenda

Let's discuss how we can close out some outstanding microformats2 questions. Below are items we didn't get to last time.

• https://github.com/microformats/microformats2-parsing/issues/
• https://github.com/microformats/h-card/issues
• https://github.com/microformats/h-entry/issues
• https://github.com/microformats/h-feed/issues
• https://github.com/microformats/h-event/issues

microformats2 features are advanced by a 3 step process: Proposed, Draft, and Stable.

• Proposed features must provide documentation of what specific real world use-cases they are solving, preferably with a link to a step-by-step user scenario.
• Draft properties must in addition be published and consumed in the wild on the public web, demonstrate solving the use case for which they were proposed, and should provide citations of real world public web sites publishing and (other sites) consuming them, interoperably.
• Stable properties must in addition be published and consumed in the wild on multiple sites by multiple implementations (3+ different sites and implementations for publishing and consuming). When a draft property reaches a critical mass of deployment by numerous sites and implementations (far beyond 3+), due to network effects and backward compatibility considerations it effectively becomes stable, since it becomes increasingly difficult to change it in any way and have so many sites and implementations also change.

Parsing

Most-discussed issues carried over from mf2 parsing issues, add your -1/0/+1 votes and/or add additional issues you’d like to bring attention to.

• #15 Specifying a mime-type for parsed mf2 json - Has there been movement since the last event?
• #15 What should mf2 textContent parsing result in? User expectation vs. DOM specification.
  • Barnaby Walters +1 this keeps on coming up, definitely something to discuss
  • +1 Tantek Çelik
• #9 "return the normalized absolute URL" for invalid URLs?
• #7 Should u-* parsing special case img srcset?
• #4 vcp: imply dates should also imply tz if needed
• #24 Parsing <noscript> tags
  • Barnaby Walters +1 seems like the discussion around this reached a consensus, would be good to confirm and resolve if possible
• #3 Parse language information
• #8 imply dates also outside vcp?
• #38 resolve relative URLs in e-* html
  • Barnaby Walters +1 I consider this vital for consumers to be able to work with parsed e-* properties
  • +1 Tantek Çelik this sounds both hard and essential
• #32 Clarify attribute properties added to objects in rel-urls.

h-card

(stub section)

• https://github.com/microformats/h-card/issues

(please propose specific issues to discuss)

h-entry

• Properties waiting to move to Core
  • u-photo https://github.com/microformats/h-entry/issues/4 - Discussed at previous popup, but tabled till #24 was addressed
    • Update definition https://github.com/microformats/h-entry/issues/24
  • u-video https://github.com/microformats/h-entry/issues/5
  • u-comment https://github.com/microformats/h-entry/issues/20

• Properties Waiting to Move to Draft
  • u-audio https://github.com/microformats/h-entry/issues/6
    • huffduffer.com is an example
  • u-bookmark-of https://github.com/microformats/h-entry/issues/12
  • u-featured https://github.com/microformats/h-entry/issues/14
  • u-checkin https://github.com/microformats/h-entry/issues/15

• Proposed Properties
  • u-listen-of https://github.com/microformats/h-entry/issues/11
  • u-read-of https://github.com/microformats/h-entry/issues/10
  • u-watch-of https://github.com/microformats/h-entry/issues/17
  • Status https://github.com/microformats/h-entry/issues/18 - Idea to use TODO elements from iCal
    • needs-action
    • completed
    • in-process
    • cancelled

h-feed

• Do Not Restrict H-Feed to contain only H-Entry https://github.com/microformats/h-entry/issues/16
• Rules for Implied H-Feed https://github.com/microformats/h-feed/issues/1 - Also comes up as a parsing question https://github.com/microformats/microformats2-parsing/issues/47

h-event

• Advance H-Event to Microformats Specification https://github.com/microformats/h-event/issues/2
• Event Description should be replaced with Content Property https://github.com/microformats/h-event/issues/3
• Format for Duration Should Be Specified https://github.com/microformats/h-event/issues/5
• Adopt iCal Status for Events - https://github.com/microformats/h-event/issues/6
  • tentative
  • confirmed
  • cancelled20