Return-Path: Delivered-To: apmail-incubator-clerezza-dev-archive@minotaur.apache.org Received: (qmail 80175 invoked from network); 23 Mar 2011 08:48:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Mar 2011 08:48:51 -0000 Received: (qmail 97411 invoked by uid 500); 23 Mar 2011 08:48:51 -0000 Delivered-To: apmail-incubator-clerezza-dev-archive@incubator.apache.org Received: (qmail 97383 invoked by uid 500); 23 Mar 2011 08:48:51 -0000 Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: clerezza-dev@incubator.apache.org Delivered-To: mailing list clerezza-dev@incubator.apache.org Received: (qmail 97375 invoked by uid 99); 23 Mar 2011 08:48:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 08:48:51 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tommaso.teofili@gmail.com designates 209.85.218.47 as permitted sender) Received: from [209.85.218.47] (HELO mail-yi0-f47.google.com) (209.85.218.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Mar 2011 08:48:45 +0000 Received: by yia13 with SMTP id 13so3246750yia.6 for ; Wed, 23 Mar 2011 01:48:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Ip8XdEZJ6S7vvgAeAAF2peHl/n2/q237Xy0R+h+RslE=; b=D621yFDM1y/Ovw0sg1CjT5Zq591QRvIGNiywGxL3A+Jrnfe28NllklAhbvZQc+YsPQ Jy9oZ4HKJeu2Cbm3gEkgczjwN1VdOY/Gft1UDFnK9sEHiZZM2K8fRkUJ7dGO4MOWgn/J 2FvipV8+DqXThoG5foHdi5CKMuL8ghjQKWuvs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=gqMM5Snw0V6T0DNj8JK3+h7MK2ru+Cq6yqP+K+jqYnkkzz4LEAvNtlC93pEZ0DNEqO SwtVeMRRvZ+8d2aHutD/V77PimwYUrP90+9LnKDOWg3XV619/EteN9sG+on9oZkevkly P3Nxko/PS31dX/n5FGe7hRF/ECiF+QxlVs1IQ= Received: by 10.150.251.21 with SMTP id y21mr6296426ybh.273.1300870104147; Wed, 23 Mar 2011 01:48:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.147.35.14 with HTTP; Wed, 23 Mar 2011 01:47:44 -0700 (PDT) In-Reply-To: <5863FB4055D90542A7A7DAE0CEF2ACB0064F9D3AC6@E2K7CCR1.netvigour.com> References: <63349C4A-3387-42E2-87B2-631758702F57@bblfish.net> <5863FB4055D90542A7A7DAE0CEF2ACB0064F9D3AC6@E2K7CCR1.netvigour.com> From: Tommaso Teofili Date: Wed, 23 Mar 2011 09:47:44 +0100 Message-ID: Subject: Re: Website Apache Clerezza To: clerezza-dev@incubator.apache.org Cc: Marco Zaugg Content-Type: multipart/alternative; boundary=000e0cd6cf1a74ea41049f226cc1 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd6cf1a74ea41049f226cc1 Content-Type: text/plain; charset=ISO-8859-1 Hi all, I think one more thing could be to add a "Powered by" page which counts known solutions/platforms which rely on Apache Clerezza (i.e. Trialox CMS), that can be useful for people to try to understand what kind of product/application one can end up with using Clerezza. This is more pragmatic than the "use cases" page and I'd keep both as they respond to different concerns. Regards, Tommaso 2011/3/23 Marco Zaugg > Hi Henry et all > > Use cases are definitely needed, not only for the devs but also for > decision makers and IT professionals. > > IMO the use case you described ergo 'the decentralised Social Network' is > just one > of many. There are many other cases, some of them are: > > - Enterprise Content Classification: decentralized storing and linking of > entities and data, i.e. WWF (Worldwide Fund for Nature) with more than 50 > national and programme offices to share and find content across the network > > - Open Platforms for media companies and other content-centric companies > and organizations, i.e. The Guardian Open Platform (not done with Clerezza > though) > > - (Web) Content Management Systems such as the Trialox Web Content > Management System > > - Media monitoring: aggregate data feeds, annotate data and prioritize > content based on user behaviour, i.e. Read it Later, Instapaper (not done > with Clerezza) -> getunik/Trialox build a similar system though > > > In addition, the documentation should contain answers to the questions why > not building this type of systems with other platforms such as RoR, Spring, > Sling etc. Although this one is rather difficult as you can indeed build it > on other systems too, it should focus on the advantages using semweb > technologies. But should also talk about the disadvantages of them. > > My 2 cents. > Marco > --000e0cd6cf1a74ea41049f226cc1--