I replied to the following: ↷

If we go with the third option, I'd be slightly pressing the suggestion to parsers to allow for an option to restrict any of the `h-` values to be ones that can represent known values, namely those with defined specifications

This could be an evolving list, which is already done with Micropub extensions and new specifications of objects themselves. This also could break backcompat with those parsers that fallback to being a h-entry or the like, but I see that as very unlikely.

Posted with Quill at in Everything

Shared to GitHub

Engagement is powered by Webmentions — a premier standard of the Web to let other sites know you've mentioned them. Learn how to reply from your own site. or from a supported silo Aaron has an interactive post about this. If you've mentioned this URL via another one, use the form below to submit it.

If you don't currently own your replies, then you can click below to do so.

I currently aim to own my comments and plan to eventually show those I've received once I finish Lighthouse.