adopt same change control as h-entry

[tantek]

@aaronpk proposed that h-event adopt the same explicit change control as h-entry as summarized at the top of http://microformats.org/wiki/h-entry and described in detail at http://microformats.org/wiki/h-entry#change_control. So as a self-contained experiment, let's discuss that as we would if such change control were already on h-event.

Please thumbs up/down and/or comment accordingly.

I think one possibly dependent thing to address is the state of h-event as a whole (Microformats Draft Specification) vs h-entry (Microformats Specification) and will file that as a separate issue.

[tantek]

This update is now required (prerequisite) for tantek/post-type-discovery#26, which to normatively reference h-event, requires similar explicit change control as h-entry.

[kevinmarks]

👍

[dshanske]

Propose that we, instead of duplicating change control from h-entry...we extract h-entry's change control from the h-event specification and agree it will be cited/adopted by all h- properties at the time those items move from draft to stable, starting with h-event.