Competition Law and Semantic Interoperability

Introduction

Semantic interoperability refers to the ability of two or more technologically distinct systems to exchange information and understand the meaning, structure, context, and functional significance of that information consistently.

It goes beyond simple technical connectivity.

For example:

• Syntactic interoperability: System A can transmit a data file to System B.
• Technical interoperability: System A and System B can communicate through compatible protocols or APIs.
• Semantic interoperability: System B can correctly understand what the data from System A means and use it in the intended way.

In modern digital markets, semantic interoperability can become a competition-law issue because dominant firms may control the standards, APIs, data schemas, protocols, metadata, authentication systems, or technical documentation needed for rivals to interact effectively with their ecosystem.

The central competition question is therefore:

When does control over the meaning and interpretation of data become a source of market power capable of excluding competitors?

The issue is particularly important in operating systems, cloud computing, healthcare information systems, payment networks, connected vehicles, IoT, AI platforms, digital advertising, enterprise software and digital ecosystems.

I. Meaning and Elements of Semantic Interoperability

Semantic interoperability generally requires four layers:

1. Common data vocabulary

Systems must understand the same concepts.

For example:

"Customer ID", "Account Holder", and "User Identifier"

may refer to the same underlying concept but have different meanings across systems.

2. Common data structures

The systems must understand how information is organised.

Examples include:

• JSON schemas;
• XML schemas;
• metadata structures;
• database fields;
• API specifications;
• machine-readable taxonomies.

3. Common interpretation

The receiving system must understand the substantive meaning of the information.

For example, an electronic health record containing "BP 120/80" must be interpreted as a blood-pressure measurement rather than merely two numerical values.

4. Functional interoperability

The information must be capable of being used by the receiving system to perform the relevant function.

Thus, interoperability may exist formally while being commercially ineffective.

II. Why Semantic Interoperability Matters to Competition

Semantic interoperability can influence competition through several mechanisms.

1. Network effects

Digital platforms often become more valuable as more users, developers and complementary businesses participate.

If a dominant platform controls the relevant semantic standards, interoperability with that platform may become commercially essential.

This can produce:

More users → more developers → more complementary products → greater platform attractiveness → more users.

A rival that cannot meaningfully interoperate may therefore face a substantial disadvantage.

2. Switching costs

Semantic incompatibility can make migration difficult.

A business may technically be able to leave a platform but still face enormous costs because:

• historical data cannot be interpreted;
• customer records require conversion;
• workflows must be rebuilt;
• employees require retraining;
• applications need redevelopment;
• APIs must be rewritten.

Consequently, interoperability can affect contestability even when there are nominal alternatives.

3. Data portability

Data portability is closely connected with semantic interoperability.

Suppose Platform A permits users to export their data but provides it in a proprietary format that Platform B cannot meaningfully understand.

Formally:

Data portability exists.

Practically:

Effective portability does not.

Competition authorities may therefore examine not merely whether data can be transferred but whether the transfer allows meaningful use by competing services.

III. Semantic Interoperability and Dominance

Semantic interoperability becomes particularly important where an undertaking has substantial market power.

A dominant undertaking might control:

• proprietary protocols;
• APIs;
• technical standards;
• authentication mechanisms;
• data dictionaries;
• metadata;
• cloud interfaces;
• interoperability specifications;
• identity systems;
• application-development frameworks.

The competitive concern arises when the undertaking uses that control to disadvantage competitors.

Possible conduct includes:

1. refusing access;
2. delaying access;
3. providing incomplete specifications;
4. discriminatory access;
5. degrading interoperability;
6. changing APIs selectively;
7. withholding technical documentation;
8. imposing unreasonable licensing conditions;
9. restricting interoperability with competing products;
10. deliberately creating incompatible semantic standards.

IV. Refusal to Interoperate as an Abuse of Dominance

The traditional refusal-to-deal doctrine is important here.

Competition law generally does not require a monopolist or dominant firm to cooperate with every competitor.

However, exceptional circumstances can justify intervention where refusal to provide access or interoperability information has exclusionary effects.

The classic European framework developed through cases such as Magill, Bronner, IMS Health, and particularly Microsoft.

V. Essential-Facility Dimension

Semantic interoperability can sometimes resemble an essential facility problem.

The basic structure is:

Dominant upstream system
↓
Essential interoperability/data/interface
↓
Competitive downstream market

If rivals cannot effectively compete downstream without meaningful access to the interoperability layer, withholding that access may become an antitrust concern.

However, not every useful interface is an essential facility.

Courts have traditionally applied stringent conditions before imposing compulsory access.

VI. Key Case Laws

1. Microsoft Corp. v Commission, Case T-201/04 (2007)

Facts

Microsoft possessed a dominant position in PC operating systems.

Its Windows operating system contained information concerning protocols necessary for work-group server operating systems to communicate effectively with Windows PCs and servers.

Microsoft refused to provide sufficient interoperability information to competing server-operating-system suppliers.

Legal issue

Whether Microsoft's refusal to provide interoperability information constituted an abuse of dominant position.

Decision

The General Court upheld the Commission's principal findings concerning Microsoft's refusal to supply interoperability information.

The Court confirmed that the relevant interoperability information consisted of technical specifications concerning interaction between systems rather than disclosure of Microsoft's source code.

The Commission had concluded that Microsoft's conduct risked eliminating competition in the work-group server operating-system market and ordered disclosure of interoperability information on reasonable and non-discriminatory terms.

Importance for semantic interoperability

This is the central competition-law precedent for interoperability.

It demonstrates that interoperability can concern much more than physical connection.

The important information consisted of rules governing how systems interact and communicate.

The case therefore provides a foundation for analysing modern semantic interoperability involving:

• APIs;
• data structures;
• protocols;
• software ecosystems;
• cloud services;
• enterprise platforms.

The case also shows that a competition authority can require technical specifications without necessarily requiring disclosure of source code.

2. IMS Health GmbH & Co. OHG v NDC Health GmbH, Joined Cases C-418/01 (2004)

Facts

IMS Health developed a particular 1,860-brick geographical structure used for pharmaceutical-sales data in Germany.

The structure became widely used as an industry standard.

Competitors seeking to supply competing pharmaceutical-data services needed to use that structure.

Legal issue

Whether refusal to license an intellectual-property-protected system could constitute an abuse of dominance.

Principle

The Court applied the stringent conditions associated with compulsory licensing and refusal to supply.

The case is important because it established that refusal involving intellectual property can raise Article 82/now Article 102 concerns only in exceptional circumstances.

Importance for semantic interoperability

An industry-wide data architecture can effectively become a semantic standard.

If an entire industry uses a particular structure to interpret commercial information, access to that structure may become important for downstream competition.

IMS Health therefore provides an important bridge between:

IP rights → industry standards → data architecture → interoperability → competition.

Later jurisprudence, particularly Microsoft, developed the relationship between these concepts further.

3. Magill TV Guide Ltd v Commission, Joined Cases C-241/91 P and C-242/91 P (1995)

Facts

Television broadcasters controlled copyright-protected programme listings.

Magill sought to produce a comprehensive weekly television guide using information controlled by the broadcasters.

The broadcasters refused to license the relevant information.

Principle

The Court recognised circumstances in which refusal to license intellectual property could constitute an abuse of dominance.

The classic conditions included:

1. the information being indispensable;
2. refusal preventing the emergence of a new product for which consumer demand existed;
3. refusal being unjustified; and
4. reservation of the market to the right-holder.

Relevance to semantic interoperability

Although Magill was not an interoperability case in the modern technological sense, its reasoning is highly relevant to proprietary information required to create interoperable competing products.

It establishes the exceptional nature of compulsory access where intellectual property is involved.

4. Bronner v Mediaprint, Case C-7/97 (1998)

Facts

Bronner operated a newspaper and sought access to Mediaprint's newspaper-delivery system.

Mediaprint had an extensive distribution network.

Legal issue

Whether refusal to provide access constituted an abuse of dominance.

Principle

The Court adopted a strict approach to compulsory access.

The facility had to be effectively indispensable, with no real or potential alternative, and duplication had to be economically or technically impossible or unreasonably difficult.

Relevance to semantic interoperability

The Bronner principle cautions against treating every useful interoperability interface as an essential facility.

For example:

"This API would make competition easier"

is not necessarily enough.

The competition authority may need to establish much stronger facts concerning necessity and exclusionary effects, depending on the legal framework and type of conduct involved.

5. Aspen Skiing Co. v Aspen Highlands Skiing Corp., 472 U.S. 585 (1985)

Facts

Three Aspen ski mountains were owned by the defendant, while a fourth was owned by the plaintiff.

The firms had previously participated in a joint multi-area ticket system.

The defendant subsequently terminated the cooperative arrangement.

Decision

The U.S. Supreme Court upheld the monopolization finding.

The Court emphasised the unusual circumstances surrounding the termination of an established cooperative relationship and evidence that the defendant was willing to sacrifice short-term benefits in pursuing exclusionary objectives.

Relevance to interoperability

The case is important by analogy.

A dominant platform that historically permitted meaningful interoperability and then deliberately withdraws it may attract greater scrutiny than a firm that never provided interoperability at all.

Thus:

Existing interoperability → withdrawal → exclusionary effect

can be legally significant.

6. Verizon Communications Inc. v Law Offices of Curtis V. Trinko, LLP, 540 U.S. 398 (2004)

Facts

The case concerned access to telecommunications infrastructure and allegations that Verizon failed to provide adequate access to competitors.

Decision

The Supreme Court emphasised that U.S. antitrust law generally does not impose a broad duty upon monopolists to cooperate with rivals.

The Court also treated Aspen Skiing as an exceptional case and expressed caution about compelled sharing because of difficulties in identifying and administering such obligations.

Relevance to semantic interoperability

Trinko establishes an important limitation:

Competition law should not automatically become a general interoperability regulator.

Therefore, a semantic-interoperability claim under U.S. antitrust law must ordinarily demonstrate exclusionary conduct satisfying established monopolization principles rather than simply showing that interoperability would improve competition.

7. Google Android — Google LLC and Alphabet Inc. v European Commission, Case T-604/18 (2022)

Facts

The European Commission found several forms of abusive conduct concerning Google's Android ecosystem.

Among other things, Google imposed contractual restrictions concerning:

• pre-installation of Google Search and Chrome;
• Android fragmentation;
• distribution of competing services.

The Commission found that these practices restricted competition in the Android ecosystem.

General Court

The General Court substantially upheld the Commission's findings, while modifying the treatment of certain aspects and reducing the fine.

The Court's analysis also recognised that competition between mobile ecosystems must consider the interdependence between operating systems and app stores.

Relevance to semantic interoperability

Android demonstrates how interoperability and compatibility restrictions can be used at the ecosystem level.

The competition problem may arise not merely from refusing a single API but from controlling the rules governing which versions of an operating system, applications and services can interact.

VII. Comparative Significance of the Cases

VIII. Semantic Interoperability and Market Definition

Semantic interoperability can influence how the relevant market is defined.

Traditional market-definition analysis may consider:

• products;
• services;
• geographic markets;
• substitutability.

Digital ecosystems require additional attention to:

A. Platform-specific compatibility

An application designed for one operating system may not function on another.

B. Data portability

Users may technically move their data but be unable to use it elsewhere because the semantic structure is proprietary.

C. Multi-homing

Users or developers may simultaneously use multiple platforms.

However, multi-homing does not necessarily eliminate market power where the platforms are not practically substitutable for particular functions.

The CCI's Google Android investigation, for example, examined ecosystem effects and concluded that app stores associated with different operating systems were not necessarily substitutable from the perspective of app developers.

IX. Semantic Interoperability and Network Effects

The competition implications can be represented as follows:

Dominant platform

↓

Large user base

↓

Large developer/complementor base

↓

Common semantic standards

↓

Higher interoperability value

↓

Greater switching costs

↓

More users and developers attracted

↓

Further strengthening of the platform

This can create a self-reinforcing ecosystem.

Consequently, an interoperability restriction can have effects substantially larger than the immediate technical restriction.

X. Semantic Interoperability and Foreclosure

Foreclosure may occur through several techniques.

1. API degradation

A dominant platform makes its API technically available but reduces its functionality for competing products.

2. Documentation withholding

The platform does not provide sufficient technical documentation.

3. Semantic ambiguity

The platform provides data but with incomplete definitions, making the information practically unusable.

4. Selective compatibility

The platform ensures that its own products receive complete interoperability while rival products receive restricted access.

5. Version discrimination

New platform versions remain compatible with the dominant firm's products but break compatibility with rivals.

6. Certification restrictions

The dominant undertaking may make interoperability conditional upon certification requirements that are unnecessarily restrictive.

7. Data-format discrimination

The dominant platform permits export but uses proprietary schemas that competitors cannot practically interpret.

XI. Semantic Interoperability and Self-Preferencing

Semantic interoperability can also facilitate self-preferencing.

Suppose a platform controls the underlying data layer.

It could theoretically provide:

Complete semantic access to its own downstream business

while providing:

Delayed, incomplete or degraded semantic access to competitors.

This creates an information asymmetry.

The competition concern is not simply that the dominant firm possesses data.

The relevant question is whether it uses control over the interoperability layer to foreclose equally efficient competitors or restrict effective competition.

XII. Semantic Interoperability and Data Access

Modern competition cases increasingly involve data.

Important categories include:

Personal data

• identity;
• preferences;
• transaction history;
• behavioural information.

Business data

• inventory;
• logistics;
• pricing;
• customer information.

Machine-generated data

• IoT data;
• vehicle telemetry;
• industrial sensor data;
• smart-meter information.

Metadata

Metadata can be particularly important because it gives meaning to otherwise unusable data.

For example:

"42.7"

has little meaning without knowing whether it represents:

• temperature;
• voltage;
• blood pressure;
• battery state of charge;
• currency;
• distance.

Therefore:

Data portability without semantic portability may be commercially ineffective.

XIII. Semantic Interoperability and AI Competition

AI markets create a new dimension.

AI systems may rely on:

• data ontologies;
• model schemas;
• embeddings;
• APIs;
• metadata;
• identity systems;
• agent protocols;
• tool specifications.

A dominant AI ecosystem could potentially make competing AI systems less useful by restricting semantic access to important information or services.

Potential competition concerns include:

1. AI-to-AI interoperability;
2. model portability;
3. agent interoperability;
4. access to structured datasets;
5. API compatibility;
6. proprietary data schemas;
7. identity interoperability;
8. interoperability between foundation models and applications.

The competition-law analysis would still depend upon dominance, conduct, foreclosure, effects and applicable legal standards rather than the mere existence of a proprietary technology.

XIV. Semantic Interoperability in Healthcare

Healthcare provides a particularly strong example.

Suppose Hospital A uses one electronic-health-record system and Hospital B uses another.

If:

Hospital A can export the patient's records

but

Hospital B cannot understand the clinical terminology,

then nominal interoperability exists but semantic interoperability does not.

A dominant healthcare-information platform controlling a widely adopted data standard could potentially obtain substantial ecosystem advantages.

Competition authorities may therefore examine:

• interoperability;
• data portability;
• switching costs;
• exclusionary contracts;
• access to technical standards;
• discriminatory API access.

XV. Semantic Interoperability in Financial Services

Financial technology produces similar concerns.

Examples include:

• payment systems;
• open banking;
• digital wallets;
• account-information services;
• financial APIs;
• digital identity.

A dominant financial platform might restrict semantic access to account information so that competing fintech firms receive less useful information than the platform's own services.

This can make formal API access insufficient.

The competition question becomes:

Is access genuinely functionally interoperable, or merely technically available?

XVI. Competition Law Tests

A competition authority examining semantic interoperability may consider the following sequence.

Step 1 — Identify the relevant market

Determine whether the market involves:

• operating systems;
• cloud services;
• enterprise software;
• digital platforms;
• data services;
• payment services;
• healthcare software;
• AI systems.

Step 2 — Establish market power

Relevant factors may include:

• market share;
• network effects;
• switching costs;
• ecosystem control;
• data advantages;
• entry barriers;
• interoperability dependence.

Step 3 — Identify the interoperability layer

Determine what the undertaking controls:

• API;
• protocol;
• semantic schema;
• metadata;
• database;
• authentication system;
• standard.

Step 4 — Examine the conduct

Possible conduct:

• refusal;
• discriminatory access;
• degradation;
• delay;
• excessive licensing terms;
• technical restrictions;
• tying;
• exclusive interoperability.

Step 5 — Determine competitive effects

Potential effects include:

• foreclosure;
• reduced innovation;
• reduced consumer choice;
• increased switching costs;
• reduced entry;
• strengthening of dominance;
• suppression of competing ecosystems.

Step 6 — Examine justification

The undertaking may identify:

• security;
• privacy;
• cybersecurity;
• intellectual-property protection;
• system integrity;
• technical stability;
• fraud prevention.

These justifications must be examined against the actual design and proportionality of the restriction.

XVII. Interoperability vs Compulsory Access

An important distinction must be maintained.

Interoperability regulation

Requires systems to communicate effectively.

Compulsory access

Requires a dominant undertaking to provide competitors with access to a particular resource.

Competition law traditionally approaches the second more cautiously.

This distinction explains why Microsoft is particularly important: the remedy was directed toward disclosure of interoperability specifications rather than unrestricted disclosure of Microsoft's source code.

XVIII. Competition Risks Created by Poor Semantic Interoperability

Poor interoperability can generate:

1. Lock-in

Customers remain with the incumbent because migration is difficult.

2. Entry barriers

New entrants cannot obtain sufficiently useful access.

3. Innovation suppression

Competitors cannot build complementary products.

4. Ecosystem foreclosure

The dominant firm protects its downstream products.

5. Data silos

Users become dependent upon a particular provider.

6. Reduced multi-homing

Users cannot conveniently use competing platforms simultaneously.

7. Increased switching costs

Customers incur significant conversion and integration expenses.

8. Reinforcement of network effects

The dominant ecosystem becomes increasingly difficult to challenge.

XIX. Possible Competition-Law Remedies

Where unlawful exclusion is established, remedies could include:

1. Interoperability disclosure

Require publication of necessary technical specifications.

2. API access

Require reasonable access to APIs.

3. Non-discrimination

Require equivalent interoperability conditions for competitors.

4. Data portability

Require usable data export.

5. Semantic portability

Require data to be supplied in sufficiently interpretable formats.

6. Interoperability standards

Require compliance with specified open standards where legally justified.

7. Monitoring

A monitoring mechanism may supervise compliance.

The Microsoft remedy illustrates how interoperability obligations can require continuing technical documentation and reasonable, non-discriminatory access.

XX. Limits of Competition-Law Intervention

Semantic interoperability should not automatically be equated with an antitrust violation.

There are legitimate reasons for restricting interoperability, including:

• cybersecurity;
• privacy;
• intellectual-property protection;
• system integrity;
• fraud prevention;
• protection against malicious software;
• technical reliability.

Moreover, excessive compulsory interoperability may:

• reduce incentives to innovate;
• increase cybersecurity vulnerabilities;
• expose proprietary technology;
• impose substantial compliance costs;
• make technical standards rigid;
• facilitate free-riding.

The Trinko decision is particularly important for this limitation because the U.S. Supreme Court emphasised the dangers and administrative difficulties of compelling firms to share infrastructure or resources with rivals.

XXI. Semantic Interoperability and the Digital-Ecosystem Problem

The most important modern issue is that competition increasingly occurs between ecosystems rather than isolated products.

For example:

Operating system

↕

App store

↕

Applications

↕

Cloud services

↕

Identity

↕

Payment

↕

Data

A dominant firm controlling several layers can make semantic interoperability strategically important.

The competitive concern becomes greater where control over one layer allows the firm to disadvantage competitors operating at another layer.

The Google Android litigation illustrates the importance of examining competition at the ecosystem level rather than looking at individual products in isolation. The General Court specifically considered the relationship between Android and the Play Store when assessing competitive constraints.

XXII. Key Legal Principles Emerging from the Case Law

Six broad principles can be extracted.

Principle 1 — Interoperability can itself be a competition variable

Microsoft demonstrates that insufficient interoperability can restrict competition in a related market.

Principle 2 — Dominance does not automatically create a general duty to cooperate

Trinko establishes a strong U.S. limitation on compelled cooperation.

Principle 3 — Refusal to supply can be abusive in exceptional circumstances

Magill, IMS Health and Microsoft illustrate the European approach.

Principle 4 — Indispensability matters particularly in traditional essential-facility situations

Bronner remains an important reference point for strict compulsory-access analysis.

Principle 5 — Existing cooperation can matter

Aspen Skiing demonstrates why withdrawal from an established cooperative arrangement can receive particular scrutiny.

Principle 6 — Ecosystem compatibility can affect market power

Google Android demonstrates how compatibility, platform rules and ecosystem restrictions can interact with dominance and foreclosure.

XXIII. Emerging Issues

Future competition disputes are likely to concern:

1. AI-agent interoperability

Whether competing AI agents can meaningfully communicate and exchange tasks.

2. Cloud interoperability

Whether customers can migrate workloads between cloud providers.

3. Data-space interoperability

Whether competing platforms can interpret shared industrial and commercial data.

4. Connected vehicles

Whether independent service providers can understand vehicle-generated data.

5. Smart grids

Whether competing energy-management systems can interpret grid data.

6. Digital identity

Whether competing services can meaningfully authenticate and exchange identity information.

7. Healthcare interoperability

Whether competing health-information systems can understand common patient data.

8. Financial APIs

Whether competing fintech firms can obtain functionally equivalent information from banking platforms.

Conclusion

Semantic interoperability is increasingly a competition-law issue because control over the meaning, structure and usability of information can become a source of market power.

The central distinction is:

Technical interoperability asks whether systems can connect; semantic interoperability asks whether they can meaningfully understand and use what they exchange.

The leading legal framework can be understood through Magill, Bronner, IMS Health, Microsoft, Aspen Skiing, Trinko and Google Android.

Among these, Microsoft v Commission is particularly significant because the case directly recognised that withholding interoperability information from competitors could constitute an abuse of dominance where the necessary legal conditions and competitive effects were established.

For modern digital markets, therefore, competition analysis should examine not merely whether an API or data-export mechanism exists, but whether competitors receive meaningful, timely, non-discriminatory and functionally usable interoperability.

The key legal tension is between two objectives:

Preserving incentives to innovate and control proprietary technology

versus

preventing dominant control over interoperability from becoming a mechanism for exclusion and ecosystem foreclosure.