[REPORT] Apache Jena Sept 2019

[Andy Seaborne]

New ASF reporter.apache.org helper to produce reports.

It encourages more than a few basic numbers in the "Project Activity" 
and "Community Health" sections.  So if you can think of ways/metrics we 
can regular report on the state of the project, please suggest them.


I tried to extract the stats:
https://reporter.apache.org/wizard/statistics?jena

but its a fancy app and cut&paste or print of the the graphs doesn't work.

Plain text, no graphs:

dev@jena.apache.org had a 5% decrease in traffic in the past quarter 
(544 emails compared to 567)


us...@jena.apache.org had a 30% increase in traffic in the past quarter 
(304 emails compared to 233)


JIRA activity:
37 issues opened in JIRA, past quarter (23% increase)
27 issues closed in JIRA, past quarter (-10% decrease)

Commit activity:
62 commits in the past quarter (-52% decrease)
10 code contributors in the past quarter (11% increase)

GitHub PR activity:
34 PRs opened on GitHub, past quarter (13% increase)
32 PRs closed on GitHub, past quarter (no change)

Andy


## 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 (7 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.
- Greg Albiston was added as committer on 2019-07-08

## Project Activity:

Jena 3.13.0 was released on 2019-09-28.

The release had some minor issues and the project hopes to release a 
follow-up 3.13.1 quite soon.


## Community Health:

This release was 4 months after the previous one.  The project aims for 
3-4 months so this was at the longer end. The 3-4 month is clock-tick is

aspiration rather than resourced plan.

The project mailing lists are at normal levels, and users@ is getting 
some more answers to questions from other users, not just the main 
developers. StackOverflow is the main place for basic questions.

[GitHub] [jena] afs merged pull request #613: Improve some comments

[GitBox]

afs merged pull request #613: Improve some comments
URL: https://github.com/apache/jena/pull/613
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] afs merged pull request #614: Compatibility

[GitBox]

afs merged pull request #614: Compatibility
URL: https://github.com/apache/jena/pull/614
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] afs commented on issue #611: JENA-1761: General option setting for RDFParser and RDFWriter

[GitBox]

afs commented on issue #611: JENA-1761: General option setting for RDFParser 
and RDFWriter
URL: https://github.com/apache/jena/pull/611#issuecomment-536959773
 
 
   I'll hold back from merging this until after 3.13.1.  It is a functionality 
change.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [jena] afs merged pull request #615: JENA-1766: Fuseki Web interface endpoint fix

[GitBox]

afs merged pull request #615: JENA-1766:  Fuseki Web interface endpoint fix
URL: https://github.com/apache/jena/pull/615
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (JENA-1766) Fuseki Web interface endpoint mechanism not working

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JENA-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941694#comment-16941694
 ] 

ASF subversion and git services commented on JENA-1766:
---

Commit d22a673432db919d72401efc9f546e67be1a611d in jena's branch 
refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=d22a673 ]

Merge pull request #615 from afs/jena1766-ep_names

JENA-1766:  Fuseki Web interface endpoint fix

> Fuseki Web interface endpoint mechanism not working
> ---
>
> Key: JENA-1766
> URL: https://issues.apache.org/jira/browse/JENA-1766
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.13.0
>Reporter: Elie Roux
>Priority: Major
> Attachments: core.ttl
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Using the new 3.13.0 Fuseki, I'm getting a bug in the web interface, the 
> "SPARQL ENDPOINT" is empty in the query interface.
>  
> After a bit of debugging, I believe this is due to a difference returned by 
> {{/fuseki/$/server}}: it used to return non-lower case values for 
> {{srv.type}}, for instance with Fuseki 3.12.0:
> {noformat}
> {
> "version" : "3.13.0-SNAPSHOT" ,
> "built" : "2019-07-17T09:12:45+" ,
> "startDateTime" : "2019-09-27T16:18:34.271+00:00" ,
> "uptime" : 163057 ,
>     "datasets" : [
>   {
>     "ds.name" : "/corerw" ,
>     "ds.state" : true ,
>         "ds.services" : [
> {
>    "srv.type" : "GSP_RW" ,
>    "srv.description" : "Graph Store Protocol" ,
>    "srv.endpoints" : [ "data" ]
>    } ,
>    {
>    "srv.type" : "Upload" ,
>    "srv.description" : "File Upload" ,
>   "srv.endpoints" : [ "upload" ]
>    } ,
>          {
>   "srv.type" : "Query" ,
>   "srv.description" : "SPARQL Query" ,
>   "srv.endpoints" : [ "query" ]
>    } ,
>        {
>   "srv.type" : "Update" ,
>   "srv.description" : "SPARQL Update" ,
>   "srv.endpoints" : [ "update" ]
>        }
>  ]
>     }
>   ]
>  }
> }
> {noformat}
> While with Fuseki 3.13.0, with an equivalent configuration, the returned json 
> is:
>  
> {noformat}
>   "version" : "3.13.0" ,
>   "built" : "2019-09-25T15:01:44+" ,
>   "startDateTime" : "2019-09-29T12:46:11.353+00:00" ,
>   "uptime" : 3025 ,
>   "datasets" : [
>     {
>   "ds.name" : "/corerw" ,
>   "ds.state" : true ,
>       "ds.services" : [
>         {
>   "srv.type" : "gsp-rw" ,
>           "srv.description" : "Graph Store Protocol" ,
>           "srv.endpoints" : [ "data" ]
>         } ,
>        {
>           "srv.type" : "query" ,
>           "srv.description" : "SPARQL Query" ,
>           "srv.endpoints" : [ "query" ]
>         } ,
>        {
>           "srv.type" : "update" ,
>           "srv.description" : "SPARQL Update" ,
>           "srv.endpoints" : [ "update" ]
>         } ,
>        {
>           "srv.type" : "upload" ,
>           "srv.description" : "File Upload" ,
>           "srv.endpoints" : [ "upload" ]
>         {
>       ]
>    }
>   ]
> }
> {noformat}
> where srv.type is all lower-case. This doesn't play well with the JavaScript 
> code that compared against non-lowercase values, see for instance
>  
> [https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-webapp/src/main/webapp/js/app/models/dataset.js#L122]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1766) Fuseki Web interface endpoint mechanism not working

[Andy Seaborne (Jira)]

 [ 
https://issues.apache.org/jira/browse/JENA-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1766.
-
Fix Version/s: 3.13.1
 Assignee: Andy Seaborne
   Resolution: Fixed

This involves changes on the JavaScript side as well so any testing of 
development builds would be greatly appreciated.

> Fuseki Web interface endpoint mechanism not working
> ---
>
> Key: JENA-1766
> URL: https://issues.apache.org/jira/browse/JENA-1766
> Project: Apache Jena
>  Issue Type: Bug
>  Components: Fuseki
>Affects Versions: Jena 3.13.0
>Reporter: Elie Roux
>Assignee: Andy Seaborne
>Priority: Major
> Fix For: 3.13.1
>
> Attachments: core.ttl
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Using the new 3.13.0 Fuseki, I'm getting a bug in the web interface, the 
> "SPARQL ENDPOINT" is empty in the query interface.
>  
> After a bit of debugging, I believe this is due to a difference returned by 
> {{/fuseki/$/server}}: it used to return non-lower case values for 
> {{srv.type}}, for instance with Fuseki 3.12.0:
> {noformat}
> {
> "version" : "3.13.0-SNAPSHOT" ,
> "built" : "2019-07-17T09:12:45+" ,
> "startDateTime" : "2019-09-27T16:18:34.271+00:00" ,
> "uptime" : 163057 ,
>     "datasets" : [
>   {
>     "ds.name" : "/corerw" ,
>     "ds.state" : true ,
>         "ds.services" : [
> {
>    "srv.type" : "GSP_RW" ,
>    "srv.description" : "Graph Store Protocol" ,
>    "srv.endpoints" : [ "data" ]
>    } ,
>    {
>    "srv.type" : "Upload" ,
>    "srv.description" : "File Upload" ,
>   "srv.endpoints" : [ "upload" ]
>    } ,
>          {
>   "srv.type" : "Query" ,
>   "srv.description" : "SPARQL Query" ,
>   "srv.endpoints" : [ "query" ]
>    } ,
>        {
>   "srv.type" : "Update" ,
>   "srv.description" : "SPARQL Update" ,
>   "srv.endpoints" : [ "update" ]
>        }
>  ]
>     }
>   ]
>  }
> }
> {noformat}
> While with Fuseki 3.13.0, with an equivalent configuration, the returned json 
> is:
>  
> {noformat}
>   "version" : "3.13.0" ,
>   "built" : "2019-09-25T15:01:44+" ,
>   "startDateTime" : "2019-09-29T12:46:11.353+00:00" ,
>   "uptime" : 3025 ,
>   "datasets" : [
>     {
>   "ds.name" : "/corerw" ,
>   "ds.state" : true ,
>       "ds.services" : [
>         {
>   "srv.type" : "gsp-rw" ,
>           "srv.description" : "Graph Store Protocol" ,
>           "srv.endpoints" : [ "data" ]
>         } ,
>        {
>           "srv.type" : "query" ,
>           "srv.description" : "SPARQL Query" ,
>           "srv.endpoints" : [ "query" ]
>         } ,
>        {
>           "srv.type" : "update" ,
>           "srv.description" : "SPARQL Update" ,
>           "srv.endpoints" : [ "update" ]
>         } ,
>        {
>           "srv.type" : "upload" ,
>           "srv.description" : "File Upload" ,
>           "srv.endpoints" : [ "upload" ]
>         {
>       ]
>    }
>   ]
> }
> {noformat}
> where srv.type is all lower-case. This doesn't play well with the JavaScript 
> code that compared against non-lowercase values, see for instance
>  
> [https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-webapp/src/main/webapp/js/app/models/dataset.js#L122]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (JENA-909) Create Docker launcher for Fuseki

[Rob Vesse (Jira)]

[ 
https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941711#comment-16941711
 ] 

Rob Vesse commented on JENA-909:


+1 to Claude's point, we're currently using various Maven plugins to build 
Docker images as part of a larger Maven built project.  We put the relevant 
plugins and modules inside a profile so developers opt-in to building the 
Docker artifacts:

* https://github.com/spotify/dockerfile-maven - for doing builds
* https://github.com/fabric8io/docker-maven-plugin - for exporting the images 
as tarballs which is needed for some aspects of our CI/CD pipeline

> Create Docker launcher for Fuseki
> -
>
> Key: JENA-909
> URL: https://issues.apache.org/jira/browse/JENA-909
> Project: Apache Jena
>  Issue Type: Improvement
>  Components: Fuseki
>Reporter: Andy Seaborne
>Priority: Major
>
> Provide a Docker launcher and setup documentation for  Fuseki2.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (JENA-1767) Enable clear out of all TDB1 location-related state.

[Andy Seaborne (Jira)]

Andy Seaborne created JENA-1767:
---

 Summary: Enable clear out of all TDB1 location-related state.
 Key: JENA-1767
 URL: https://issues.apache.org/jira/browse/JENA-1767
 Project: Apache Jena
  Issue Type: Bug
  Components: TDB
Reporter: Andy Seaborne
Assignee: Andy Seaborne
 Fix For: 3.13.1


Jena 3.13.0 TDB1 has caching of DatasetGraphTransaction in TDBMaker (so the 
same transactional object is used at all times for a given location)

Previous, the only retained objects were StoreConnections in its cache.

Tests need to expel all location state.

Existing tests call StoreConnection.expel so this needs to flush the TDBMaker 
cache. At the same time (without risk of recusion)

It would be better to have a TDBInternal operation that controls all this but 
still retain teh call of StoreConnection.expel.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (JENA-1764) Fix missing and duplicate Automatic-Module-Name metadata

[Andy Seaborne (Jira)]

 [ 
https://issues.apache.org/jira/browse/JENA-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne resolved JENA-1764.
-
Fix Version/s: 3.13.1
   Resolution: Fixed

> Fix missing and duplicate Automatic-Module-Name metadata
> 
>
> Key: JENA-1764
> URL: https://issues.apache.org/jira/browse/JENA-1764
> Project: Apache Jena
>  Issue Type: Bug
>Affects Versions: Jena 3.12.0
> Environment: Using Jena on Java11 when Jena artifacts are on the 
> module path (rather than the class path)
>Reporter: Aaron Coburn
>Assignee: Aaron Coburn
>Priority: Major
> Fix For: 3.13.1
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The Java9+ module system makes use of the MANIFEST header: 
> Automatic-Module-Name. This header is optional, but if present it needs to be 
> globally unique and must follow certain formatting rules (e.g. no hyphens).
> The Automatic-Module-Name header in the jena-dboe-storage artifact is empty 
> (not missing), which is invalid.
> In addition, the various jena-elephas-* and jena-jdbc-* artifacts contain 
> duplicate module name declarations
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena] afs opened a new pull request #616: JENA-1767: Release TDB1 database and location state

[GitBox]

afs opened a new pull request #616: JENA-1767: Release TDB1 database and 
location state
URL: https://github.com/apache/jena/pull/616
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Discuss: write PREFIX not @prefix?

[Rob Vesse]

Same here -1

On 20/09/2019, 12:18, "Claude Warren"  wrote:

For me this falls under "if it ain't broke don't fix it"
so
-1


On Fri, Sep 20, 2019 at 11:47 AM Andy Seaborne  wrote:

> The Turtle and TriG writers output "@prefix".
>
> RDF 1.1 allows PREFIX.
>
> Should we change the writers to output PREFIX? (after the next release)
>
> (we can add options but majority of users don't set options and exisintg
> code doesn't)
>
>  Andy
>


-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

ApacheCon North America 2020, project participation

[Rich Bowen]

Hi, folks,

(Note: You're receiving this email because you're on the dev@ list for
one or more Apache Software Foundation projects.)

For ApacheCon North America 2019, we asked projects to participate in
the creation of project/topic specific tracks. This was very successful,
with about 15 projects stepping up to curate the content for their
track/summit/event.

We need to know if you're going to do the same for 2020. This informs
how large a venue we book for the event, how long the event runs, and
many other considerations.

If you intend to participate again in 2020, we need to hear from you on
the plann...@apachecon.com mailing list. This is not a firm commitment,
but we need to know if you're, say, 75% confident that you'll be
participating.

And, no, we do not have any details at all, but assume that it will be
in roughly the same calendar space as this year's event, ie, somewhere
in the August-October timeframe.

Thanks.

-- 
Rich Bowen
VP Conferences
The Apache Software Foundation
@apachecon