← Back to Posts

Compete on features, not on closed standards: Mark Maxham on governance by API

Sean Roberts•November 13, 2020•3 min read

By this point in the afternoon Mark Maxham and I had spent an hour on scooters, consent decrees and antitrust, the heavy, top-down end of government. I wanted to try the other end. Could an agency like the FTC, made a bit more hands-on like the SEC, publish its requirements to Facebook and Google through APIs, the way the Open Mobility Foundation publishes a city's rules to scooter companies? It sounds a great deal better to me than breaking Facebook up.

Mark did not hedge.

I believe that governance via API is going to be one of the transformational technologies of the 21st century. And that's a big statement. It's a bold statement, especially since it's really still in its infancy.

He gave me two details I had not heard before. The rules in the Mobility Data Specification are not only caps. A city can set a minimum as well as a maximum, so a company has to keep enough scooters in a neighborhood for anyone there to rely on them. And the specification is growing past scooters to taxis, buses, robot delivery vehicles and drones. He imagines a city closing the airspace just above an elementary school to delivery drones the way it closes a street, with a published rule every operator's software can read instead of a PDF.

Then he made the point I came for. None of this is specific to scooters.

Is it very specific to scooters? Not at all. There are many, many, many opportunities for describing interfaces that are agreed upon by multiple parties, that can be published, that can be scrutinized. And the only way in my mind to minimize the risk is to put everything out where people can see it. That's not where you compete. You do not compete on proprietary standards, on closed source. You compete on features, functionality, price, mass production, whatever.

His grandmother is not going to read the code, he said, and she does not need to. What matters is a critical mass of people who can, looking for security holes and strange behavior. Then the work gets done once, in one jurisdiction, done well, and reused everywhere else. The specification started in the Los Angeles basin, with some excellent people in Santa Monica contributing, and quickly became a multi-city, multi-continent effort. It is deployed in South America and Europe now, and he has been working with a developer in Norway on yet another implementation.

Apply that to the largest platforms and the shape is clear. The rules a regulator wants followed, on data access, portability or interoperability, get written as a specification anyone can read. Compliance is checked by code that is open to inspection. The companies keep competing on everything that makes their products good. The House antitrust subcommittee recommended interoperability and data portability last month, leaving open how either would be specified or checked. This is one way it could be.

What I like about Mark's version is that it moves the fight. Today the rules for big platforms are written in lawsuits and consent decrees, and they arrive years late. A published interface can be argued over, revised and enforced at the speed of software, and nobody has to pretend the companies stop competing. He thinks the same approach fits almost every industry that touches government, and his examples are the other half of this conversation.

From Lincoln Shorts, the interview series I hosted for Lincoln Network, recorded 13 November 2020.

Share this post