"use cases" and "powered by" pages are indeed very interesting suggestions. assuming clerezza - after some times (hopefully not taking years) - is widely used to build semantic web applications and services, those use cases would flow into "powered by" real cases. At that time, use cases either stay as potential solutions based on clerezza or they have been realized. I support Marco's suggestions to sketch a few use cases and in particular showing why clerezza is very much suitable, but also be honest to tell its limitations (and if possible some plans to solve them).
Having said that, I wonder who would like to help writing such texts. I think we can begin with some simple text skeleton for each use case description in the use cases page(s). Suggestion: USE CASE 1: <Title> Description: xxx Key Problems: xxx Solving Them In Clerezza Way: xxx Limitations: xxx cheers, Hasan On Wed, Mar 23, 2011 at 9:47 AM, Tommaso Teofili <[email protected]>wrote: > 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 <[email protected]> > > > 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 > > >
