Mailing-List: contact dev-help@stanbol.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stanbol.apache.org
Received-SPF: pass (athena.apache.org: domain of rupert.westenthaler@gmail.com
 designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+_sZ+hyeQH=-UZRB28PVEut0BKeK1HU1Kveu=uqKBwCr9-ofQ@mail.gmail.com>
References: 
 <CALvhUEV91BfEU1VONPbVUDDSWCRYMhAZYFq_4-SicDx4PwrY4A@mail.gmail.com>
	<CAOzb7FKio6yqdqC+gbFA_wdu=udvhAu=whdKmeHXTQVg5NPLgA@mail.gmail.com>
	<CAA7LAO3f9CagW_QYsBvRetGpJz4on-V4eoz9SkEeh+dhTzctbA@mail.gmail.com>
	<CALvhUEV2T3CWJ5mKNXgiPZ8WD30BzeVuKZZn+qT602=tUYRw=A@mail.gmail.com>
	<CAA7LAO15gW9hgbNa9LbjOTzWT3t3KrT1r-ERaGdBYUkSqT346w@mail.gmail.com>
	<CALvhUEUbEJXmaKM68NEdAWOUNpg7xB=CneT5qVhrqwFpn9XEzA@mail.gmail.com>
	<CA+_sZ+hyeQH=-UZRB28PVEut0BKeK1HU1Kveu=uqKBwCr9-ofQ@mail.gmail.com>
Date: Mon, 12 Nov 2012 00:22:59 +0100
Message-ID: 
 <CAA7LAO2X++Uk8PoNM+b9=f9v2DN5zdZLjh2BjE0MmrZCYafnZQ@mail.gmail.com>
Subject: Re: Future of Clerezza and Stanbol
From: Rupert Westenthaler <rupert.westenthaler@gmail.com>
To: clerezza-dev@incubator.apache.org, dev@stanbol.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all ,

On Sun, Nov 11, 2012 at 4:47 PM, Reto Bachmann-Gm=C3=BCr <reto@apache.org> =
wrote:
> - clerezza.rdf graudates as commons.rdf: a modular java/scala
> implementation of rdf related APIs, usable with and without OSGi

For me this immediately raises the question: Why should the Clerezza
API become commons.rdf if 90+% (just a guess) of the Java RDF stuff is
based on Jena and Sesame? Creating an Apache commons project based on
an RDF API that is only used by a very low percentage of all Java RDF
applications is not feasible. Generally I see not much room for a
commons RDF project as long as there is not a commonly agreed RDF API
for Java.

On Sun, Nov 11, 2012 at 5:40 PM, Fabian Christ
<christ.fabian@googlemail.com> wrote:
>
> Having the clerezza platform in Stanbol and thinking in the long term abo=
ut
> merging and using this stuff is a good choice. This can not be done with
> some simple imports and we should carefully evaluate what will be the rig=
ht
> way to go in Stanbol.

I would still suggest to do this within an own branch as this makes it
easier to commit/review unfinished stuff. In addition we will need a
branch for making a vote (I guess both for Clerezza and Stanbol) on
the proposed changes.

The following list tries to sum-up discussed points (please refine/complete=
)

* apache.commons.web:
    + Jersey -> Apache Wink
    + replace Viewable with LDViewable
    + Stanbol Web UI should become optional
    * add type based Rendering (at a later time)
* apache.commons.security:
    + move security from Clerezza to Stanbol
    + based on Servlet filter
* Scala: no change needed
    * TODO: observe the PermGen space issue
* Shell: no change needed
* Development Tools
    * add Bundle-Dev-Tools to shell
    * add Maven Archetype support to Stanbol
* Clerezza RDF framework:
    ? Is community strong enough to manage its own RDF framework
    ? Where to manage the code
    + SPARQL 1.1 via fast lane (direct access to the native SPARQL
implementations)
    + Update to the newest Jena versions
    + Merge Indexed in-memory TripleCollections to clerezza
    + finish and release the SingleTdbDatasetTcProvider
    + add support for JSON-LD parsing/serializing
? Clerezza Platform: Can someone make a list what else is present in Clerez=
za

best
Rupert

--=20
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstra=C3=9Fe 11                             ++43-699-11108907
| A-5500 Bischofshofen