Open Access. Powered by Scholars. Published by Universities.®

Law Commons

Open Access. Powered by Scholars. Published by Universities.®

UF Law Faculty Publications

Antitrust

Computer Law

Publication Year

Articles 1 - 2 of 2

Full-Text Articles in Law

Measuring Compliance With Compulsory Licensing Remedies In The American Microsoft Case, William H. Page, Seldon J. Childers Jan 2009

Measuring Compliance With Compulsory Licensing Remedies In The American Microsoft Case, William H. Page, Seldon J. Childers

UF Law Faculty Publications

Section III.E of the final judgments in the American Microsoft case requires Microsoft to make available to software developers certain communications protocols that Windows client operating systems use to interoperate with Microsoft's server operating systems. This provision has been by far the most difficult and costly to implement, primarily because of questions about the quality of Microsoft's documentation of the protocols. The plaintiffs' technical experts, in testing the documentation, have found numerous issues, which they have asked Microsoft to resolve. Because of accumulation of unresolved issues, the parties agreed in 2006 to extend Section III.E for up to five more …


Software Development As An Antitrust Remedy: Lessons From The Enforcement Of The Microsoft Communications Protocol Licensing Requirement, William H. Page, Seldon J. Childers Oct 2007

Software Development As An Antitrust Remedy: Lessons From The Enforcement Of The Microsoft Communications Protocol Licensing Requirement, William H. Page, Seldon J. Childers

UF Law Faculty Publications

An important provision in each of the final judgments in the government's Microsoft antitrust case requires Microsoft to "make available" to software developers the communications protocols that Windows client operating systems use to interoperate "natively" (that is, without adding software) with Microsoft server operating systems in corporate networks or over the Internet. The short-term goal of the provision is to allow developers, as licensees of the protocols, to write applications for non-Microsoft server operating systems that interoperate with Windows client computers in the same ways that applications written for Microsoft's server operating systems interoperate with Windows clients. The long-term goal …