你眼中的web2.0？

   

 

 

What do you see in Web 2.0?

你眼中的web2.0？

 

There is an ongoing discussion on the validity of the "Web 2.0" moniker, started by Tim Bray, rejoined by Tim O'Reilly, and refined by Sam Ruby and many others. The whole discussion is fascinating not only for technical points, but for the psychological aspects. There is no hard and fast definition of "Web 2.0" and the nature of that nebulous concept allows it act like a technologist's roschach test.

 

当下正在进行一场关于Web 2.0这一名号有效性的讨论，web2.0由Tim Bray 发起，由，Tim O'Reilly进行了聚集，并由Sam Ruby 和很多的人进行了提炼。整个的讨论之所以非常令人着迷，不仅仅是因为技术方面的要点，还有心理方面的因素。并没有严格的关于web2.0的定义，这个模糊概念的本性，使她好像是一个技术专家的 Rorschach test
    [译者注：作者这里可能拼写错误，不是“roschach test”而是“Rorschach test”；Rorschach test是“罗尔沙赫氏测验(视对墨渍图案反应而分析其性格的实验）”，我从网上找到了提供这个测试的地方，谁有兴趣可以去玩玩，哈哈http://www.l8k.com.ar/blog/2.05/09/test-de-roschach.html ]

   
   

 

It's like a rorschach test

她就像罗尔沙赫氏测验

It's like a rorschach test, which let's everyone pour their own thoughts and ideas into it, forming it to how they see the world. What shouldn't be suprising is that I see the world diffently from most people. To get some perspective let's look at Sam's categorization of the three phases of the web to date:

 

她就像罗尔沙赫氏测验，这个测验通过让人们把自己的想法和观念倾诉出来，组成被测试人是如何看待这个世界的（世界观）[译者注：我发现国外有很多“罗尔沙赫氏测验”测验的版本，有兴趣的朋友可以通过上面那个链接了解一下）]如果我的世界观和大部分的人不一样请不要惊讶。为得到一些观点，让我们来看看Sam的对到目前为止的web发展阶段的分类，
   

• Web[0] is exemplified by static home pages, published in broadcast mode. Many weblogs today continue to operate in this fashion.
• Web[0] 是采取广播的方式发布的，它的典型特征就是静态主页.现在很多weblogs继续按照这种方法运营。
• Web[1] is exemplified by e-commerce shopping carts, enabling two way interaction between business and consumers. Comments and Trackbacks are in this category.
• Web[1]允许商家和用户之间的双向互动，电子商务购物车是它的典型特征。评论和引用都是这个类别的。
• Web[2] is characterized by action-at-a-distance interactions and ad hoc integration. By my putting a link here, your page rank is changed there. A book I purchase today affects Amazon's recommendations tomorrow.
• Web[2]的特点在于远距离行为的交互作用和高度集成。通过我在一个地方放一个链接，这个链接页面的等级就会改变。我今天买的一本书，就会影响亚马逊明天的推荐内容。

The One-Way Web

 

My view differs slightly. At first there was a mostly one-way web. If the communication was two-way it was strictly between one client and one server.

 

我的看法略有不同，最初，网络绝大部分都是单向的，如果交流是双向的，这种交流是被严格限制在一台服务器和一台服务器之间的。

 

Here is a picture of Web[0]. The only interaction is through web forms. This is useful for dropping comments on a site, or buying a book.

 

这里有一张关于web1.0的图片，页面窗口（网络形式）是唯一的交互，这对于在网站留言或者购买一本书，都是有效的

 

The One and a Half-Way Web

 

The next stage is more interactive, with trackbacks, pingback, and personal publishing. This diagram is also missing an arrow, one that goes from Server1 to a news aggregator. That arrow represents RSS and syndication.

 

接下来的阶段，更加注重互动，互动方法包括引用、广播和个人发布。这个图表中仍然缺少一个箭头，一个从服务器到新闻聚合器的箭头。这个箭头代表了RSS和联合技术

 

Note that all the arrows represent different formats and sometimes even different protocols. Web pages are server over HTTP, but may be uploaded to a server via FTP. Feeds are one of the many flavors of RSS. The publishing method could just as well have been WebDAV or the Blogger API. Each part of the infrastructure is different. It's like living in an old house where the plumbing is a mix of copper, steel and PVC -- every transition requires a custom fitting.

 

注意，所有箭头代表不同的形式，有时甚至是不同的协议。网页通过HTTP提供服务，但可能通过FTP上传到服务器端。Feed是RSS众多形式中的一种。发布内容的方法可以是webDAV或者Blogger接口。这个基础结构的每一部分都是不一样的。这就像住在一个老房子里，那里的管道是由铜、钢和聚氯化氢混合而成的，每一处转换导管都需要定制的配件。

 

 

The Two-Way Web

 

双向网

 

This is where we're headed.

 

这就是我们标题提到的。

 

With the rise of Atom we can start to standardize some of that plumbing. Publication can take place via the Atom Publishing Protocol, which is just a way of pushing Atom Entries up to a server. In turn those Entries can be published as an Atom Feed. Trackbacks? Those are just Atom Entries pushed over HTTP too. Same thing for comments. Now we've got Atom Entries traveling from client to the server, from server to the client, even from server to server. It's an entire Atom Entry eco-system.

 

随着Atom的出现，我们可以开始对那些管道中的一部分进行标准化。发布可以通过Atom发布协议（APP）来实现，APP就是一种把Atom Entries push 到服务器的一种方法。之后，这些Entries作为Atom Feed可以被发布。引用通告（Trackbacks）这些也是通过http协议发布的Atom Entries 。对于评论（注释）来说同样如此。现在，我们明白了Atom Entries的传递过程：从客户端到服务器端，从服务器端到客户端，甚至于从服务器端到服务器端。这就是Atom Entry整个的生态系统。

 

[译者注：Trackbacks，目前国内理解程度不一，我觉得有一篇文章，大家有兴趣可以看一下，就知道怎么回事情了：http://www.williamlong.info/archives/547.html ]

 

 

But with a standard publication mechanism like the Atom Publishing Protocol you can be sure more than just blog entries are going to published. For example, look at the early implementations of the TypePad Atom API, there's publication points for music, books, and people. You can also be sure that blogging clients  will be built into many places, the most obvious is the browser itself. It's perfectly reasonable to build an APP client in JavaScript that runs inside a Greasemonkey script.

 

不过，通过像Atom 发布协议这样的标准发布机制，你所能知道的要比即将发布的blog词条更多。比如，TypePad早期实现的Atom接口，那里可以为音乐、书籍和人发布内容。你能并且肯定的是，blog客户端将被植入很多地方，最明显的莫过于浏览器本身。使用javascript构建APP客户端是非常理想的，JavaScript是运行在Greasemonkey的脚本。

 

[译者注：Greasemonkey script. 不是很了解，大家自己上网查一下吧，：]

 

When blogging isn't blogging any more.

 

当发布时不再是发布

 

A Greasemonkey script that can publish Atom Entries.

 

Greasemonkey 脚本可以发布Atom Entries

 

Now we're talking real power. How about a script that blogs books to your book blog everytime you visit Amazon? Or how about one that finds links to FOAF files on web pages your browsing and then blogs that information to your people blog? How about mining microformat information, a Greasemonkey script could find all the Calendar information in all the web pages you visit, or cull them from entries on Bloglines, and publish them to your calendar blog. The possibilities are endless.

 

现在，该讨论核心了。你每次访问亚马逊后，都可以发布书籍信息到你的书籍blog上的脚本怎么样？或者，可以在你浏览的网络页面里面发现连接到FOAF文件的信息并发布这些信息到你的人员blog的脚本怎么样？挖掘微格式信息，Greasemonkey脚本，能够在你浏览过的网络页面里发现所有日程信息，或者从Bloglines里面的词条里进行筛选，并发筛选出的信息到你的日常blog上，这样的Greasemonkey脚本怎么样？ 这些可能是无止境的。

 

How do you know a technology has matured? When it becomes invisible. Look at all the blogging that's taking place in the above scenarios. Look at how much of it could be automatic, easy, almost invisible.

 

你对技术的成熟期了解多少？当它变得不可见时，去看看在上面所说的场景里面所进行的blog发布吧，去看看它是多么的简单、自动，并且几乎不可见。

 

Stigmergy

 

群发建造

 

Now let's loop back to something I wrote two and a half years ago, Stigmergy and the World-Wide Web. Stigmergy, a term coined by French biologist Pierre-Paul Grasse is 'interaction through the environment'. In that essay I outlined all the ways in which the web acted like a stigmeric communication system for people. In the Atom Powered Web 2.0, that vision doesn't change, the same principles apply, it's just that with standard plumbing the trails are laid down even faster.

 

现在，让我们回到我两年半之前写的一些东西，Stigmergy and the World-Wide Web.Stigmergy,一个由法国生物学家Pierre-Paul Grasse所发明的词汇，意思是“通过环境交互作用”。在那篇论文中，我概述了所有方式，这些方式使互联网就像一个Stigmeric交流系统一样为人们服务。在Atom构建的web2.0中，这个远景并没有改变，相同的规则在使用，it's just that with standard plumbing the trails are laid down even faster.（不知道该如何翻译，：（）

 

If you think I'm pushing the envelope with what can be done with Atom and the APP I'll again point to Adam Bosworth's "Database Requirements in the Age of Scalable Services" [via lesscode.org].