Interview with Tim Berners-Lee | Harry Halpin and Alexandre Monnin, Chapter 12 of their "Philosophical Engineering" book
Republication of interview in 2010.
Explanation of the term "Philosophical Engineering":
when you study and take exams in physics at Oxford, formally the subject is actually not physics but experimental philosophy. I thought that was quite an interesting way of thinking about physics, a kind of philosophy that one does by “dropping things and seeing if they continue to drop”—in other words, “thinking about the stuff you do by dropping things.” (182)
Philosophical engineering first of all refers to how protocols define a particular world for interaction:
It struck me what we ended up calling “Web Science” could have been called “philosophical engineering,” because effectively when you create a protocol you get the right to “play God” and define what words mean. You can define a philosophy, define a new world. So when people use your system—when they run the protocol—to a certain extent they have to leave their previous philosophy at the door. They have to join in and agree they will work with your system. So you can build systems—worlds—which have different properties. That’s exciting, and a source of responsibility as well.
Footnote 1: The first use of term “philosophical engineering” by Berners-Lee in a public forum was this quote: “We are not analyzing a world, we are building it. We are not experimental philosophers, we are philosophical engineers” (Berners-Lee 2003).
Berners-Lee seems to liken internet protocols with language games. Participation implies a basic agreement on the rules of the game. You do not engage in philosophical quabbles over what an HTTP header really means.
Certainly, when people write a specification, they argue about what words mean until everyone assumes that they mean in some sense the same thing. When the concepts in different people’s brains have been sufficiently well aligned and there have been enough connections between the concepts, this is written down in a language that people feel comfortable with and that they share. You can, if you want to, philosophically argue that a word is in fact ambiguous, but nobody bothers. Understand that when you play the game [of Web protocols] you’re not going to argue about that. For example, you’re not going to pay a bill online, and then afterwards come back and say “Well, I sent some HTTP3 headers off, but because they’re just HTTP headers, they don’t actually mean anything.” As a spammer said once, “It’s just a form field, I can put whatever I like there, it doesn’t have to be the person sending the e-mail.” But it does if you’re playing the game!
B-L: the missing link that would make this clear is "the relationship between 'the law of the land' and protocols." (182)
How do URIs compare to natural language?
URIs have domain names in them, and on the Semantic Web the owner of the domain is obliged to tell what everything on the domain means.
Monnin: but you can't own a philosophical name. (183)
Maybe in your world—in your philosophy—you don’t deal with names that are owned, but in the world we’re talking about, names are owned. Some people have a philosophy where they find it useful to think of a name as just a function of use, not of definition. Other people like lawyers work in worlds where the model is that there is a legal definition of a term. While meaning is use, use can be according to definition.
HH: isn't it controversial that everything can be named with an URI?
originally called these things “Universal Document Identifiers” (UDIs) even before we started using them for concepts.8 The IETF were a bit put off, thinking it was too much hubris to call them “universal.” Now I realize that I should have held firm and said “but they are,” as any alternative system of naming you can make out there, I can map it to the character set we use in URIs and I can invent a new scheme for it.
Footnote 10: Berners-Lee is referring to the transformation of URIs as “Universal Resource Identifiers” (Berners-Lee 1994) to “Uniform Resource Identifiers” (Berners-Lee, Fielding, and Masinter 2005) in the final IETF Internet standard.
Email as an example of how a protocol has both a social and technological side:
The Web Science cycle starts off with idea that the design of the Web is not just the design of one thing but the design of two things: a social and technological protocol. For example, in e-mail, there’s a general technological protocol like SMTP and there’s a social protocol. In e-mail, the social protocol that states that everyone involved is ready to run a machine that has the space to store e-mail messages while they are en route to their destination, that people will send e-mail to each other on perfectly reasonable topics, and that people will read e-mail that they receive.
You then design the microscopic, and study the macroscopic behavior that emerges:
There’s that social piece of e-mail, but then technically e-mail is actually pushed around with SMTP and pulled off with IMAP, and those pieces then together form a system. It’s a microscopic system that explains how one person sends another person an e-mail through a finite number of hops, but then you get the effects of scale. So the engineering of Web Science is not like building a mousetrap. You design a microscopic system, but what you’re interested in is the macroscopic phenomena that emerge.
And then SPAM happened! What went wrong? Well one of the social assumptions was wrong. It was too academic to assume all people are friendly and only send appropriate email that the receiver wants to read. No solution yet:
Interestingly, no one has really succeeded in redesigning either the social or the technical piece of mail to make spam go away. So there’s an example: there’s a design piece and an analysis piece, an engineering piece and a science piece, with one being done on the microscopic system and the other being done on the macroscopic system, and we’re missing a lot of the mathematics that would let us understand the connection between the two levels. (185)
What's the role of philosophy in web science?
So a lot of philosophy in the past is inapplicable. A lot of people might say that philosophy is irrelevant to daily life, but if a W3C Working Group stops and people start arguing about what things really mean—people refuse to play the game, refuse to say what terms mean, and they don’t do their job to define a protocol properly—then it’s a philosophical task to point out to them that this is important. (185)
Practical issues might warrant philosophical debates on questions of reference/representations, e.g.:
Also, philosophy may be necessary to explain what happens when the legal system hits the Web. When you make a web-page you can link to anything, you can write anything about it. But when a lawyer comes along and reserves the right to charge you to link to their page, then in a way it’s a philosophical question, as you have to tie linking to the way the protocol is defined over a name as just a reference, something that has never been controlled over the millennia. (185)
Task of philosophers:
What I would like for philosophers to do is to work diligently and to produce very nice documents that describe to people like computer scientists how things work in a simple way. What happens when you click on a link? Quite a lot of that is philosophy. (185)
So if you can produce enough discussion and understanding so that we don’t have to stop work for philosophical discussions and we can rely on philosophy being there, that would be excellent. (186)