RE: Next steps for Microdata

>2) Remove Microdata API from the Microdata and HTML specifications, and advance that document to CR.

I believe another option was discussed as well:

2a) Mark Microdata API as being a Feature At Risk and advance Microdata to CR.

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: Sam Ruby [mailto:rubys@intertwingly.net] 
Sent: Wednesday, April 24, 2013 7:17 AM
To: public-html-admin@w3.org
Subject: Next steps for Microdata

This was a topic of discussion at the F2F[1]

Summary: during a CR advancement call with the Director, we noticed a merge failure.  While that was corrected, Blink chose to remove Microdata API.  Oprah is EOL'ing Presto.  We have other signs of lack of industry momentum for Microdata.

Four ways forward were discussed:

1) Remove references to Microdata from the HTML specification, and publish Microdata as a note.

2) Remove Microdata API from the Microdata and HTML specifications, and advance that document to CR.

3) Fold Microdata into HTML 5.1, remove from 5.0, and revisit periodically during the development of 5.1.

4) Remove Microdata API and fold into HTML 5.0.

My sense of the sentiment in the room at the time of the discussion was that there was considerable support for option 3, and there were various levels of objections to options 1, 2, and 4.  While some clearly preferred other options, everybody could live with option 3.

The purpose of this note is twofold:

1) Solicit other options that those in the room might have missed.

2) Solicit additional objections to any of these options, in particular the third alternative.

- Sam Ruby

[1] http://www.w3.org/2013/04/23-html-wg-minutes.html#item04

Received on Wednesday, 24 April 2013 20:03:54 UTC