Arnaud Leene列了一個Web 2.0服務的對照表，看上去有點理想主義，但有一定的參考價值，節譯如下：

• 結構化微內容 - 一種服務應該允許對結構化微內容進行操作。這可以是數據存儲服務或數據加工服務；
• 外部數據 - 數據主要來自外部。因而一種服務主要關注的應該是處理微內容，而不是存儲微內容。這也意味著一種服務應該允許從外部獲取數據。這既可以是通過一個feed，也可以是一種導入功能。這也意味著用戶對他的數據擁有全部控制權（編輯、刪除，等等）；
• 許可 - 用戶決定每個微內容項的使用許可。這種許可可以區分私人數據、群組數據以及公開數據；
• 豐富的feed - 一種服務應該提供可供用戶訂閱的很多feed，這些feed應該以任何可能的方式融合并匹配于經過處理的微內容；
• Web API - 一種服務應該提供很多的Web API，以便將其功能整合到其他的服務中；
• 桌面集成 - 一種服務應該不只依賴于網絡，還應該與桌面進行緊密集成。比方說，可以通過微內容客戶端實現；
• 單一身份 - 一個用戶在所有他所使用的服務中無需多次創建他的身份，只有一個可以導出到其他服務的單一身份就夠了（當然可以有多個角色）；
• 微Web - 用戶應該可以在某個領域中隨意穿越微內容空間。在一個單獨的領域內，用戶可以從一個微內容項，轉到相關的其他微內容項。何為相關由用戶自己決定。就是說看到一個名字“Arnaud Leene”，就可以查閱相關的FOAF文件、blog、tag等等；
• 非預設結構 - 一種服務應該支持靈活的微內容結構。就是說這種結構不是預設的，而是由用戶決定的。

Arnaud Leene的原文如下：

I have come up with the following points:

• Structured MicroContent - a service should be able to handle structured MicroContent. This can be the data stored at the service or processed by the service;
• Data Outside - the data should be primarily outside. Thus main focus of a service should be processing MicroContent and not storing MicroContent. This also implies that the service should be able to get the outside data. This can either be by a feed (limited window) or an import function. This also implies that the user is in full control (datalibre compliant) of his data (edit, delete, etc.);
• Licenses - for each MicroContent Item the user determines the usage license. One can differentiate here between private data, i.e. data that is only for the user and thus has a very restrictive license, group data, where for each Item is determined which other user might do something with it, and public data, for which the Creative Commons licenses are valid. (remark: I might throw this one out, as it is strongly related to Data Outside);
• Feeds Galore - A service should have many feeds to which clients can subscribe. This feeds mix and match the processed MicroContent in any way imaginable. Feeds can be compound in nature and use many types of enclosures. These feeds allow for syndication of MicroContent;
• Web API's - a service should offer many Web API's, which allow their functionality to be integrated in other services;
• Desktop Integration - A service should not only live on the network, but also allow tight integration with the desktop. This can for instance be achieved with MicroContent clients.
• Single Identity - A user should not have to copy with creating identities at all services he wants to use. It should be sufficient to have a single identity (but multiple personae) that can exported to service;
• MicroWeb - the user should be able traverse MicroContent space on the field level. From a single field in a MicroContent Item, the user should be able to go to relevant other MicroContent Items. The user decides for himself what is relevant. Thus seeing a name "Arnaud Leene", he should be able to go to the relevant FOAF-file, Weblog, tags, etc;
• lowercase Structure - a service should support lowercase MicroContent structure. This implies that the structure is not set beforehand, but is determined by the user. There are no standard setting committees or services that set structure in stone;
• Placeholder - this checkpoint is a placeholder for something that I have not yet thought of, or seen on the Web;

Ok, this is checklist version 2.0. It is still a moving target. I might change some things as I experiment with applying it.