Re: [DRAFT] Apache Jena report - 2021-10
+1 indeed, thanks Andy! Adam On Thu, Sep 30, 2021, 5:44 PM Bruno P. Kinoshita wrote: > +1 > Thanks! > > On Friday, 1 October 2021, 10:34:51 am NZDT, Andy Seaborne < > a...@apache.org> wrote: > > ## Description: > The mission of Jena is the creation and maintenance of software related > to Java framework for building Semantic Web applications > > ## Issues: > There are no issues requiring board attention. > > ## Membership Data: > Apache Jena was founded 2012-04-18 (9 years ago). > There are currently 18 committers and 14 PMC members in this project. > The Committer-to-PMC ratio is 9:7. > > Community changes, past quarter: > - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. > - No new committers. Last addition was Greg Albiston on 2019-07-08. > > ## Project Activity: > Jena version 4.2.0 was released 2021-09-12. It fixed CVE-2021-39239, > which was discovered by the team, and affects all version 4.1.0 and > earlier. > > The release was not just about a CVE fix. The release included a new > component, a data validation engine for the ShEx language to go > alongside the SHACL engine; and also support for reading JSON-LD 1.1 > using an external 3rd party library. JSON-LD 1.1 is used by some IOT > device and service descriptions. > > During the release checking, a problem was discovered in the OSGi bundle > related to the new dependencies for JSON-LD 1.1 handling. The project > dropped the OSGi convenience binaries, and a discussion has started > about retiring them. The development community no longer has the skills, > nor interest, necessary to maintain their production. Contact with known > downstream open source projects, and a message to users@ has not > produced any concern. > > Jena has a process for retiring modules - delete in git, record the last > git commit with the code in case some interest emerges and will maintain > the module. > > ## Community Health: > Activity seems normal. Some of the figures are slightly skewed because > one PR had 48 commits which is unusual for Jena. > > The dev@ list is also the destination of JIRA email and is otherwise > quite quiet. The speed of evolution of the project is down to developer > time. > > The users@ is active and the main support channel. >
Re: [DRAFT] Apache Jena report - 2021-10
+1 Thank you, indeed On Thu, 30 Sept 2021 at 17:44, Bruno P. Kinoshita wrote: > +1 > Thanks! > > On Friday, 1 October 2021, 10:34:51 am NZDT, Andy Seaborne < > a...@apache.org> wrote: > > ## Description: > The mission of Jena is the creation and maintenance of software related > to Java framework for building Semantic Web applications > > ## Issues: > There are no issues requiring board attention. > > ## Membership Data: > Apache Jena was founded 2012-04-18 (9 years ago). > There are currently 18 committers and 14 PMC members in this project. > The Committer-to-PMC ratio is 9:7. > > Community changes, past quarter: > - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. > - No new committers. Last addition was Greg Albiston on 2019-07-08. > > ## Project Activity: > Jena version 4.2.0 was released 2021-09-12. It fixed CVE-2021-39239, > which was discovered by the team, and affects all version 4.1.0 and > earlier. > > The release was not just about a CVE fix. The release included a new > component, a data validation engine for the ShEx language to go > alongside the SHACL engine; and also support for reading JSON-LD 1.1 > using an external 3rd party library. JSON-LD 1.1 is used by some IOT > device and service descriptions. > > During the release checking, a problem was discovered in the OSGi bundle > related to the new dependencies for JSON-LD 1.1 handling. The project > dropped the OSGi convenience binaries, and a discussion has started > about retiring them. The development community no longer has the skills, > nor interest, necessary to maintain their production. Contact with known > downstream open source projects, and a message to users@ has not > produced any concern. > > Jena has a process for retiring modules - delete in git, record the last > git commit with the code in case some interest emerges and will maintain > the module. > > ## Community Health: > Activity seems normal. Some of the figures are slightly skewed because > one PR had 48 commits which is unusual for Jena. > > The dev@ list is also the destination of JIRA email and is otherwise > quite quiet. The speed of evolution of the project is down to developer > time. > > The users@ is active and the main support channel. >
Re: [DRAFT] Apache Jena report - 2021-10
+1 Thanks! On Friday, 1 October 2021, 10:34:51 am NZDT, Andy Seaborne wrote: ## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Jena was founded 2012-04-18 (9 years ago). There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. - No new committers. Last addition was Greg Albiston on 2019-07-08. ## Project Activity: Jena version 4.2.0 was released 2021-09-12. It fixed CVE-2021-39239, which was discovered by the team, and affects all version 4.1.0 and earlier. The release was not just about a CVE fix. The release included a new component, a data validation engine for the ShEx language to go alongside the SHACL engine; and also support for reading JSON-LD 1.1 using an external 3rd party library. JSON-LD 1.1 is used by some IOT device and service descriptions. During the release checking, a problem was discovered in the OSGi bundle related to the new dependencies for JSON-LD 1.1 handling. The project dropped the OSGi convenience binaries, and a discussion has started about retiring them. The development community no longer has the skills, nor interest, necessary to maintain their production. Contact with known downstream open source projects, and a message to users@ has not produced any concern. Jena has a process for retiring modules - delete in git, record the last git commit with the code in case some interest emerges and will maintain the module. ## Community Health: Activity seems normal. Some of the figures are slightly skewed because one PR had 48 commits which is unusual for Jena. The dev@ list is also the destination of JIRA email and is otherwise quite quiet. The speed of evolution of the project is down to developer time. The users@ is active and the main support channel.
[DRAFT] Apache Jena report - 2021-10
## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Issues: There are no issues requiring board attention. ## Membership Data: Apache Jena was founded 2012-04-18 (9 years ago). There are currently 18 committers and 14 PMC members in this project. The Committer-to-PMC ratio is 9:7. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. - No new committers. Last addition was Greg Albiston on 2019-07-08. ## Project Activity: Jena version 4.2.0 was released 2021-09-12. It fixed CVE-2021-39239, which was discovered by the team, and affects all version 4.1.0 and earlier. The release was not just about a CVE fix. The release included a new component, a data validation engine for the ShEx language to go alongside the SHACL engine; and also support for reading JSON-LD 1.1 using an external 3rd party library. JSON-LD 1.1 is used by some IOT device and service descriptions. During the release checking, a problem was discovered in the OSGi bundle related to the new dependencies for JSON-LD 1.1 handling. The project dropped the OSGi convenience binaries, and a discussion has started about retiring them. The development community no longer has the skills, nor interest, necessary to maintain their production. Contact with known downstream open source projects, and a message to users@ has not produced any concern. Jena has a process for retiring modules - delete in git, record the last git commit with the code in case some interest emerges and will maintain the module. ## Community Health: Activity seems normal. Some of the figures are slightly skewed because one PR had 48 commits which is unusual for Jena. The dev@ list is also the destination of JIRA email and is otherwise quite quiet. The speed of evolution of the project is down to developer time. The users@ is active and the main support channel.
[jira] [Resolved] (JENA-2172) WantPropertyElement.rdf_n() is not thread-safe
[ https://issues.apache.org/jira/browse/JENA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-2172. - Fix Version/s: Jena 4.3.0 Resolution: Fixed > WantPropertyElement.rdf_n() is not thread-safe > -- > > Key: JENA-2172 > URL: https://issues.apache.org/jira/browse/JENA-2172 > Project: Apache Jena > Issue Type: Bug > Components: RDF/XML >Affects Versions: Jena 2.7.4, Jena 4.2.0 >Reporter: ian green >Assignee: Andy Seaborne >Priority: Minor > Fix For: Jena 4.3.0 > > > In 2.7.4, concurrent calls to Model.read (on RDF/XML) are occasionally > corrupting internal parser state which results in NPE. This corruption is > sticky - all subsequent RDF/XML parsing (at least via Model.read) is > potentially affected. > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement._rdf_n can be left with > null elements when multiple threads race to expand the array. One > consequence of such null elements is that WantPropertyElement.predicate can > be null, causing a NullPointerException when toObject() is called. > This was discovered in 2.7.4, but the same code is present in > org.apache.jena.rdfxml.xmlinput.states.WantPropertyElement. (I don't know > the role that code plays in the latest Jena versions, so this issue may not > be manifest in main.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JENA-2167) Provide an RDF Binary format using Protobuf
[ https://issues.apache.org/jira/browse/JENA-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422953#comment-17422953 ] ASF subversion and git services commented on JENA-2167: --- Commit 0c0a509e3b0f5f636306275ef2b7ab273e99e1fc in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=0c0a509 ] Merge pull request #1079 from afs/fixes JENA-2172, JENA-2167 and small improvements. > Provide an RDF Binary format using Protobuf > --- > > Key: JENA-2167 > URL: https://issues.apache.org/jira/browse/JENA-2167 > Project: Apache Jena > Issue Type: New Feature >Affects Versions: Jena 4.2.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 4.3.0 > > > To go along side the RDF Thrift encoding. > Sometimes, apps want protobuf encoded RDF, e.g. for use with gRPC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JENA-2167) Provide an RDF Binary format using Protobuf
[ https://issues.apache.org/jira/browse/JENA-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422951#comment-17422951 ] ASF subversion and git services commented on JENA-2167: --- Commit 2071508862313ab58296ef405f6ecc55ab0ba0a1 in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=2071508 ] JENA-2167: Flush output > Provide an RDF Binary format using Protobuf > --- > > Key: JENA-2167 > URL: https://issues.apache.org/jira/browse/JENA-2167 > Project: Apache Jena > Issue Type: New Feature >Affects Versions: Jena 4.2.0 >Reporter: Andy Seaborne >Assignee: Andy Seaborne >Priority: Major > Fix For: Jena 4.3.0 > > > To go along side the RDF Thrift encoding. > Sometimes, apps want protobuf encoded RDF, e.g. for use with gRPC. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JENA-2172) WantPropertyElement.rdf_n() is not thread-safe
[ https://issues.apache.org/jira/browse/JENA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422952#comment-17422952 ] ASF subversion and git services commented on JENA-2172: --- Commit 0c0a509e3b0f5f636306275ef2b7ab273e99e1fc in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=0c0a509 ] Merge pull request #1079 from afs/fixes JENA-2172, JENA-2167 and small improvements. > WantPropertyElement.rdf_n() is not thread-safe > -- > > Key: JENA-2172 > URL: https://issues.apache.org/jira/browse/JENA-2172 > Project: Apache Jena > Issue Type: Bug > Components: RDF/XML >Affects Versions: Jena 2.7.4, Jena 4.2.0 >Reporter: ian green >Assignee: Andy Seaborne >Priority: Minor > > In 2.7.4, concurrent calls to Model.read (on RDF/XML) are occasionally > corrupting internal parser state which results in NPE. This corruption is > sticky - all subsequent RDF/XML parsing (at least via Model.read) is > potentially affected. > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement._rdf_n can be left with > null elements when multiple threads race to expand the array. One > consequence of such null elements is that WantPropertyElement.predicate can > be null, causing a NullPointerException when toObject() is called. > This was discovered in 2.7.4, but the same code is present in > org.apache.jena.rdfxml.xmlinput.states.WantPropertyElement. (I don't know > the role that code plays in the latest Jena versions, so this issue may not > be manifest in main.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JENA-2172) WantPropertyElement.rdf_n() is not thread-safe
[ https://issues.apache.org/jira/browse/JENA-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17422950#comment-17422950 ] ASF subversion and git services commented on JENA-2172: --- Commit fd37039ca3c6ca7073bcb0e0dfef3a8b69302c1f in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=fd37039 ] JENA-2172: Thread-safe WantPropertyElement.rdf_n > WantPropertyElement.rdf_n() is not thread-safe > -- > > Key: JENA-2172 > URL: https://issues.apache.org/jira/browse/JENA-2172 > Project: Apache Jena > Issue Type: Bug > Components: RDF/XML >Affects Versions: Jena 2.7.4, Jena 4.2.0 >Reporter: ian green >Assignee: Andy Seaborne >Priority: Minor > > In 2.7.4, concurrent calls to Model.read (on RDF/XML) are occasionally > corrupting internal parser state which results in NPE. This corruption is > sticky - all subsequent RDF/XML parsing (at least via Model.read) is > potentially affected. > com.hp.hpl.jena.rdf.arp.states.WantPropertyElement._rdf_n can be left with > null elements when multiple threads race to expand the array. One > consequence of such null elements is that WantPropertyElement.predicate can > be null, causing a NullPointerException when toObject() is called. > This was discovered in 2.7.4, but the same code is present in > org.apache.jena.rdfxml.xmlinput.states.WantPropertyElement. (I don't know > the role that code plays in the latest Jena versions, so this issue may not > be manifest in main.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
