[Bug 13101] TAG issue on HTML+RDFa and Microdata last call drafts

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13101

--- Comment #4 from Manu Sporny <msporny@digitalbazaar.com> 2011-07-05 19:51:26 UTC ---
(In reply to comment #3)
> That is a risky assumption given that the Last Call ends on Aug 4 which 
> is less than one month away and the TF has not yet been created.

>From my understanding, the HTML WG's Last Call timeline doesn't matter if both
the RDFa and Microdata specs in HTML5 are blocked indefinitely from publication
as RECs until the Task Force decides a reasonable path forward. We will exit
HTML WG Last Call with documents that will, at worst, be blocked from going to
REC or at best, will have architectural issues logged against them during
Candidate REC. What am I missing?

> I encourage you to provide specific more actionable changes that can be made as
> Last Call comments ASAP.

I could do that, but I'm concerned that it would be perceived as an attack
against the Microdata group. I'm currently in the middle of trying to pull each
of these groups together to try and figure out if there is a reasonable
compromise that can be worked out. I can't be effective at doing that and
logging "bugs" against the Microdata spec.

I have clearly outlined the differences between Microdata, RDFa and
Microformats here:

http://manu.sporny.org/2011/uber-comparison-rdfa-md-uf/

I have a hard time calling these things "bugs" as they are really just use
cases that are and are not supported by each mechanism. There are a few things
that qualify as bugs, but the rest are design decisions based on a subset of
use cases that each group decided to address.

The real bug is that the HTML WG is pushing two solutions forward that do
effectively the same thing (from the perception of the majority of Web
developers). This is confusing people, in that they don't know which one to
pick. It is creating a situation where the early adopters are screwed when a
search company like Google picks a winner, and where the rest of the folks that
just want a single solution are waiting for the dust to settle before
implementing. It's confusing the market and slowing adoption.

I say this knowing that I was one of the people advocating that the W3C publish
two solutions to the same problem. Advocating this position was a mistake, in
hindsight.

I will personally, (not on behalf of the RDF Web Apps WG) log bugs against
Microdata if one of two things happen:

1) The Chairs of the HTML WG request that all design issues and bugs known to
me are logged against Microdata.
2) Ian, Henri and the rest of the WHATWG folks ask me to log all design issues
and bugs that have been identified over the past two years on Microdata into
the HTML WG issue tracker.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 5 July 2011 19:51:30 UTC