slanted W3C logo

The eX Markup Language?

Eric van der Vlist

XML Prague 2012

Revisiting the question that was the tag line of XML Prague last year: "XML as new lingua franca for the Web. Why did it never happen?", Eric tries to answer to other questions such as: "where is XML going?" or "is XML declining, becoming an eX Markup Language?".
Picture © MyriamLouviot http://fr.wikipedia.org/wiki/Fichier:YoffGarbage.jpg

The eX Markup Language?

Eric van der Vlist

XML Prague 2012

Revisiting the question that was the tag line of XML Prague last year: "XML as new lingua franca for the Web. Why did it never happen?", Eric tries to answer to other questions such as: "where is XML going?" or "is XML declining, becoming an eX Markup Language?".

Welcome to the less technical and most controversial talk of the conference

There will be no time for questions (too many slides, too controversial)!

Picture © MyriamLouviot http://fr.wikipedia.org/wiki/Fichier:YoffGarbage.jpg

A suggestion for next year

My talk would have been different if I had seen Jeni's one before

Next year, can you please leave a couple of days before Jeni's openening keynotes and the next talk so that we can adapt?

Picture © Eric van der Vlist

XML as new lingua franca for the Web. Why did it never happen?

Tag line for XML Prague 2011

Still waiting for an answer...

Picture © skëne http://www.flickr.com/photos/skene/3874882162/
Flashback

Back in February 1998

Source: Wikipedia

Picture © DanCentury http://www.flickr.com/photos/dancentury/3917753198/

Design Goals for XML

  1. XML shall be straightforwardly usable over the Internet.

  2. XML shall support a wide variety of applications.

  3. XML shall be compatible with SGML.

  4. It shall be easy to write programs which process XML documents.

  5. The number of optional features in XML is to be kept to the absolute minimum, ideally zero.

  6. XML documents should be human-legible and reasonably clear.

  7. The XML design should be prepared quickly.

  8. The design of XML shall be formal and concise.

  9. XML documents shall be easy to create.

  10. Terseness in XML markup is of minimal importance.

Source: W3C Recommendation (February 1998)

Picture © Haundorf http://commons.wikimedia.org/wiki/File:Bundesarchiv_Bild_183-70282-0001,_Ingenieure_an_Reissbrettern.jpg

SGML On the Web

XML arose from the recognition that key components of the original web infrastructure -- HTML tagging, simple hypertext linking, and hardcoded presentation -- would not scale up to meet the future needs of the web. This awareness started with people like me who were involved in industrial-strength electronic publishing before the web came into existence.

Source: Jon Bosak

Picture © Eric van der Vlist http://eric.van-der-vlist.com/blog/wp-content/gallery/xml2002/adq.jpg

XML shall support a wide variety of applications

The big-gun database vendors, IBM and Oracle, see XML as a pathway into and out of their data management tools. The big-gun browser vendors, Netscape and Microsoft, see XML as the e-commerce everywhere technology. The big-gun book and document publishers, for all media, are seeing a new influx of tools, integrators, and interest but the direction XML publishing will take is less well-defined and more contingent on linking and style specs still in the hands of the W3C.

Source: Liora Alschuler for XML.com (December 1998)

Picture © Eric van der Vlist http://eric.van-der-vlist.com/blog/wp-content/gallery/xml2002/acr.jpg

XML hype

Stop the XML hype, I want to get off

As editor of XML.com, I welcome the massive success XML has had. But things prized by the XML community — openness and interoperability — are getting swallowed up in a blaze of marketing hype. Is this the price of success, or something we can avoid?

Source: Edd Dumbill (March 2001)

Picture © Eric van der Vlist http://eric.van-der-vlist.com/blog/wp-content/gallery/xml2001-speakers/aae.jpg

XML Sucks

I've spent years learning XML / I like XML / This is why www.XmlSuck.com is here

Source: PaulT (January 2001)

Picture © Divine Harvester http://www.flickr.com/photos/divine_harvester/2414090010/

Crowded Working Groups

Working Group size - so many people means it is difficult to gain consensus, or even know everyone's face. Conference calls are difficult.

Source: Mark Nottingham, about the SOAP W3C WG (May 2000)

Picture © Kalan http://commons.wikimedia.org/wiki/File:Overflowed_platform_of_Vyhino,_fore_part_3.jpg

Huge Working Groups + different directions

This is a huge responsibility for the Schema Working Group since it means that the defects of W3C XML Schema will be perceived by most as defects of XML.

Source: Eric van der Vlist on xml-dev (April 2001)

Picture © Eric van der Vlist

The XML crowd started to celebrate

XML is now as important for the Web as HTML was to the foundation of the Web. XML is everywhere.

Source: connet.us (February 2001)

Picture © Eric van der Vlist

Why such a hype?

When the wind is strong enough, even flatirons can fly.

Source: Anonymous (February 2012)

Picture © Mouleesha http://commons.wikimedia.org/wiki/File:ClothesIron.JPG

Two standards to maintain

The W3C had now to maintain:
  • XML, a subset of SGML

  • HTML, a SGML application that did not match the XML subset

Picture © L.Miguel Bugallo Sánchez http://commons.wikimedia.org/wiki/File:Bascula_9.jpg

Obvious (Technically speaking)

Refactor HTML to meet the XML requirements

XML was (supposedly) so successful that everyone will follow

Picture © Catalogue des signaux routiers français http://fr.wikipedia.org/wiki/Fichier:Signal_C28-3.svg

XHTML value added

Unfortunately from a web developer perspective the benefits of XHTML 1.0 were not that obvious:

the problem with XHTML is :

a) it's different enough from HTML to create new compatibility problems.

b) it's not different enough from HTML to bring significant advantages.

Source: Eric van der Vlist on XHTML-DEV (May 2000)

Picture © Kelvin Kay http://en.wikipedia.org/wiki/File:Gifts_xmas.jpg

Microsoft was feeding the hype

XML, XML, Everywhere

There's no avoiding XML in the .NET world. XML isn't just used in Web applications, it's at the heart of the way data is stored, manipulated, and exchanged in .NET systems.

Source: Rob Macdonald for MSDN (February 2001)

Picture © Chris Pirillo http://www.flickr.com/photos/lockergnome/191919351/

Everywhere except in IE

No support for application/xhtml+xml in IE

You can serve XHTML if you don't say so!

Picture © BlubrNL http://www.flickr.com/photos/blubrblog/4326100513/

By 2001, the landscape was set

  • XML == dominant buzzword => false impression of wide adoption

  • Many developers deeply upset by the hype

  • Serving XHTML web pages as such is not an option

Picture © Per Olof Forsberg http://www.flickr.com/photos/perolofforsberg/6180265227/

Hypes in 2001 - 2003

The XML hype was still high

Another hype was growing...

Picture © Unknown Japanese copyists http://fr.wikipedia.org/wiki/Fichier:The_Great_Wave_off_Kanagawa.jpg

Web 2.0

The Web we know now, which loads into a browser window in essentially static screenfuls, is only an embryo of the Web to come.

Ironically, the defining trait of Web 2.0 will be that it won't have any visible characteristics at all. The Web will be identified only by its underlying DNA structure-- TCP/IP (the protocol that controls how files are transported across the Internet); HTTP (the protocol that rules the communication between computers on the Web), and URLs (a method for identifying files).

The Web will be understood not as screenfuls of text and graphics but as a transport mechanism, the ether through which interactivity happens.

Source: Darcy DiNucci (1999)

Picture © Markus Angermeier & Luca Cremoninihttp://en.wikipedia.org/wiki/File:Web_2.0_Map.svg

Ajax (Asynchronous JavaScript and XML)

Ajax isn’t a technology. It’s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:

Source: Jesse James Garrett (February 2005)

Picture © Marie-Lan Nguyen http://en.wikipedia.org/wiki/File:Achilles_Ajax_dice_Louvre_MNB911_n2.jpg

XML Domination...

Back in 2005, we could still think that XML would dominate the Web

Both for documents (XHTML) and data

Picture © Bubba73 http://en.wikipedia.org/wiki/File:CheckmateProper.jpg

Was a dream!

This vision defended by the W3C, has been torpedoed by:

Picture © Deutsches Bundesarchiv http://en.wikipedia.org/wiki/File:Bundesarchiv_DVM_10_Bild-23-61-28,_Am_Torpedorohr.jpg

W3C

Founded in 1985

Browsers War I battle ground

Picture © United Kingdom Government http://en.wikipedia.org/wiki/File:Royal_Irish_Rifles_ration_party_Somme_July_1916.jpg

2005: new generation

  • Netscape had disappeared
  • MSIE was frozen
  • Mozilla was born
  • Apple had published Safari
  • Opera became free (as in free beer)
Picture © TimVickers http://en.wikipedia.org/wiki/File:Ape_skeletons.png

WHATWG

Software developers are increasingly using the Internet as a software platform, with Web browsers serving as front ends for server-based services. Existing W3C technologies — including HTML, CSS and the DOM — are used, together with other technologies such as JavaScript, to build user interfaces for these Web-based applications.

However, the aforementioned technologies were not developed with Web Applications in mind, and these systems often have to rely on poorly documented behaviors. Furthermore, the next generation of Web Applications will add new requirements to the development environment — requirements these technologies are not prepared to fulfill alone. The new technologies being developed by the W3C and IETF can contribute to Web Applications, but these are often designed to address other needs and only consider Web Applications in a peripheral way.

The Web Hypertext Applications Technology working group therefore intends to address the need for one coherent development environment for Web Applications. To this end, the working group will create technical specifications that are intended for implementation in mass-market Web browsers, in particular Safari, Mozilla, and Opera.

Source: WHATWG (June 2004)

Picture © Catalogue des signaux routiers français http://fr.wikipedia.org/wiki/Fichier:C24b-1.svg

W3C choice

  • Push XHTML recommendations that might never be implemented in any browsers
  • Ditch XHTML and ask the WHATWG to come back

HTML work resumed within W3C in 2007

Picture © Hans Andersen http://fr.wikipedia.org/wiki/Fichier:Auguste_Rodin_-_Grubleren_2005-02.jpg

JSON

Unfortunately, XML is not well suited to data-interchange, much as a wrench is not well-suited to driving nails. It carries a lot of baggage, and it doesn't match the data model of most programming languages. When most programmers saw XML for the first time, they were shocked at how ugly and inefficient it was. It turns out that that first reaction was the correct one. There is another text notation that has all of the advantages of XML, but is much better suited to data-interchange. That notation is JavaScript Object Notation (JSON).

Source: Douglas Crockford (JSON: The Fat-Free Alternative to XML)

Picture © antjeverena http://www.flickr.com/photos/antjeverena/2684726518/

Why?

A number of reasons can be found for this failure:
  • Bad timing between the XML and HTML specifications (see Adam Retter's presentation at XML Amsterdam 2011).

  • Lack of quality of some XML recommendations (XML Namespaces, XML Schema, ...).

  • Lack of pedagogy to explain why XML is the nicer technology on the earth.

  • Dumbness of Web developers who do not use XML.

  • ...

Picture © DanCentury http://www.flickr.com/photos/dancentury/3917753198/

XML vs Domain Specific Languages

XML is about extensibility

When extensibility is not required, XML will always loose against DSLs:

  • RELAX NG compact syntax
  • JSON
  • HTML
  • N3
  • CSS
  • ...
Picture © Wenger S.A. http://en.wikipedia.org/wiki/File:The_giant_wenger.jpg

Timing

Yes, HTML should have been created as an XML application,

But that was not the case!

Picture © Eric van der Vlist

The old prediction

XML arose from the recognition that key components of the original web infrastructure -- HTML tagging, simple hypertext linking, and hardcoded presentation -- would not scale up to meet the future needs of the web. This awareness started with people like me who were involved in industrial-strength electronic publishing before the web came into existence.

Source: Jon Bosak

Picture © Sanjay Acharya http://en.wikipedia.org/wiki/File:Quartz_crystal.jpg

Was wrong

HTML did scale!

Picture © Eddau, Janke and Mike Chapman http://en.wikipedia.org/wiki/File:Train_scale_4-4-0.JPG

Compatibility

The first Google index in 1998 already had 26 million pages

The XML design meant:

  • Existing pages have to be upgraded
  • "What you've done so far was crappy, here is how you should work"
Picture © Kaptain Kobold http://www.flickr.com/photos/kaptainkobold/3203311346/

The missing requirement

Existing (valid) HTML documents must be considered well formed XML.

This should have been the first design goal

Picture © Kevyn http://en.wikipedia.org/wiki/File:TenCommandmentsAustinStateCapitol.jpg

XML success

XML has a unique toolbox

  • To manipulate and exchange information
  • To power web sites
Picture © Per Erik Strandberg http://en.wikipedia.org/wiki/File:20060513_toolbox.jpg

The XML ecosystem

A new buzzword?

Java, JavaScript, Ruby are becoming ecosystems

We have created a strong ecosystem that goes beyond the XML syntax

Picture © Eric van der Vlist

The XML jewel

A generic data model

Picture © Marie-Lan Nguyen http://en.wikipedia.org/wiki/File:Earring_Mycenae_Louvre_Bj135.jpg

Growing our ecosystem

Forget batles that have been lost

Focus on the data model and tools

Picture © Eric van der Vlist

Diversity makes strong ecosystems

Our data model must support:

  • HTML5 (more during the next talk and panel discussion)
  • JSON

Other possible candidates:

  • Graphs (RDF)
  • Name/value pairs (NoSQL)
  • Tables (SQL)
  • Overlaps (LMNL)
  • ...
Picture © Eric van der Vlist

Refactoring?

Past initiatives have failed so far (Simple XML, SML, XML 2.0, Micro XML, ... and even XML 1.1)

What benefit can compensate a lack of compatibility?

What benefit if it stays compatible?

More during Anne van Kesteren's presentation!

Picture © Bain News Service http://en.wikipedia.org/wiki/File:Stone_sculptor_at_work.jpg

XML is more that syntax

Angle Brackets Are a Way of Life

Source: Planet XMLHack

Picture © <?xmlhack?> http://planet.xmlhack.com/