{"id":363,"date":"2012-10-13T21:05:15","date_gmt":"2012-10-13T21:05:15","guid":{"rendered":"http:\/\/www.w3.org\/community\/respimg\/?p=363"},"modified":"2012-12-07T15:34:59","modified_gmt":"2012-12-07T15:34:59","slug":"the-state-of-the-picture-specification","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/respimg\/2012\/10\/13\/the-state-of-the-picture-specification\/","title":{"rendered":"The State of the Picture Specification"},"content":{"rendered":"

First, a little housekeeping: while the community group is site is great for ongoing discussion, it doesn\u2019t offer anything in the way of tracking specific goals and issues. Up to this point we\u2019ve been using a GitHub repo<\/a> on my account.<\/p>\n

It\u2019s working great for us so far<\/a>, if I may say so, and it feels good to be working on familiar turf \u2014 but it\u2019s still tied to my admittedly nonsensical nickname. This is an effort led by the developer community, and it should be reflected as such.<\/p>\n

I\u2019m pleased to announce that the RICG now has a formal home on GitHub<\/a>. We\u2019ll be tracking issues and publishing drafts through this organization and its repos, while the CG site and mailing list will continue to be used for broader conversation. I hope to see you all there!<\/p>\n

We\u2019ve put out a call on the mailing list for anyone willing to contribute an hour or two per week to helping us triage issues and review changes \u2014 let us know if you\u2019re willing to pitch in!<\/p>\n

The Extension Specification<\/strong><\/p>\n

Politics aren\u2019t my strong suit, so the current state of our proposal is a weight off my shoulders.<\/p>\n

Both our proposal and the srcset<\/code> proposal are being handled as \u201cextension specifications,\u201d and they\u2019re currently being developed independent of the overall HTML spec. We\u2019re actively working with proponents of the srcset<\/code> extension specification to ensure that the two complement each other, and both our extension spec and use case documentation<\/a> reflects that.<\/p>\n

No single decision maker or group has the final word in this, as Marcos explained on the mailing list<\/a> earlier today. When and if it leads to functional native implementations, it will be merged into a snapshot of the HTML spec.<\/p>\n

The picture<\/code> specification, though still in progress, is eligible for real-world implementations as we speak. We\u2019re continuing to reach out to browser representatives to collaborate on the proposal and discussing where the picture<\/code> element would fit on their development roadmaps. I\u2019m calling on all of you to do the same. In the end, demand is the deciding factor when it comes to new features \u2014 there\u2019s no shortage of demand for picture<\/code>; we\u2019re proof of that. Let\u2019s make sure the browsers vendors hear from us.<\/p>\n

A Native Implementation<\/strong><\/p>\n

We\u2019ve reached the point in hammering out the extension specification where we\u2019re focusing on more specific issues we\u2019d be likely to run into in a native implementation.<\/p>\n

It\u2019s difficult \u2014 if not impossible \u2014 to hash out the potential issues with a real-world implementation in a vacuum. As a result, Yoav Weiss has begun prototyping a native picture<\/code> element in a fork of Chromium<\/a>. We\u2019re addressing the questions that arise as a result in the issue tracker for the extension specification.<\/p>\n

I know, for my part, it was exciting to finally see that picture<\/code>\u2019s source<\/code> pattern can and will work with Chrome\u2019s image prefetching with my own eyes. It\u2019s one thing to talk about it on a mailing list\u2014it\u2019s another to see it working.<\/p>\n

Twitter Account<\/strong><\/p>\n

As my Twitter followers know all too well: I am largely unbearable. For the sake of anyone that wants to keep tabs on ongoing developments without being subjected to dog photos and complaints about the Boston subway system, we\u2019ve started up an RICG Twitter account: @respimg<\/a>.<\/p>\n

Thanks<\/strong><\/p>\n

I want to personally thank Marcos Caceres<\/a>. Marcos has been putting a tremendous amount of time and effort into the extension specification, and into organizing the efforts of the RICG.<\/p>\n

I also want to thank all of you, once again. We\u2019re not only making steady progress on a long overdue solution to a very real problem, but we\u2019re bringing about changes to the way the web is built. Our community group is being held up as a shining example of how developers can get directly involved in web standards, and we\u2019re working with members of the W3C to find ways of smoothing out the rough edges on the process we\u2019ve carved out. It hasn\u2019t been especially easy or chaos-free, but we\u2019re making things that much easier for the next group of developers that comes along with a good idea. <\/p>\n

Blue Beanie Day<\/a> is coming up. When you put one on, know that you\u2019re not just supporting<\/i> web standards \u2014 you\u2019re taking an active role in moving standards, and the web itself, forward.<\/p>\n","protected":false},"excerpt":{"rendered":"

First, a little housekeeping: while the community group is site is great for ongoing discussion, it doesn\u2019t offer anything in the way of tracking specific goals and issues. Up to this point we\u2019ve been using a GitHub repo on my … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1272,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[1],"tags":[],"class_list":["post-363","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/posts\/363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/users\/1272"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/comments?post=363"}],"version-history":[{"count":15,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/posts\/363\/revisions"}],"predecessor-version":[{"id":397,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/posts\/363\/revisions\/397"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/media?parent=363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/categories?post=363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/respimg\/wp-json\/wp\/v2\/tags?post=363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}