[http://creativecommons.org/licenses/by/3.0/]
This work is licensed under a CC
Attribution 3.0 Unported License [http://creativecommons.org/licenses/by/3.0/]
It has become commonplace to praise the Web as "open" or to hear impassioned defenses of "the Open Web." But what does it mean for an information system to be open? Today we will examine some varying definitions of openness, and guest speaker Ashwin Jacob Mathew [http://www.ischool.berkeley.edu/people/students/ashwinmathew] will present some questions about issues about "openness" raised by his study of the Internet Working Protocols.Where do domain names come from? Who secures HTTPS transactions? How are IP addresses allocated? In this lecture, Ashwin will address these questions and more, exploring the infrastructure of the Internet as social and political system; just as much as it is a technical system.
At Google we believe that open systems win. They lead to more innovation, value, and freedom of choice for consumers, and a vibrant, profitable, and competitive ecosystem for businesses. Many companies will claim roughly the same thing since they know that declaring themselves to be open is both good for their brand and completely without risk. After all, in our industry there is no clear definition of what open really means. It is a Rashomon [http://en.wikipedia.org/wiki/Rashomon_effect]-like term: highly subjective and vitally important.
Jonathan Rosenberg, "The meaning of open" [http://googleblog.blogspot.com/2009/12/meaning-of-open.html], Official Google Blog, 2009
David Recordon, "What does the 'open' in 'open graph protocol' mean?" [http://groups.google.com/group/open-graph-protocol/msg/5b700e5b7e563acf?pli=1], 2010