Posts tagged "html"


GForm is great component where can be defined steps of questionnaire with any HTML. That means images, videos, maps, iframes and so on.

Questionnaire forms, as the name of the component says, are not part of the component. These forms are supposed to be created at Google Drive and then copied to the component. The best thing is that user responses will be stored at Google Drive Spreadsheet so they can be easily processed.

Individual steps can be submitted either by submitting the form of by countdown.

Menu item can point to any step or to list of all steps.

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.

Semantic Web: W3C Publishes Working Draft of HTML + RDFa Spec

The W3C (news, site) has been busy. They've released seven documents related to HTML, one of which is of interest to anyone working with HTML and another to anyone involved with the semantic web.


One of the documents released is HTML5 differences from HTML4. This resource is broken into sections according to feature type. Some examples include open issues which are still under debate within the mailing lists, as well as ways in which HTML5 will likely impact:

  • Web architecture
  • Web page syntax such as character encoding and DOCTYPEs
  • Character encoding
  • HTML itself such as new, changed and removed elements and attributes
  • APIs with new extensions added to HTMLDocument and HTMLElement

This document also offers changelogs listing the changes made in each of the HTML5 drafts.


The other document of interest is HTML+RDFa, which details the new working draft for embedding RDF into HTML. This update offers the following changes from the previous version:

  • Updating the processor (Infoset) that transforms XML fragments to HTML5 (referred to as "coercion")
  • Clarifying how to extract RDFa attributes through Infoset
  • Clarifying how to extract RDFa attributes through DOM2

Note that within the Infoset documentation it states that this is the last call for comments, so if you're planning on looking at the transformation process and giving any input, now is the time.

Also, within the HTML+RDFa document a number of sections are identified which refer to open issues, or blocked progress before being able to declare a Last Call.

For more on RDFa, see our primer at RDFa, Drupal, and a Practical Semantic Web.