incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Seaborne <>
Subject Modularisation
Date Thu, 02 Feb 2012 18:51:03 GMT
(discussion on jena-dev@ for all the developers)

A question to you both.  Rather that adding feature to the "core" of 
Jena, I have been wondering if the responsibility of core Jena is to 
provide the extensibility.  This has two effects:

1/ the release cycle does not hold back new features, or improvements to 
those features.

2/ It gives other people a way to add their features without having to 
delve into the core and building it.

Of course there a downside ... complexity can exposed to the application 
writer who is not interested.

Do you have any thoughts on what interfaces and astractions Jena should 
be providing?

Henry - for you, is a sync call because the contract on 
return is that it's finished.  Did you think you will provide your own 
API and way teh status of the actions are proceeding?

Martynas - what sort of control is needed for the syntaxes which aren't 
the usual RDF only data formats?


View raw message