Can you do me a favour and replace the copyright symbol with a (c) symbol? My pipeline isn't UTF-8 safe yet and so I have some early filtering in place that drops everything if it detects a high bit set. (Hopefully my upcoming changes will fix this, but I'm not there yet.)

BTW, please take a look at the bugs with <img> in their summary, and take any of them that you're planning on working on. I'll move the others to a far future milestone for now, at which point we can see how much the ongoing <picture> maintenance cost is and figure out next steps.

http://html5.org/tools/web-apps-tracker?from=8611&to=8612

Still need to remove the "Adaptive images" section.

Fixed (c).

I've taken the bugs that affect the integration. The other bugs are lower priority for me, but I can take them later also.

Should we create a new bugzilla component for <img> and have the spec's bug filer pick that for bugs in that section?

I've commented out the Adaptive images section. I'd love to see that exact section unchanged but with the examples switched to the new syntax, though.

zcorpan, are you planning on resurrecting that section in the new world?

https://github.com/ResponsiveImagesCG/picture-element/commit/be59932c68600fed2ef9ca0ccd0565d28896ce4f

Is that really what authors prefer?! Those are examples are all ten times more verbose and have dozens more possible ways of making mistakes.

The last three examples in this section all address one of the criticisms originally levied against old-srcset: that by short-handing media queries – reducing them to a number and a signifier which effectively resolve to something like a max-width or max-height query – old-srcset prevented the min-width-based, “mobile-first” pattern many authors had adopted in their CSS media queries. [1]

The section, as originally written, shows that that criticism is baseless. Old-srcset can be used with that pattern.

But frankly, the new syntax, by simply *just using media queries* which authors are already familiar with, is *so* much simpler from an education standpoint that this section doesn't merit inclusion anymore. Because we're just using media queries, *of course* we can adopt either desktop-first or mobile-first patterns. *Of course* we can use either min-widths or max-widths. 

And we can do these things using the sort of code we’re already writing in our CSS... *without* having to put our minimum queries on a different source (!); *without* having to remember that by assigning a density descriptor without w/h the image is treated as suitable for a viewport of infinite dimensions (!).

Full media queries, unlike old-srcset, are obvious.

Old-srcset was terser and provided tighter constraints on what authors could and couldn't do. But it presented a much steeper learning curve. So of course authors prefer `picture`.

[1] http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-May/290211.html