W3C

Talks by W3C Speakers

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.

Listing is based on the following search constraints:

  • Possible presentation dates: past few months and upcoming
  • Technology area: Web Architecture

May 2016

June 2016

  • 2016-06-05 (5 JUN)

    Parse Earley, Parse Often

    by Steven Pemberton

    XML London

    London, United Kingdom

    Relevant technology areas: XML Core Technology and Web Architecture.

    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.

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, XML Core Technology, and Web Architecture.

    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 Design and Applications, XML Core Technology, and Web Architecture.

    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