commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <>
Subject Re: [ALL][RDF] github Commons RDF vs. Apache Commons Sandbox RDF
Date Sat, 17 Jan 2015 20:22:54 GMT
On 15 Jan 2015 11:06, "Sergio Fernández" <> wrote:

> Therefore my proposal for Commons RDF is the following:
> * Commons RDF proposes an API that addresses portability issues. I'd
recommend to start form what we currently have at github which was actually
designed by committee and both Jena and Sesame already started to implement.
> * We evolve the current design in the context of Apache Commons Sandbox
> * We keep separated the API from the implementations:
> * We keep clear the point that the major established RDF Toolkits (Apache
Jena and OpenRDF Sesame) are the recommended implementations
> * We make an open call for contributing basic implementations to the
project. We can adopt the one provided by Stian, and also work with Reto to
move the Clerezza-based implementation (aka Apache Commons Sandbox RDF) to
that API (what seems to be what he is willing to do anyway). The feedback
from those implementations would be consider for evolving the API.

+1 to all the above.

> We can easily organize in different Maven artifacts if we all agree on
this setup.

+1 - I can have a first go at this if you want, including Reto's module.

> I just want to ask about the option of having a dedicated dev mailing
list, keeping the general style for announcements or things relevant for
the whole project

Just rdf@commons should do? Its both a topic and a component.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message