This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] Sent: Monday, July 22, 2013 6:13 PM To: public-html-admin@w3.org Cc: Robin Berjon; Michael[tm] Smith Subject: WG Decision to remove Microdata from HTML 5.0, remove JS API, continue HTML Microdata as a separate spec No one objected to the CfC to remove Microdata from HTML 5.0, remove JS API, and to continue HTML Microdata as a separate spec by the Wed Jul 17 deadline. http://lists.w3.org/Archives/Public/public-html-admin/2013Jul/0019.html Therefore, the HTML Working Group hereby resolves to handle the Microdata discussion as specified in the above referenced CfC. The Editors are requested to carry out the directions of the CfC: a) to remove all references to Microdata from the HTML 5.0 CR draft, b) to remove the Javascript API from the Microdata spec, and c) to publish the separate "HTML Microdata" document as an extension spec (iff editorial resources can be found). /paulc HTML WG co-chair Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596 Fax: (425) 936-7329
I've combed through the current CR Draft spec of HTML5.0. The bulk of the Microdata definitions, etc., seem to already be removed, but I did find these vestiges: (1) HTMLDataElement * Mentions microdata in conjunction with microformats (giving it equal footing) in relation to the value attribute of that element. This seems fine to leave in. (2) HTMLTimeElement.dateTime (code example) * Provides a code example using microdata. However, this code example is paired with 4-5 other code examples illustrating how the datatime attribute is used for the <time> element in a variety of formats such as microformats (ex. 1), schema.org microdata (ex. 3), ISO8601 (ex. 4), and some other normal date and timezone+date examples (5 & 6). I think it's OK to leave these references to microdata in the spec within the context of exploratory examples of this sort. (3) HTMLMeterElement * A one-liner about how to interpret meter's value in the context of Microdata. This is a good candidate to remove as it is specific to microdata. (4) Drag-drop processing model * Step 6, puts some Microdata into the clipboard if the dragged nodes contain microdata. This entire step can be dropped to avoid the microdata reference without compromising the integrity of the algorithm. (5) Acknowledgements * A special thanks callout to folks of the Microdata usability study for helping guide the design of Microdata. While it feels a little cold to strip this out, leaving it in could lead someone to reason that there should be a feature called Microdata in this spec, which there will not be. Therefore, I think this should be removed as well. So to re-cap, my plan is to remove occurrences 3-5 above from HTML5.0 CR, and I think that will satisfy the Chair's CfC above.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: Removed occurances of microdata as previously outlined Commit details: https://github.com/w3c/html/commit/9ae7583d28ef1e0e6042943f7fafd98113bbb4f0