Hi Andy
On Thu, Dec 18, 2014 at 11:12 PM, Andy Seaborne <a...@apache.org> wrote: > > I am rather surprised by the approach here. > > There are several RDF-related projects - Jena, Marmotta, Any23, Stanbol, > Clerezza and other that use RDF. > > How do they fit in? > > reto wrote: > >> Following the recent announcement and as mentioned yesterday I've started >> some steps towards commons RDF. >> > > How do those projects fit in? > > On the Clerezza list there has been support for working with > /commons-rdf/commons-rdf [1] No other project has been contacted. > > There is a community, with a significant number of participants and > significant discussion, sometimes quite intense, at > > https://github.com/commons-rdf/commons-rdf/issues > > from both ASF committers and people outside ASF. The work was communicated > to all Apache RDF-related projects from the start. > > The hope, at least my hope, has always been to bring this to Apache IF it > got some traction with users. This is stated in [2] > > There is SANDBOX-479 still open. This is a blocker to bringing code in. > > Benedikt wrote: > >> *copy pasting my answer from the other thread* >> >> We had a similar proposal a while ago [1]. Is the Clerezza RDF library >> related to this proposal? In the end the people around >> https://github.com/commons-rdf/commons-rdf decided not to bring their >> code >> to Apache Commons, because they wanted to use github for development and >> discussions. They already requested the commons-rdf git repository from >> infra, which is now unused [2]. So if you want to bring your RDF library >> to >> commons, we can use that repo, I guess... I can help you with bootstraping >> the component and bring up a website. >> > > Clerezza is unrelated to commons-rdf. Do not be fooled by the many uses > of the word "commons" :-) > > There are several RDF systems for the JVM - not all of them here at ASF. > To build community around the controversial area of RDF APIs (they have > always been controversial since day one in RDF land - much history). > > Starting from one existing project's API is a non-starter, if nothing > else, from a social perspective. Two major RDF systems go back 13 years. > > Having initial discussion on apache-commons lists was felt not to be ideal > to create community across groups not at Apache. > > As I recall, it was the details of the commons processes that was felt to > be unhelpful *initially*. Too many other things going on in the same list > for one. To engage as widely as possible, we started on github - neutral > ground. > > Benedikt wrote: > > I've created a new component for the project called "RDF" which > > you can use for RDF. When a commons component is promoted to proper we > > create an individual Jira project (this usually happens when we > > release version 1.0). > > Now we have a new endeavour here without them. It is very unfair to call > this "commons" or grab "RDF". > > The Clerezza process hast started several years ago on Apache ground to provide a generic API for RDF. In the discussions in that community it was always a topic to "go commons" at some point with this API. The choice of having a new API was based on the analysis of existing APIs like, openrdf, Jena and rdf2go. An influence had also an API that I developed while working with at HP on a graph versioning system. I don't see why clerezza would no be unfairly stealing something from the github project by starting RDF commons. The code in SVN is extracted from clerezza and I'm aligning it, as far as I think this makes sense to the proposal at github which has some good elements. > Now I see: > > rdf/trunk/src/main/java/org/apache/commons/rdf/Graph.java > ------------------------------------------------------------------------ > r1646333 | ... > > COMMONSSITE-80: renamed some classes to reflect new terms and standards of > RDf 1.1, Took some names and terms from https://github.com/commons- > rdf/commons-rdf > ------------------------------------------------------------------------ > > Please first reach out to all parties and not just copy one codebase over. > The code at github is apache licensed and I mentioned the source in the NOTICE, I don't see where the problem is. I think discussions are much better possible on the basis of a code proposal. That's what I'm working on putting some code in the sandbox. Apart from yours all reactions on the clerezza mailing lists where positive including the one from a contributor to the github-commons project. I hope that the proposal will show that an approach that also suits the needs and experience of the clerezza project is also able to satisfy the goals of the project on github. Cheers, Reto > > I apologise for not knowing more about the ethos of Apache Commons. > > Andy > > [1] > http://mail-archives.apache.org/mod_mbox/clerezza-dev/ > 201412.mbox/%3C5491AB06.9030601%40apache.org%3E > and thread > > [2] > https://github.com/commons-rdf/commons-rdf/blob/master/CONTRIBUTING.md > > [3] > https://github.com/commons-rdf/commons-rdf/issues > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
