Persistency Storage G.U.I. Application Integration Conversation Syndication Metadirectory synching API Persistency Storage G.U.I. Application API You, me, the Friend Of A Friend, … e-mule, Amphetadesk, Groove Networks, Plone, Chandler, … ZODB, … Replication Openldap, Oracle, MySQL, distributed file systems, … Layers of communication for KM/CM « … » Browser + HTTP, … ZEO, … SQL, LDAP, … P2P, REST, XML-RPC, … RSS + HTTP LDAP, SQL, … LDAP, SQL

Brai n App code RAM HD or DB FS or DB code Internet Network code Brai n Storing Retrieving Calling Talking Answering Caching Updating Needs for bandwidth Needs for caching One key for an efficient semantic web should be solutions for synchronizing RDF repositories that could be used as caches. Building a universal model for knowledge/RDF caches be them in- brain, in-RAM, on-HD, in-DB, in-WAN, … Could we do it ? Should we do it ?

Mean Rating, Annotating, Categorizing, Classifying, Commenting, Marking, Describing, Qualifying, Targeting at sbdy = « MEANING » (as « building semantics ») UI for meaning Picking/Droping in a tree Filling a form EvaluateValidate Recommendation engine Publish/Send View Filter Browse Query Subscribe Watch Recommendation engine Workflow example for semantically enhanced KM applications

pending private published visible hide publish reject retractshow submit Plone default workflow (for CMFNewsItem as example)

pending private published visible hide publish show submit Prepare notification prepare blog entry explore visible (news item) visible (news item) visible (news item) publish published submit To read To qualify & comment To notify to someone To explore To store & forget pending (news item) archive reject retract To print & read & evaluate for action Raw news entry built from an external source by the RSS feeder Temp. entry built as a list of links found in another news Final news entry for my blog News entry to notify to someone for his/her own blog Adapted Plone workflow (for watching & blogging) CMFNewsFeed My actions