Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of castagna.lists@googlemail.com
 designates 74.125.82.43 as permitted sender)
Message-ID: <4E92116C.4090103@googlemail.com>
Date: Sun, 09 Oct 2011 22:26:04 +0100
From: Paolo Castagna <castagna.lists@googlemail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: jena-dev@incubator.apache.org
Subject: Roadmap? (Was: Re: Site: some trivial changes and a proposal to add
 "getting involved" to the horizontal navigation bar)
References: <4E90A6C4.3060508@googlemail.com>
 <4E91FD29.7080008@epimorphics.com>
In-Reply-To: <4E91FD29.7080008@epimorphics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Ian

Ian Dickinson wrote:
> On 08/10/11 20:38, Paolo Castagna wrote:
>> Hi,
>> I made some small and trivial changes to the Jena website (without
>> publishing it).
>> Feel free to change/reject any of them, if you do not agree with the
>> changes.
>>
>>
>> The page which makes me more unsatisfied is the "Jena Roadmap" (*):
> Well, since you were the main person advocating it, I assumed that you
> would fill in some content. Not quite sure how we go about creating a
> consensus roadmap though.

>From my (and Talis) point of view:

 - scalability and performance (loading and querying)
 - ease of use (Fuseki did a great job in that direction)
 - better modularity and a small Jena core module
 - ability to create and keep up to date custom indexes (a la LARQ)
 - authentication and authorization (added to Fuseki?)
 - high availability (a simple master/slave replication solution would do)
 - a good solution for "geo" and SPARQL
 - TxTDB (ongoing) not to block reads while write transactions are in progress
 - a scalable inference engine(?)
 - ...

If any of these is not self-explanatory, please, say so and I can add
more details, rationale and use cases.

But, as you say it's important to create consensus around these.

To me, consensus come from the every day needs.

We need the things listed above to operate our services (and they are
probably shared by anyone who would want to use Apache Jena in solutions
used in a production environment).

>> http://jena.staging.apache.org/jena/about_jena/roadmap.html
>> I believe it's important to give people a sense of direction.
>> The current page IMHO, perhaps, send the wrong message (i.e. no
>> direction).
> OK, but what would you say that the project's direction is?

Make Apache Jena a solid and scalable library (and server) for everyone
wanting to build (and run) solutions or services using RDF (including,
but not limited to, people and companies (who might be running businesses
with it)).

Then, on top of this, there are the everyday problems.

For example, tomorrow, I need to load 2 billion triples|quads in TDB.
How am I going to deal with that? ;-)

Paolo