Re: Editorial patches staged for merge week 49

Hi Steve,

On Fri, Dec 7, 2012 at 6:26 PM, Steve Faulkner <faulkner.steve@gmail.com>wrote:

> Hi Silvia,
>
> this patch
> https://github.com/w3c/html/commit/ce89d21a56ae0b682e9bd5cf9d6ddd4397290594
>
> With regards to the validator contains advice that is contrary to WG
> agreed advice in regards to title attribute usage.
>

Which parts of the patch do you think are contradictory? Is it the full
patch? Could you register a bug?



> Also the addition of the markup generator attribute to flag images (I
> think) should be an extension not added directly to spec.
>

So, wrt extension specs: the way I understand them is that they are for the
HTML5 spec: they specify features that somebody hopes to still get into
HTML5, rather than HTML5.1 [1].  If this is your intention - that it should
get implemented for HTML5 - then you should indeed write an extension spec.
If instead you regard it as a feature at risk in HTML5.1 or one that you
object to, then IIUC you should register a bug on HTML5.1. Basically,
HTML5.1 will have a number of features in it that are proposals and not yet
implemented. The extension spec approach for HTML5.1 would in my
understanding take effect when HTML5.1 goes into CR and features that do
not have sufficient implementation will get pulled out.

Note that I have not checked my interpretation with the chairs, so I may be
off. I guess we need clarification on what to do wrt extensin
specifications and HTML5.1.

Best Regards,
Silvia.

[1] http://dev.w3.org/html5/decision-policy/html5-2014-plan.html


> regards
> Steve
>
>
> On 28 November 2012 16:06, Silvia Pfeiffer <silviapfeiffer1@gmail.com>wrote:
>
>> Hi all,
>>
>> My weekly merger announcements are now two-fold:
>>
>> 1. For HTML5.0 CR
>> 2. For HTML5.1 WD only
>>
>> For HTML5.0 CR there are only editorial patches and they are staged in
>> the branch:
>> https://github.com/w3c/html/commits/editorial_fixes
>>
>> For HTML5.1 WD I will be reporting on what WHATWG patch we have reached.
>> Those are directly applied to master unless they are controversial new
>> features that require a extension spec, in which case they end up in new
>> branches.
>>
>> Let's do it!
>>
>> ===
>>
>> 1. Staged for HTML5.0 CR
>> ------------------------------------
>>
>> You can find the new patches staged for HTML5.0 CR at:
>> https://github.com/w3c/html/commits/editorial_fixes
>> (patches for 28th November)
>>
>> It includes a fix for the following bug.
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17465
>>
>> It includes addition of an example for the MicroData spec to close the
>> following bug:
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=18142
>>
>>
>>
>> 2. Merged into master for HTML5.1 FPWD
>> --------------------------------------------------------
>>
>> I merged WHATWG patch up to and inc commit 7529 [1], which takes us to
>> 23rd November 2012.
>>
>> You can see the committed patches here:
>> https://github.com/w3c/html/commits/master
>> (patches for 28th Nov)
>>
>> If you see any patches there that should also be applied to HTML5.0 CR,
>> please register a bug.
>> (e.g. the patch for https://www.w3.org/Bugs/Public/show_bug.cgi?id=19560)
>>
>>
>> The following bugs have been closed:
>>
>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17465
>>
>>
>> Branches held back for extension specifications:
>>
>> * feature/whatwg_srcset:
>> https://github.com/w3c/html/compare/master...feature;whatwg_srcset
>>
>> * feature/whatwg_canvas_workers:
>> https://github.com/w3c/html/compare/master...feature;whatwg_canvas_workers
>>
>>
>> Best Regards,
>> Silvia.
>>
>>
>> [1] http://html5.org/tools/web-apps-tracker?from=7528&to=7529
>>
>>
>
> <http://www.paciellogroup.com/resources/wat-ie-about.html>
>