An in-depth look at the Selectors module for CSS.

Enthusiasm and political support for open data is based on three pillars: that it will increase transparency, improve efficiency and stimulate innovation. Meeting these promises has had several spectacular successes but there remains a lot of work to do before data becomes as much a part of the public infrastructure as, say, transport or leisure facilities. W3C's 'go to person' for open data and eGov in Europe assesses the road ahead, looking for pitfalls suggesting routes around some of the obstacles.

Phil Archer chairs a panel featuring Emer Coleman, former Deputy Director of UK Government Digital Service, Tomislav Korman, head of social media for the Croatian Government, Alberto Cottica, economist and expert in online participation, and Jed Shilling, Millenium Institute

SEMIC 2013 will offer a unique opportunity to explore and discuss how Public Administrations are tackling Semantic Interoperability issues to make information exchange more efficient and effective.

Phil Archer reviews the progress of the ISA Programme's Core Vocabularies within W3C's Government Linked Data Working Group and looks ahead to future vocabulary support at W3C.

The web is now over 20 years old, but still in its infancy. Books printed 100 years ago are still readable, and available in many cases. Will we still be able to read and access websites made today in 100 years time? Or will all our content be lost to future ages? What is needed to make the web age-tolerant? What do we want from the web in both the short and long term? Content Despite the use of style-sheets, the current web is almost completely visually-oriented. This locks the content into one particular representation, and makes it hard to repurpose. What we need is a web that is primarily content-oriented, with a final phase of presentation; only in that way can content be repurposed in the same way that data can be. Design for the web should be like design for a house style. It has a general style that the content can flow into. Multi-device We don't want to have to produce copies of our websites for each new type of platform or device. There needs to be a generic method of repurposing content to the formfactor of the device accessing it. Accessibility Even when we are 80, we will still want and need to use the web. How can we make our 30-year-old selves sensitive to the problem of our less-abled Authorability With the coming of HTML5, the web has stopped being about documents, and started being about programs. Now only programmers can produce modern web pages. What can be done to alleviate the problem? Availability HTTP, the protocol used for serving Web pages, has served us well for the last 20 years, but is beginning to show its age: it has become a single-point-of-failure for content. It enables DDoS attacks, makes it easy for governments and other agencies to censor sites and content, and just when a website becomes super-popular it can fail causing the website to crash and be unreachable. This talk will cover these points, and general approaches that could be used to make a coherent future web.

XForms is a high-level tool for defining user interfaces to XML data. With a design based on years of experience with the simple forms of HTML, XForms systematically distinguishes between the model (the information structures being edited, in the form of sets of XML documents) and the user interface and its appearance. As an XML vocabulary, XForms is embeddable in arbitrary host document languages; its user interface widgets can easily be represented in different ways for different devices and users. Forms of arbitrarily complex fixed structure can be easily represented in XForms. Mixed content, variable-depth recursion, and structural modifications to the model are more challenging. This introduction to XForms provides an overview of its capabilities and current limits and the prospects for overcoming them.

What if you could see everything as XML? XML has many strengths for data exchange, strengths both inherent in the nature of XML markup and strengths that derive from the ubiquity of tools that can process XML. For authoring, however, other forms are preferred: no one writes CSS or Javascript in XML. It does not follow, however, that there is no value in representing such information in XML. Invisible XML is a method for treating non-XML documents as if they were XML, enabling authors to write in a format they prefer while providing XML for processes that are more effective with XML content. There is really no reason why XML cannot be more ubiquitous than it is.

Le Livre Électronique est probablement le plus gros consommateur de Standards du Web actuel hors du Web lui-même. Les points de convergence entre notre moyen d'expression préféré et les eBooks sont nombreux mais les points de divergence également. Quels sont les apports du Livre Électronique dans HTML, les CSS, les autres langages ? Quels sont les spécifications du W3C qui doivent impérativement progresser pour aider le Livre Électronique ? Pouvez-vous transformer une collection de documents Web en Livre Électronique en moins que temps que Tristan Nitot en a besoin pour passer son fameux tutu rose ? Comment le W3C et l'IDPF, le consortium chargé d'EPUB, travaillent-ils ensemble ? Le Livre Électronique et le Web évoluent-ils à la même vitesse ? Bref, tout ce que vous avez voulu savoir sur les dessous Web du Livre Électronique sans jamais oser le demander.