question on Eyeball license

[Mei Sasaki]

Dear developers,

Thanks for all your time and effort in developing Apache Jena.
I am currently trying to use Eyeball as a validating tool at my workplace.

However, I am worried about license issues.
I have checked out source code from here;
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/
The comment on top of this code implies that the framework is distributed under the Apache License.
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/assembly-eyeball.xml
However, this webpage clearly states that “Jena Eyeball has not been released under the Apache Software License.”
https://jena.apache.org/documentation/tools/eyeball-getting-started.html

This puzzles me.
It would be of great help if you could inform of me which license Eyeball is distributed under.

Thanks in advance!
++++++++++++++++++++++++++++++++++++
Yahoo Japan Corporation
Mei Sasaki (Ph.D.)

[Chris Dollin]

Post by Mei Sasaki
Dear developers,
Thanks for all your time and effort in developing Apache Jena.
I am currently trying to use Eyeball as a validating tool at my workplace.
However, I am worried about license issues.
I have checked out source code from here;
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/
The comment on top of this code implies that the framework is distributed under the Apache License.
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/assembly-eyeball.xml
However, this webpage clearly states that “Jena Eyeball has not been released under the Apache Software License.”
https://jena.apache.org/documentation/tools/eyeball-getting-started.html
This puzzles me.
It would be of great help if you could inform of me which license Eyeball is distributed under.

Hmm. I'll try and get this cleared up. (I'm the original developer of
Eyeball.)

Chris

[Andy Seaborne]

Post by Chris Dollin

Post by Mei Sasaki
Dear developers,
Thanks for all your time and effort in developing Apache Jena.
I am currently trying to use Eyeball as a validating tool at my workplace.
However, I am worried about license issues.
I have checked out source code from here;
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/
The comment on top of this code implies that the framework is
distributed under the Apache License.
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/assembly-eyeball.xml
However, this webpage clearly states that “Jena Eyeball has not been
released under the Apache Software License.”
https://jena.apache.org/documentation/tools/eyeball-getting-started.html
This puzzles me.
It would be of great help if you could inform of me which license
Eyeball is distributed under.

Hmm. I'll try and get this cleared up. (I'm the original developer of
Eyeball.)
Chris

The code is covered by the HP grant and the license headers are correct.

"not released" means there are no built binaries (maven or download).

A release means the PMC has checked the licensing including dependencies
but anything in a public repo should have a license on it.

Repos are open for a reason - you can take code from them.

Being unreleased puts the onus on you with regard to checking and
dependencies. (Apache even have a license checking tool:
http://creadur.apache.org/rat/)

All the Eyeball code should have been bulk converted when the codebase
was imported originally. If you find anything wrong, let us know.

The dependencies are very, very old. It is not RDF 1.1.

Andy

[Mei Sasaki]

Dear Chris, Andy,
Thanks for your quick response.
Ok, I got that since the Eyeball is not released,
it is my responsibility to check the licenses of the old bits of code that Eyeball depends on.
I would either use the license checking tool Andy mentioned or would try to find other ways to validate
data that have less problem with licenses.
Thanks again for your help!
Mei

Post by Chris Dollin

Post by Mei Sasaki
Dear developers,
Thanks for all your time and effort in developing Apache Jena.
I am currently trying to use Eyeball as a validating tool at my workplace.
However, I am worried about license issues.
I have checked out source code from here;
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/
The comment on top of this code implies that the framework is
distributed under the Apache License.
https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/assembly-eyeball.xml
However, this webpage clearly states that “Jena Eyeball has not been
released under the Apache Software License.”
https://jena.apache.org/documentation/tools/eyeball-getting-started.html
This puzzles me.
It would be of great help if you could inform of me which license
Eyeball is distributed under.

Hmm. I'll try and get this cleared up. (I'm the original developer of
Eyeball.)
Chris

The code is covered by the HP grant and the license headers are correct.

"not released" means there are no built binaries (maven or download).

A release means the PMC has checked the licensing including dependencies
but anything in a public repo should have a license on it.

Repos are open for a reason - you can take code from them.

Being unreleased puts the onus on you with regard to checking and
dependencies. (Apache even have a license checking tool:
http://creadur.apache.org/rat/)

All the Eyeball code should have been bulk converted when the codebase
was imported originally. If you find anything wrong, let us know.

The dependencies are very, very old. It is n

[Andy Seaborne]

Post by Mei Sasaki
Dear Chris, Andy,
Thanks for your quick response.
Ok, I got that since the Eyeball is not released,
it is my responsibility to check the licenses of the old bits of code that Eyeball depends on.
I would either use the license checking tool Andy mentioned or would try to find other ways to validate
data that have less problem with licenses.
Thanks again for your help!
Mei

RDF Validation is moving towards SHACL (W3C spec in progress)

Draft:
http://w3c.github.io/data-shapes/shacl/

Implementation:
https://github.com/TopQuadrant/shacl

I'd be interested to hear if this meets your requirements.

Andy

[Mei Sasaki]

Dear Andy,

I took a quick look on SHACL.
It looks like exactly what we were looking for, but GNU Affero General Public License makes
it almost impossible for our team (and most business enterprises) to use this tool.
I am thinking of using some implementations of ShEx validator.
Thanks anyway for your advice!
Mei

Post by Mei Sasaki
Dear Chris, Andy,
Thanks for your quick response.
Ok, I got that since the Eyeball is not released,
it is my responsibility to check the licenses of the old bits of code that Eyeball depends on.
I would either use the license checking tool Andy mentioned or would try to find other ways to validate
data that have less problem with licenses.
Thanks again for your help!
Mei

RDF Validation is moving towards SHACL (W3C spec in progress)

Draft:
http://w3c.github.io/data-shapes/shacl/

Implementation:
https://github.com/TopQuadrant/shacl

I'd be interested to hear if this meets your requirement