W3C

Talks by W3C Speakers (Recent and Upcoming)

Many in the W3C community — including staff, chairs, and Member representatives — present W3C work at conferences and other events. Below you will find a list some of the talks. All material is copyright of the author, except where otherwise noted.

March 2016

April 2016

May 2016

  • 2016-05-05 (5 MAY)

    HTML5

    by Steven Pemberton

    J.Boye Philadelphia 16

    Philadelphia, USA

    Relevant technology area: Web Architecture.

  • 2016-05-09 (9 MAY)

    Catching Up with Accessibility: Beginner's Basics (tutorial)

    by Shawn Henry

    AccessU

    Austin, TX, USA

    Relevant technology area: Web Design and Applications.

    Abstract:
    If you're just getting started in web accessibility or if you want to make sure you have the basics covered, this class is for you. It provides you with a solid foundation for understanding how people with disabilities use the web, experiencing common web accessibility barriers, and learning the easy things and the most important things you can do now to get up to speed on accessibility. We'll focus mostly on the user experience aspects of web accessibility, and mention a little about the underlying code. (You don't need to know HTML or coding to get a lot from this class.) For those who want to learn about checking/evaluating web accessibility, this class provides a good basis for tomorrow's class, "Easy Checks for Web Accessibility: Get the Gist (No Experience Necessary)."
  • 2016-05-09 (9 MAY)

    Easy Checks for Web Accessibility: Get the Gist (No Experience Necessary) (tutorial)

    by Shawn Henry

    AccessU

    Austin, TX, USA

    Relevant technology area: Web Design and Applications.

    Abstract:
    Have you ever wondered: "Is this web page accessible?" If you can use the Web, you can get a good start at an answer — no expertise required! Whereas web accessibility evaluation tools spit out complex results that require knowledge to interpret, the W3C resource "Easy Checks - A First Review of Web Accessibility" provides a different approach. It walks you through some basic accessibility evaluation with guidance for understanding what you are checking. Most people can complete these checks in about 10 minutes once they understand them. If you're new to web accessibility, it will take some time to learn. This session provides a jump start to understanding and using Easy Checks so that you can start to answer: "Is this web page accessible?” (Monday's class, "Catching Up with Accessibility: Beginners Basics," provides a handy background for this class; however, it is not a prerequisite.)
  • 2016-05-09 (9 MAY)

    The WAI to Web Accessibility: An Interactive Tour Through Resources form the W3C Web Accessibility (tutorial)

    by Shawn Henry, Sharron Rush, and Brent Bakken

    AccessU

    Austin, TX, USA

    Relevant technology area: Web Design and Applications.

    Abstract:
    W3C WAI is best know for WCAG, the international web standard Web Content Accessibility Guidelines. Yet WAI provides a wealth of web accessibility information for project managers, content authors, developers, designers, testers, policy makers, trainers, people with disabilities, accessibility advocates, and others. However, some people are overwhelmed from starting with the standards. But there's an easier way! In this class we'll help you find the gold within the WAI website. WAI provides resources to help you create an environment where accessibility flourishes -- whether you need to better understand how people use the web, prepare a business case to secure management support, train developers new to accessibility, integrate accessibility into a project plan, write an accessibility policy, meet international standards, or learn best practices for mobile accessibility. Whatever your web accessibility questions, and we'll show you where to go for answers. You'll also get a sneak peak at new resources in development and learn how you can help advance web accessibility and share your insights with others.
  • 2016-05-12 (12 MAY)

    The Second Enlightenment

    by Steven Pemberton

    DrupalJam 2016

    Utrecht, The Netherlands

    Relevant technology area: Web Architecture.

  • 2016-05-19 (19 MAY)

    Securing the open web platform

    by Wendy Seltzer

    OSCON

    Austin, TX, USA

    Abstract:
    One of the Web’s greatest strengths is its generality, its openness to new links and unexpected uses. Openness also means that different applications and users have different security goals and threat models. A mash-up that’s desired by one may be dangerous to another. As stewards of the Open Web Platform, W3C aims to accommodate these different needs through modular components, including work on user security and authentication, cooperative policy enforcement, and platform-level reviews. I’ll talk about what’s done, what’s in progress, and where we’re looking next to support an environment for trustworthy application development. Among the topics of current work, I will share updates on: WebCrypto and Authentication: can we kill the password yet? WebAppSec CSP and more: cooperative policy enforcement in the browser HTTPS upgrade: making it easier for Web apps to go secure Security and Privacy Considerations: building security in to specs and their implementations We’ll also talk about broader patterns. While we can’t guarantee the security of “the Web” as an application platform, we can make it easier for authors to write secure Web apps, and for users to distinguish those they trust. Can we take the hard-earned lessons of Web security to other environments that are opening, such as the burgeoning universe of connected things and cars? Can we get both security and space for innovation?
  • 2016-05-19 (19 MAY)

June 2016

  • 2016-06-05 (5 JUN)

    Parse Earley, Parse Often

    by Steven Pemberton

    XML London

    London, United Kingdom

    Relevant technology areas: Web Architecture and XML Core Technology.

    Abstract:
    Invisible XML, ixml for short, is a generic technique for treating any parsable format as if it were XML, and thus allowing any parsable object to be injected into an XML pipeline. Based on the observation that XML can just be seen as the description of a parse-tree, any document can be parsed, and then serialised as XML. The parsing can also be undone, thus allowing roundtripping. This paper discusses issues around grammar design, and in particular parsing algorithms used to recognise any document, and converting the resultant parse-tree into XML, and gives a new perspective on a classic algorithm.
  • 2016-06-17 (17 JUN)

    The evolution of CSS 4 Color

    by Chris Lilley

    CSS Day

    Amsterdam, The Netherlands

    Relevant technology areas: Browsers and Other Agents and Web Design and Applications.

August 2016

September 2016

  • 2016-09-24 (24 SEP)

    REST Interfaces to the Internet of Things

    by Steven Pemberton and Jack Jansen

    EuroIA 2016

    Amsterdam, The Netherlands

    Relevant technology areas: Web of Devices, Web Architecture, and XML Core Technology.

    Abstract:
    This talk shares insights from an on-going project coordinating data from Internet of Things (IoT) devices, and using a declarative interface to that data. REST (REpresentational State Transfer) is the architectural basis of the web. As Wikipedia points out “REST’s coordinated set of constraints, applied to the design of components in a distributed hypermedia system, can lead to a higher-performing and more maintainable software architecture.” So how can you apply the same ideas to the Internet of Things? The Internet of Things is driven by many tiny low-powered processors that produce data in a variety of different formats, and produce the data in different ways, sometimes on demand (such as thermostats), sometimes by pushing it (such as presence detectors). Traditionally, applications have to be a mash up of accesses to devices and formats. To use the data in a cohesive application, the data has to be collected and integrated; this allows very low demands to be put on the devices themselves. This project places a thin REST-layer around a diverse collection of Internet of Things devices, hiding the data-format and data-access differences, and updating the devices automatically as needed; this then allows a REST-style declarative interface to access and control the devices without having to worry about the variety of device-interfaces and formats.

November 2016

  • 2016-11-21 (21 NOV)

    XForms, the only Standard Web Framework

    by Steven Pemberton

    NLUUG najaarsconferentie
    (NLUUG Autumn Conference)

    Bunnik, The Netherlands

    Relevant technology areas: Web Architecture, XML Core Technology, and Web Design and Applications.

    Abstract:
    XForms is a W3C standard that was originally designed to allow the specification of form-handling on the web. However, after the release of version 1.0, it was quickly realised that with a small amount of generalisation the markup could be used for more general processing and application definition. And so was born XForms 1.1. XForms has now been in use for a number of years, and is widely used on websites, but also for other applications, such as the definition of machine interfaces, the operation of submarines, for ship-building, banking and insurance, food processing, medical research, and many others. The Dutch weather service KNMI is based on XForms; several Dutch government ministries use XForms. XForms is an integral part of ODF, the Open Office Format. XForms has a number of unique properties when compared with most framework languages. Firstly it has a strict separation of data and user-interface, allowing you to specify what might be called data sheets with initial values, types, constraints and dependencies, separately from the interface. Secondly, the interface uses intent-based controls that only specify what the control is supposed to do, and not how it should achieve that. That means for instance that the same control can drive a menu, or a drop down list or radio buttons, depending on needs. This can be changed by style sheets for instance. This makes applications far more device-independent, since an application can adapt to its environment, rather than requiring the author to write different applications for different devices. Thirdly, functionality is specified declaratively rather than procedurally. This reduces the size of application significantly, and vastly reduces production times and costs (examples have shown that an order of magnitude savings can be achieved). This talk introduces the elements of XForms, and then develops a Google-maps-style application in about 100 lines of code.

Extra links