For years, technology pundits have craved convergence and interoperability. In recent times, there has been a big push for the 'three' screens nirvana. The three screens ideal, encompasses mobile phone, PC and TV screen. From a content supplier point of view, the three screen approach means building content for the consumer and delivering it to the three screens - those being the mobile phone, the PC client and the TV in the living room. In order to make this three screen ideal a reality, there needs to be an enabling technology to make it happen. This is the stumbling block. How to make content from one source adaptable to threee screens? Enter SVG. With SVG, content can be authored to apply to any size screen. Scalability makes it possible. Industry has recognized this, and in response industry has put into place a number of derived specifications that make the three screen ideal a possibility. On the mobile front, the American ATSC body has adopted SVG Tiny 1.2 as the standard overlay for interactive TV on mobile phones. In the TV front, the Open IPTV forum has also chosen SVG Tiny 1.2 as the primary interactice layer for video delivered over the internet directly to TVs in the living room. At the same time, we see SVG based video enabling total interactivity for PC application areas. Maybe SVG is the glue that can finally make this video convergence a reality? Demonstrations of Open IPTV forum interactive video alongside ATSC M/H video as deployed for USA interactive Mobile DTV and accompanying PC based applications will be showcased along with examples of the convergence and business cases for SVG as the main enabling technology to make interactive video distribution a reality on all devices today.

Description of how SVG, CSS3, and WOFF fonts give high quality typography.

The Web Content Accessibility Guidelines (WCAG) Version 2.0, was published as a final W3C Recommendation Web Standard on December 11, 2008. Many private and public sectors across Canada and the globe have already moved, or are moving, to adopt these standards. This webinar is intended to share lessons learned, pitfalls, and ensure a base level of knowledge among policy makers, standards areas and web developers. CWDO will be hosting an in-depth webinar being conducted by Michael Cooper from the W3C that will demystify WCAG 2.0 and help everyone understand how to implement the standards.

Can embedded data boost the success of a Web Site. Is there:

• better ranking in search results?
• better relation between searches and results (generating a higher conversion rate)?
• more links to the page (including its data)?
• unexpected reuse of the page (or its data)?

Today there is quite some noise about how to embed data into a web site. Yahoo, Facebook, Newsweek, O'Reilley, the US White House, Google, ... make more and more use of or have announced support for RDFa, W3C's Standard for including data in Web Sites. The talk will look at some examples of how data on Web pages is used by some of the big players.

The Worldwide Web Consortium Multimodal Interaction Working Group has defined Extensible Multimodal Annotation (EMMA) as a standard for representing multimodal user inputs. As a standard, EMMA is useful for supporting interoperability among the many components that can comprise a virtual agent, particularly those components concerned with user input in a variety of modalities. In addition to supporting interoperability, a standard such as EMMA is valuable for supporting human annotation of user inputs, as well as in support of aggregative analyses of user sessions.

I detta seminarium presenteras vad HTML5 och CSS3 är; vilka nya funktionaliteter som har lagts till (och vad som tagits bort); vilka kritiska krav som driver arbetet med standardisering av dessa teknologier; vad som återstår innan standardiseringen är klar.

Panelists Include: • Malcolm Crompton - Managing Director, Information Integrity Solutions and former Federal Privacy Commission • Kai Rannenberg, - Professor, Goethe University Frankfurt • Roger Clarke - Principal, Xamax Consultancy • Linda Matthews - Privacy Commissioner, Office of the Information Commissioner (Qld) • Anna Sharpe - Partner, Clayton Utz

HTML5 is being developed as the next major revision of HTML. Along with technologies like SVG, CSS3, and various APIs, the HTML5 Platform aims at enabling rich Web applications, including with video and graphic animation. Major Web browsers are all rushing to implement this new wave.

HTML5, the next version of the HTML language, integrates support for video, making video a first class citizen of the Web. It also includes support for SVG, a 2D vector graphic language. Using the HTML5 media API and open source authoring tools such as inkscape, this live coding session will demonstrate how to develop from scratch your own interface for playing videos in HTML, using standardized Web technologies. This session will also highlight best-in-class HTML5 video players.

HTML5 is being developed as the next major revision of HTML. Along with technologies like SVG, CSS3, and various APIs, the HTML5 Platform aims at enabling rich Web applications, including video and graphic animation.

In this talk, Matt will present some of the new technologies that will enable the mobile Web apps of the future.  This talk will review the current mobile Web landscape, in particular contrasting Web apps against native mobile apps,  He will also review new efforts including new geolocation APIs and protocols, a "points of interest" format for sharing information about places, and an overview of the w3c's foray into enabling Augmented Reality on the Web.

Integration of the huge amount of data accessible on the Web is one of the major challenges of the coming years. The goal of the Semantic Web is to provide a set of technologies to achieve this type of integration, i.e., to be able to develop applications that can quickly and reliably mash up different datasets, and do that based on standard technologies as opposed to ad-hoc and site specific approaches.

This presentation uses a very simple (and, of course, a bit artificial...) example from the book publication world to show how the goal of data integration can be achieved using Semantic Web technologies. Without going into technical details, the roles of a unified data format (i.e., RDF), of vocabularies, and of queries are presented. The goal is not to give a thorough description of any particular technology but rather to give a feel of what the Semantic Web technologies aim to achieve and how, and to generate further discussions.

I detta seminarium presenteras vad HTML5 och CSS3 är; vilka nya funktionaliteter som har lagts till (och vad som tagits bort); vilka kritiska krav som driver arbetet med standardisering av dessa teknologier; vad som återstår innan standardiseringen är klar.

The progressive deployment of HTML5 and its many accompanying technologies open the way to using the Web to create applications with advanced features.

The Web of the future is no longer limited in terms of user interface. The deployment of CSS3, the long awaited possibility to use one’s own fonts, the support for <canvas> and <video>, and the arrival of SVG on all the browsers open up a myriad of possibilities.

This also means that the times of clicks and forms as the only possible interactions are now something of the past. APIs that create a stronger integration with the user’s device — geolocation, accelerometer —, or with the user’s data — calendar, contacts list —, that were only available to native applications are now being added to the Web of the future, where mobile is guaranteed to play a big role.

The availability of running Web applications under a local context, either as widgets or as offline applications, will remove the last differences between today’s native applications and tomorrow’s Web apps, while keeping a strong stance on the user’s security and privacy.

We are offering to review these various changes that will turn a number of today’s Web developers into tomorrow’s application developers.

The tutorial will provide you with a good understanding of the many unique characteristics of non-Latin writing systems, and illustrate the problems involved in implementing such scripts in products. It does not provide detailed coding advice, but does provide the essential background information you need to understand the fundamental issues related to Unicode deployment, across a wide range of scripts. It has also proved to be an excellent orientation for newcomers to the conference, providing the background needed to assist understanding of the other talks! The tutorial goes beyond encoding issues to discuss characteristics related to input of ideographs, combining characters, context-dependent shape variation, text direction, vowel signs, ligatures, punctuation, wrapping and editing, font issues, sorting and indexing, keyboards, and more. The concepts are introduced through the use of examples from Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Hindi/Tamil, Russian and Greek. While the tutorial is perfectly accessible to beginners, it has also attracted very good reviews from people at an intermediate and advanced level, due to the breadth of scripts discussed. No prior knowledge is needed.

If the Latin Alphabet is not your (or your customer's) main script, there are many good reasons for including non-Latin characters in a Web address (URL/URI). This presentation will tell you why, when, and how you can and should do this, and provide the necessary background to make things work for servers and clients.

Non-ASCII characters have been used in Web addresses for more than a decade. Such Web addresses have been called Internationalized Resource Identifiers (IRIs), and since 2005 have been specified in RFC 3987. Early this year, the IETF chartered a Working Group to update the RFC 3987.

The presentation will first explain the basic rules for working with IRIs, in particular the conversion to URIs via UTF-8 and percent-encoding. To provide a deeper understanding, we will then concentrate on the major issues that the IRI Working Group is working on addressing:

• Moving from defining IRIs as a presentation element, while restricting protocols to using URIs, to defining IRIs as protocol elements on par with URIs.
• Balancing between syntactical uniformity for long-term simplicity and backwards conformance with established browser behavior in particular for the domain name and fragment identifier parts of an IRI.
• Moving the specification from a before-after descriptive style to a more procedural style that covers edge cases of implementations existing in the wild.
• Comparing, normalization, and security issues for IRIs.
• Restrictions and display advice for bidirectional IRIs.

Work has been under way at the W3C to define extensions for handling of bidirectional text on the Web. These improvements draw on the experience of experts who use these languages themselves and have found gaps in the current specifications. Topics under discussion include ways of avoiding directional issues when inserting substrings into text from an external source (such as a database), how to guess which side of a form field to begin displaying text and how to retain information about the directionality of text input into forms, how to ensure that browser chrome respects directional information, how to allow for icons and graphics to be automatically flipped in different directional text, etc. The proposals are targeted initially at HTML5, but are also relevant for other markup. This talk will provide an overview of the proposals made, and progress on their adoption in specifications.

The Mobile Web Best Practices document became a Recommendation in July 2008 but was largely finished a year before then. Is it still relevant? (Yes, argues Phil Archer, but with caveats).

This talk will present an update on the state of standardisation of HTML5 and CSS2/CSS3, two of the core technologies for rich web applications. We will also give a glimpse of results and plans for other supporting web technologies, like SVG, audio/video, mobile platforms (geolocation, device APIs, ...), widgets, etc., that enable the web to be a ubiquitous platform for network-based applications.