XML
In 1996, the W3C entrusted Jon Bosak, an engineer at Sun Microsystems, with leading an ambitious working group. The mission was to design a markup language that would combine SGML’s structural power with a simplicity of use that SGML had never achieved. HTML dominated the web, but its limitations were becoming glaring: designed for visual formatting, it proved inadequate for logically organizing information.
Two years later, XML was officially born as a W3C recommendation. The language introduced strict tag-based syntax, imposed the notion of well-formed documents, and gave developers the freedom to create their own tag vocabularies through DTDs. Each sector could now shape its own data structures with flexibility without waiting for an organization to standardize them.
The major innovation lay in the radical separation between content and presentation. An XML document could be transformed into a web page, a PDF, or a text file, depending on current needs. XSLT, standardized the following year, provided the transformation tools necessary for this modularity. Data acquired unprecedented autonomy, freed from their destination format.
Web services emerged in 2000, e-commerce took hold, and businesses discovered the value of exchanging information between disparate systems without resorting to haphazard conversions. XML naturally became established. Its ecosystem grew richer: XPath let us navigate through documents, XQuery queried data, XML Schema gradually supplanted DTDs by providing more refined validation mechanisms.
This story has its roots much earlier, in 1969, in IBM’s laboratories. Charles Goldfarb, Edward Mosher, and Raymond Lorie developed GML there, SGML’s direct ancestor. Their insight: a document’s structure must be independent of its content. This principle, groundbreaking at the time, still underpins our approach to managing digital information.
Databases adapted. Traditional relational systems integrated native XML document storage, while specialized solutions appeared to meet specific needs. Entire sectors built their standards on this format, the pivot of service-oriented architectures known as SOAs: digital publishing reorganized its production chains, finance structured its data exchanges.
XML’s relative simplicity compared to SGML partly explains its success among developers. But it’s primarily its self-descriptive nature that appeals: an XML document carries within itself the keys to its understanding. This characteristic ensures a certain longevity: files remain readable and usable years after their creation, with external documentation mostly remaining optional.
JSON’s arrival in the mid-2000s somewhat disrupted the landscape. Lighter and more direct, it won over web development. Yet XML didn’t yield ground. It retains its relevance where structural rigor matters, where formal validation is essential, where complex transformations are necessary. The two formats coexist, each excelling in its domain.
XML has transformed our approach to documentation, encouraged structured thinking about information, and changed how organizations design their systems. The hierarchical markup principles it popularized are found in much more recent formats. The semantic web and modern microservice architectures bear its imprint.
The W3C orchestrated this entire standardization process with a method that serves as a reference. XML and its satellite technologies today form a coherent set of specifications, the result of remarkable collective work. These standards continue to evolve, adapt to emerging needs, and testify to the vitality of a format approaching its thirtieth year without showing its age.