Relevant developments

Hi,

== Adaptive Images ==
The discussion on adaptive images is probably relevant to this group -  
especially in the context of content that can adapt to a wide range of  
screen sizes and resolutions.

The idea is making it easy for a different image file to be used according  
to differing presentation. Alternatives include a microsyntax based on  
width and height of the image, or being able to use general media queries.

There is a discussion in the HTML Working Group -  
http://lists.w3.org/Archives/Public/public-html/2012Aug/0427.html and  
http://lists.w3.org/Archives/Public/public-html/2012Sep/thread.html#msg3  
are starting points in the archive.

I noted the use case for signage in a parallel discussion in the WHAT-WG  
community group, which I also cc'ed to Hatano-san. Unfortunately the  
WHATWG don't have good mail archives.

== Appcache, and other offline capabilities ==
The coremob community group (focused on mobile devices and making  
applications for them) have been pushing to work on something to fix or  
replace appcache for offline apps, since it is not considered usable by  
many people.

The Web APplications working group has a proposal for application  
packaging that mostly repeats the functionality of W3C Widgets, but uses  
JSON for packaging. Both Chrome and Mozilla have gone down this path. The  
proposal on the table comes from Mozilla. I believe that in Asia it is  
more common to use the Widgets standards - but I would like to know more  
about what is available in implementations.

== SMIL ==
There is currently no suggestion of working on SMIL, but at the workshop I  
heard some desire for doing this.

The simple timing module of SMIL is probably not difficult to prototype in  
Javascript, and it might therefore be possible to refactor it into HTML5.  
This depends in part on what parts of SMIL are considered critical, since  
I doubt that the entire SMIL specification would be adopted. But along  
these lines...

== Plan 2014 ==
(No, as far as I know W3C is not going to adopt CEA-2014...)
This is a proposal from the HTML working group to finish HTML5 on time,  
and start developing the next generation of HTML. The idea is to create  
extension specifications which describe additions to (or potentially  
things to remove from) the HTML5 specification. A very simple example is  
at  
<http://lists.w3.org/Archives/Public/public-html-a11y/2012Sep/att-0478/longdesc.html>  
The process suggestion is experimental. That example specification is  
based on a mature discussion and implementation, and it is short. It took  
me about 2 hours to create this morning, and I expect to spend another few  
hours on specification work, and I happen to have test cases already. All  
that is missing is consensus on the specification.

But this approach is something that might be interesting to members of  
this group, giving them a simpler way to develop extensions specifications  
for HTML.

cheers

Chaals

--
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com

Received on Monday, 24 September 2012 15:38:42 UTC