Re: The next HTML+RDFa Heartbeat

"Manu Sporny" <msporny@digitalbazaar.com> wrote:

> The only reason we are decoupling HTML+RDFa LC from HTML5 LC is in
> the
> case that there is some significant last-minute change to HTML5 that
> requires the RDFa WG to go back and rework HTML+RDFa.

You seem to writing as though the RDFa WG were developing HTML+RDFa if it's the WG to potentially "rework" it.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=7670#c43 says "So, any changes made to RDFa Core 1.1 will be applied to HTML+RDFa.", which seems to mean that HTML+RDFa is so constrained by the output of the RDFa WG that there isn't anything for the HTML WG to do except to rubber-stamp it. (After all, bug 7670 is about one of the central concerns raised about RDFa in the HTML WG.)

What's the point of making HTML+RDFa nominally a deliverable of the HTML WG or making SVG+RDFa nominally a deliverable of the SVG WG if RDFa Core is fully(?) constraining what these specs can say? Why aren't HTML+RDFa and SVG+RDFa direct deliverables of the RDFa WG if the RDFa WG is de facto defining the normative constraints on the specs?

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/