Re: [VOTE] Accept Jena into the incubator

2010-11-17 Thread Reto Bachmann-Gmuer
+1 (non binding) On Wed, Nov 17, 2010 at 2:40 PM, Benson Margulies wrote: > +1 > > On Wed, Nov 17, 2010 at 8:10 AM, Ross Gardler wrote: >> Please vote on the acceptance of JENA into the incubator. The proposal can >> be found at http://wiki.apache.org/incubator/JenaProposal and is copied >> belo

Re: Clerezza, Stanbol, Jena, Semantic Commons, WDYT?

2010-11-09 Thread Reto Bachmann-Gmuer
Hi Jeremy One of Clerezza aims was to use an RDF api that is maximally close to RDF abstract syntax and semantics, on this RDF core api we have different façades and utilities as well as a frontend adapter implementing the jena API. Related standards like SPARQL and the various serialization forma

Re: FOO proposal and Clerezza

2010-11-04 Thread Reto Bachmann-Gmuer
Hi To have a better overview how the different project are supposed to be different I've started a wiki-page to compare the features: http://wiki.apache.org/incubator/SemanticComparison#preview At the current state it is in no way objective, but to me it would help to see what is most likely to

Re: FOO proposal and Clerezza

2010-11-02 Thread Reto Bachmann-Gmuer
On Mon, Nov 1, 2010 at 12:00 PM, Bertrand Delacretaz wrote: > Hi, > > On Mon, Nov 1, 2010 at 10:46 AM, Reto Bachmann-Gmuer > wrote: > > ...The goal of the FOO proposal ("a modular software stack and reusable > set of > > components for semantic content managem

FOO proposal and Clerezza

2010-11-01 Thread Reto Bachmann-Gmuer
(restarting thread with general@incubator.apache.org hoping for a broader discussion) Hello The goal of the FOO proposal ("a modular software stack and reusable set of components for semantic content management") seems quite similar to the one of Clerezza ("an OSGi-based modular application and s

Re: Third party Maven Repository Usage

2010-03-22 Thread Reto Bachmann-Gmuer
We are having the same problem in Clerezza, one of the dependencies that isn't in the central repo is sesame 2 [1]. I think we have the following options: - not include the sesame backend in the default distribution (users who need it would have to compile it their selves of download it from elsew