Thanks, Greg, this is very detailed. Once the new module is in and settled and
we have a release or two to learn from, I will take a closer look at the usage
of this code to understand how it differs from the kind of caching that occurs
elsewhere in Jena.
ajs6f
> On Apr 14, 2019, at 6:21 AM, G
Hi Greg,
Neither of those (jdom2,rdf-tables) are problems or need anythign does
before we can release Jena with GeoSPARQL in it. They can be changed, or
not, later.
For timing: everyone is busy!
We could release 3.11.0 ASAP (it's 4 months since 3.10.0) and
immediately start on 3.12.0. I hav
Hi,
There are a lot of permutations that a GeoSPARQL query could take which
can generate different values that may or may not be useful later on.
The general strategy is to keep what is generated for a while and if
isn't used then drop it. I don't think any of the Cache implementations
offer this
Hi,
- rdf-tables: This could be taken out if problematic. It is a CSV/TSV to
RDF converter to provide another route to load geospatial data and was
useful on another project. Given that jena-csv has been deprecated,
there might not be the demand for its inclusion.
- jdom2: This is only used for
On 09/04/2019 17:02, Andy Seaborne wrote:
Here are the new dependencies:
[INFO] | +- org.apache.sis.core:sis-referencing:jar:0.8:compile
[INFO] | | +- javax.measure:unit-api:jar:1.0:compile
[INFO] | | \- org.opengis:geoapi:jar:3.0.1:compile
via the org.apache.sis
org.opengis:geoapi
Just out of curiosity, Greg, what is the functionality offered by Expiring Map
that isn't offered by Jena's already-extant oaj.atlas.lib.Cache
implementations? Is it the ability to manually trigger expirations?
ajs6f
> On Apr 9, 2019, at 12:02 PM, Andy Seaborne wrote:
>
> [INFO] | \- io.gith
Here are the new dependencies:
[INFO] | +- org.apache.sis.core:sis-referencing:jar:0.8:compile
[INFO] | | +- javax.measure:unit-api:jar:1.0:compile
[INFO] | | \- org.opengis:geoapi:jar:3.0.1:compile
via the org.apache.sis
org.opengis:geoapi
https://github.com/opengeospatial/geoapi
A fo
