Yes, I don't mind keeping reviewing pull requests for the future. I made a lot of comments, and inevitably some of them may have slipped through the cracks and not been fixed as part of the pull request review process or been postponed and recorded in Jira. However, I will still be a consumer of the API through both JSONLD-Java and RDF4J, so when things do stablise I plan on scheduling some time to do a full review, given I haven't been part of the day to day development so haven't been tracking everything closely for the past 18 months or so.
On 17 November 2016 at 09:36, Stian Soiland-Reyes <st...@apache.org> wrote: > Agree that many features are brand new in 0.3.0; I did not mean to imply > that 1.0.0 would be a rubber stamp copy of 0.3.0, but after sorting the > issues, like what we found during your review, for instance the RDFSyntax > as interface instead of enum, or transactions. > > Were there any of the issues from your review that we didn't record in > Jira..? > > We also need to decide if parser/writer is in or out, and if so what those > interfaces should look like. > > Would you be willing to help stabilise, perhaps towards an intermediate > 0.4.0 under Commons? Just similar reviews would be a large help! > > On 16 Nov 2016 10:25 pm, "Peter Ansell" <ansell.pe...@gmail.com> wrote: > >> Hi Stian, >> >> I personally don't think Commons RDF is ready for a 1.0.0 release. The >> APIs have still been changing recently and many of my comments on pull >> requests, both when I was an active member and recently reviewing the >> still evolving RDF4J integration, have been deferred to the future and >> they would not be easily addressed if a 1.0 release line was declared >> now. >> >> However, that isn't a reason to keep it in incubation. Good luck! >> >> Cheers, >> >> Peter >> >> On 17 November 2016 at 00:22, Stian Soiland-Reyes <st...@apache.org> >> wrote: >> > Commons RDF (incubating) has been in the Apache Incubator since 2015, >> > with an aim to graduate into the Apache Commons PMC. I think now the >> > time has come to propose such a move. >> > >> > >> > This route was agreed with the Commons PMC at the time, and we have >> > had good guidance from our mentors, including Commons PMC folks Gary >> > Gregory, Benedikt Ritter and lately myself :) >> > >> > >> > >> > >> > As noted in the 0.3.0 release today, Commons RDF aims to provide a >> > common Java API for RDF 1.1 graphs and datasets. Commons RDF 0.3.0 >> > adds API bindings for Apache Jena, Eclipse RDF4J, JSON-LD Java as well >> > as a standalone implementation. >> > >> > http://commonsrdf.incubator.apache.org/ >> > >> > >> > Now I think Commons RDF is stabilized and is ready to graduate to be a >> > component under Commons PMC where we can do a 1.0.0 release to mark >> > the spot. >> > >> > >> > (Concurrent thread on dev@commonsrdf: >> > https://lists.apache.org/thread.html/760b2d58e344e51550dcc9f6452395 >> efe72e97d3dc06169ef72f09c6@%3Cdev.commonsrdf.apache.org%3E >> > ) >> > >> > >> > I must admit that community-wise Commons RDF is not as strong as when >> > the podling started - forming a uniform API across multiple >> > implementations and use cases did mean many hard technical and >> > semantic discussions which caused some people to withdraw for a while. >> > Several has since returned as indirect contributors (e.g. code >> > review). >> > >> > >> > Now that the Commons RDF API has settled, and given that Commons has a >> > "any ASF committer have write access" policy and an open development >> > mode, I would like to propose here (and at dev@commonsrdf) that the >> > component graduate to be owned by Apache Commons PMC. >> > >> > >> > Views..? >> > >> > >> > Here's a project maturity report >> > https://github.com/apache/incubator-commonsrdf/blob/master/MATURITY.md >> > >> > >> > >> > Want to crunch some code ? Have a look at >> > >> > https://commonsrdf.incubator.apache.org/download >> > https://github.com/apache/incubator-commonsrdf/ >> > https://commonsrdf.incubator.apache.org/apidocs/ >> > >> > >> > -- >> > Stian Soiland-Reyes >> > http://orcid.org/0000-0001-9842-9718 >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
