An artificially complex XML schema as a lock-in tool
A document format is a tool for sharing knowledge and, as such, should be as simple and accessible as possible in relation to the complexity of the document content itself. This remains true even when the format is based on an XML schema that is hidden from users when the document is displayed on screen.
Unfortunately, while an XML schema can be simple, it can also be unnecessarily complex, bloated, convoluted and difficult to implement without specific knowledge of its features. This is true even if the on-screen documents are identical. In this case, complexity is an intentional tactic used to lock users into a vendor, as is the case with the Microsoft 365 document format.
An XML schema comprises the structure, data types and rules of an XML document and is described in an XML Schema Definition (XSD) file. This tells the PC what to expect and checks that the data follows the rules. In theory, XML and XSD together form the basis of the concept of interoperability. However, in practice, an XML schema can be made so complex that it becomes a barrier rather than a bridge.
An “artificially complex” XML schema goes beyond the level of complexity needed to display even the most intricate content on screen. In fact, it is completely disconnected from the actual complexity of the content, to the extent that even a simple sentence such as “To be, or not to be, that is the question” becomes an inextricable sequence of tags that users cannot access.
This artificial complexity is characterised by a deeply nested tag structure with excessive abstraction, dozens or even hundreds of optional or overloaded elements, non-intuitive naming conventions, the widespread use of extension points and wildcards, the multiple import of namespaces and type hierarchies, and sparse or cryptic documentation.
In the case of the Microsoft 365 document format, the only characteristic not present is sparse or cryptic documentation, given that we are talking about a set of documents totalling over 8,000 pages. All the other characteristics are present to a greater or lesser extent, making life almost impossible for a developer trying to implement the schema.
To illustrate how this translates into a lock-in strategy, consider a railway system where the tracks are accessible to all, but the main train manufacturer imposes its own incredibly complicated control system. In theory, anyone could build a train compatible with the tracks, but the control system specifications are so convoluted that only the main train manufacturer can ultimately offer rail services.
The worst thing is that passengers don’t realise they are being held hostage by technical constraints that they cannot understand until ticket prices rise or the number of cities served declines. At this point, the main manufacturer can dictate its terms, which passengers are forced to accept.
This is very similar to what is happening in the world of information technology, where Microsoft is effectively forcing its customers to switch from Windows 10 to Windows 11 against their will. This switch has no technical justification and locks customers into using Windows 11 and Microsoft 365. This is because customers have completely ignored the problems that arise from using proprietary technologies.
If, over the years, the millions of Microsoft users who uncritically accepted a narrative that was credible to non-technical users but divorced from technological reality had taken a critical stance towards this monopoly, which would have raised doubts in any other sector, we would be in a very different situation today.
Instead, these users – including governments and supranational organisations – have allowed lock-in strategies, in which Microsoft 365’s artificially and unnecessarily complex XML document schema plays a fundamental strategic role, to become increasingly sophisticated and pervasive.
Therefore, if you are developing or choosing an XML-based system, bear in mind that complexity imprisons people, whereas simplicity and clarity set them free.