commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Ansell <>
Subject Re: [COMMONSRDF] GroupID for incubation releases
Date Mon, 30 Mar 2015 21:53:47 GMT
On 30 March 2015 at 23:45, Reto Gmür <> wrote:
> Hi all,
> The clerezza commons RDF proposal that was in the sandbox and is now in the
> clerezza-rdf-core repository has been changed to use
> org.apache.clerezza.commons-rdf.
> As you know if all goes well clerezza will be based in the result of the
> incubating project. If however this project should unfortunately not lead
> to something generic enough to be used for interfacing arbitrary data as
> RDF and thus be usable for clerezza, then clerezza might reactivate its
> commons-rdf proposal. It would then be up to commons to decide which
> proposal to adopt and under which name.

The project is not designed with "interfacing arbitrary data as RDF"
in mind, so it is unlikely it will suit Clerezza if that is what you
are aiming for Clerezza Commons RDF to do for its internal purposes.
It is aimed at representing the RDF-1.1 Abstract Data Model using Java
interfaces. Designing around interfaces should theoretically be the
lowest common denominator for attaching to any existing project, and
it isn't clear why it wouldn't work for you. Also keep in mind that we
are not expecting any project to internally rely on the API we are
providing here. The main goal is interoperability at the external
facing parts of each implementation, not changing the core models that
each implementation uses internally.

What exactly do you mean by "reactivate" the clerezza commons-rdf
proposal? All that happened previously was that you followed the
Commons suggestion for any Apache committer to unilaterally add
modules arbitrarily to Apache Commons. There was, and is, no bilateral
support for your actions and threatening to propose an alternative,

> Till then I would prefer this project to use a group ID outside
> org.apache.commons.

We should probably resolve this now. There is no point to changing the
group ID in the future and Reto has threatened an alternative (again)
to support the proposal to not have this project use the standard


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message