| « | July 2025 | » | | 日 | 一 | 二 | 三 | 四 | 五 | 六 | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | | | |
|
公告 |
| 暂无公告... |
| Blog信息 |
|
blog名称:Eternal Spark
日志总数:32
评论数量:49
留言数量:0
访问次数:267304
建立时间:2004年12月23日 |
| |
|
 [social network]【转载】Web 2.0 checklist 2.0
文章收藏
Spark 发表于 2005/7/23 18:32:20 |
| 转载自: http://www.sivas.com/aleene/microcontent/index.php?id=P2205
Web 2.0 checklist 2.0After my first checklist I was not quite happy. I need more details. So I upgraded my checklist to a 10-point scale. That way I have a nice rating scale. The idea is that I put a service against the checklist, check the boxes, add the number of checked boxes and voila a rating. 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.
microcontent; web2.0; [0] Comments (0 views) | [0] Trackbacks | [0] Pingbacks | Permalink |
|
|