On 09/10/11 22:26, Paolo Castagna wrote:
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(?)
- ...
There are three axes: time, resources and functionality. It's not a
free choice: choose two and the third is determined. Other limitations
may apply.
Making tiny incremental steps on too many fronts doesn't lead to real
progress.
What are the priorities for Talis and how much time&resource is Talis
prepared to contribute to each priority?
Andy
