Posts tagged "w3c"

HTML5 Gets Glitzy New Logo, Bids Adieu to Flash

The W3C has unveiled a new logo for HTML5, a "striking visual identity for the open web platform." But really, what's more important here, a glitzy new logo or the potential end of Flash?


What's the Purpose of the New HTML5 Logo?

Like any other logo, the HTML5 logo has the purpose to spread the word (or the image, if we are more precise) and to build brand awareness.

Contrary to what you might expect however, this logo isn't an official W3C logo yet — it is just a pilot project to popularize HTML5, although it is expected that within the first quarter of 2011, W3C will adopt an official logo, which could possibly be exactly the piece you are looking at now.

The logo hasn't been designed as a symbol of proof that a site is HTML5 compliant. In fact, if the logo is used on any page, it doesn't mean that the site complies with the requirements of W3C but that, simply, the site designer sympathizes with HTML5.

How Can I Use the New HTML5 Logo?

Designers will appreciate the new logo and will, no doubt, find millions of creative ways to incorporate it in their designs. If you don't think orange is your color, you can modify or download an alternative black and white version. The logo is designed under a Creative Commons Attribution 3.0 Unported license — providing people with lot of freedom to modify it. Just remember to credit the original authors.

What's New in HTML5 Besides the Logo?

The new HTML5 logo is exciting but it certainly isn't the only news surrounding HTML5. For instance, the canvas element moved a step further with the recently updated draft of the HTML Canvas 2D Context specification. Considered a Flash-killer, only the future will show if Flash will be kicked to the curb or not. 

The canvas element looks very promising because it allows not only to draw basic shapes but also to apply more advanced techniques. It has attributes for colors and styles, shadows, complex shapes, focuses, etc. You can also use it to manipulate text and separate pixels. It is not as powerful as Flash but it has enough power to replace Flash in many of its uses.

However, the way browsers render images and use hardware acceleration could seriously affect the practical application of the canvas element. The element might have enough horse power but when browsers misinterpret it, it can lead to slow operations. Maybe it is too early to say that we are heading in the direction of the Flash-less Web.

W3C Solution For Robust Web Application Caching Progresses


The Web's days of innocence, where it was just used to post the digital equivalent of static brochures, are long past. Today we expect to do everything over the web, no matter how forced and cludgy it has to work under the hood to accomplish our goals. Fortunately there are people willing to wade into the mind-numbing realm of protocols and data streams in order to improve it all.

Taking Care of Data in Offline Web Apps

As web applications grow in sophistication, they're escaping the boundaries of constraints such as the web browser and the need to be constantly connected. The problem is that web standards such as HTML weren't developed for many of the use cases that are common with today's web applications.

Right now, everyone working on such applications has to develop their own solution. As work continues on the update toward HTML 5, parallel work is also in play to create standard protocols and APIs to prevent this constant reinvention of the wheel and faster innovation and easier interoperability.

One of the areas where, for the moment, people are having to hack solutions together is that of how to queue or cache data for a web application that has gone offline. HTML 5 offers a way to create application caches, but due to their static nature this option can only be used with safe HTTP methods. The Programmable HTTP Caching and Serving API is under development by the Web Applications Working Group to address this problem.

A Solution That Extends HTML 5's App Cache

This API extends HTML 5's application cache by:

  • Allowing applications to add resources to the cache, which can then be served by the user agent when the resource is requested.
  • Enabling applications to generate responses to requests for resources that were added to the cache.

These extensions allow use of the HTML 5 cache with unsafe HTTP methods like PUT and POST. As an example, the working draft offers,

"Using this application cache extension, applications can obtain locally cached data or data produced locally by JavaScript servers and perform requests on resources that can be served whether or not the user agent is connected to a remote server. Applications can then save and replay locally satisfied requests to the server when it is reconnected, thus enabling responsive and robust Web applications in the presence of low connectivity conditions."

Essentially, this extension allows web applications to seamlessly switch between online and offline work, causing far less hair loss as users will be less likely to lose their work due to a connection outage.

Those who want the absolute bleeding edge can check out the W3C Editor's Draft version of the API here.

Leadership Change: Jeffrey Jaffe Takes the Helm at W3C

There's a change of the guard at the W3C (site) this month. Jeffrey Jaffe has been named as the new Chief Executive Officer. His extensive business and technical experience make him the perfect match to support the W3C's role as the leading forum for the technical development of the Web.

 An Background in Enterprise Solutions

Jaffe has a pretty impressive background:

  • Executive Vice President, products, and Chief Technology Officer at Novell
  • President of Bell Labs Research and Advanced Technologies at Lucent Technologies
  • Vice President of Technology for IBM

And that list is only a subset of the interesting roles he has played. In everything that Jaffe has done, he has shown commitment to open standards and open source, which makes him a perfect match for the W3C. 

"Web technologies continue to be the vehicle for every industry to incorporate the rapid pace of change into their way of doing business," said Dr. Jaffe. "I'm excited to join W3C at this time of increased innovation, since W3C is the place where the industry comes together to set standards for the Web in an open and collaborative fashion."

Leading the Web to Its Fullest Potential

As part of Jaffe's role, he will work with W3C Director Tim Berners-Lee, along with the rest of the W3C — staff and membership, and the great community to communicate the organization's vision and evolve it.

In his first blog post as CEO, Jaffe says his immediate priority is to "preserve and enhance the W3C culture of having an open consensus-based process."

He also says that he will blog often on the issues and encourage comments and/or direct emails to discuss issues of importance to the organization.

A long road ahead of him, Jaffe does seem excited to play such an important role in the evolution of the Web. We look forward to hearing more from him on initiatives such as HTML 5, the Semantic Web and the Mobile Web.