Replied to Process for updating a proposed h-entry property · Issue #25 · microformats/h-entry by Tantek Çelik (GitHub)

The current h-entry change control process does not specify how to update the definition of a proposed feature, which means it falls back to being as strict as updating a stable feature which is more strict that desired for proposals. This issue is for considering a proposal for updating the definition of a proposed feature, as discussed during the recent Microformats Issue Resolution pop-up.

Proposal: the definition of a proposed feature may be updated to be more consistent with one or more real world public web sites publishing and or consuming the feature, by citing URLs for those examples in an edit summary. New proposed property or value definitions may also be added for consideration per the existing requirements for adding a proposed feature. If you’re not sure whether to update an existing definition or add a new definition, try to work with the proposer(s) of an existing definition to come to a consensus to update it. Lacking consensus, add a new definition for consideration, retaining any previous definition(s).

This proposal also adds a convergence requirement for moving a feature from proposed to draft. If there are multiple definitions for a proposed feature, an issue must be opened to discuss how to converge the definitions by consensus agreement among those with real world public web sites publishing and or implementations consuming the feature.

This is a rough first draft, feel free to propose alternatives, simplifications, editorial suggestions.

(Originally published at: https://tantek.com/2020/259/b2/)

This is acceptable to me. No further ideas or revisions at this time.