issues  

Messages by Thread

• • Re: [I] Broken CLI tool: jena.textindexer [jena] via GitHub
• [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
  • Re: [I] Fuseki 5.5.0 Increased Heap Usage [jena] via GitHub
• [I] Add more tests for EBV, and FILTER isSatisfiable [jena] via GitHub
  • Re: [I] Add more tests for EBV, and FILTER isSatisfiable [jena] via GitHub
• [I] DatasetGraphFactory.createWithGraphMaker [jena] via GitHub
  • Re: [I] DatasetGraphFactory.createWithGraphMaker [jena] via GitHub
• [I] `IF` does not handle errors in the condition expression as effective boolean values. [jena] via GitHub
  • Re: [I] `IF` does not handle errors in the condition expression as effective boolean values. [jena] via GitHub
  • Re: [I] `IF` does not handle errors in the condition expression as effective boolean values. [jena] via GitHub
  • Re: [I] `IF` does not handle errors in the condition expression as effective boolean values. [jena] via GitHub
• [I] Jena scripts fail if an ancestor directory has spaces in its name [jena] via GitHub
  • Re: [I] Jena scripts fail if an ancestor directory has spaces in its name [jena] via GitHub
  • Re: [I] Jena scripts fail if an ancestor directory has spaces in its name [jena] via GitHub
  • Re: [I] Jena scripts fail if an ancestor directory has spaces in its name [jena] via GitHub
  • Re: [I] Jena scripts fail if an ancestor directory has spaces in its name [jena] via GitHub
• [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 exposes numeric literals in canonical form instead of lexical form. [jena] via GitHub
  • Re: [I] TDB2 fails to roundtrip non-canonical decimals. [jena] via GitHub
• [I] Calculate variables used within an expression once and cache. [jena] via GitHub
  • Re: [I] Calculate variables used within an expression once and cache. [jena] via GitHub
• [I] sh:sourceConstraint missing on SHACl validation results [jena] via GitHub
  • Re: [I] sh:sourceConstraint missing on SHACL validation results [jena] via GitHub
  • Re: [I] sh:sourceConstraint missing on SHACL validation results [jena] via GitHub
• [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
  • Re: [I] ExprTripleTerm should return getConstant [jena] via GitHub
• [I] Convert the W3C tests manifest processor to JUnit5 [jena] via GitHub
  • Re: [I] Convert the W3C tests manifest processor to JUnit5 [jena] via GitHub
• [I] Emit warnings for dot segments when not at the start of a relative URI [jena] via GitHub
  • Re: [I] Emit warnings for dot segments when not at the start of a relative URI [jena] via GitHub
• [I] Deprecate oaj.ontology.OntModel (oaj.onrtology migrating to jena-ontapi) [jena] via GitHub
  • Re: [I] Deprecate oaj.ontology.OntModel (oaj.ontology migrating to jena-ontapi) [jena] via GitHub
• [I] StatementTerm.isResource() should not return true [jena] via GitHub
  • Re: [I] StatementTerm.isResource() should not return true [jena] via GitHub
  • Re: [I] StatementTerm.isResource() should not return true [jena] via GitHub
• [I] Decode JSON-LD blank node identifiers [jena] via GitHub
  • Re: [I] Decode JSON-LD blank node identifiers [jena] via GitHub
  • Re: [I] Decode JSON-LD blank node identifiers [jena] via GitHub
  • Re: [I] Decode JSON-LD blank node identifiers [jena] via GitHub
• [I] Update javascript test dependency on-headers [jena] via GitHub
  • Re: [I] Update javascript test dependency on-headers [jena] via GitHub
• [I] Consistent [jena] via GitHub
  • Re: [I] Provide an API to start a Fuseki server inside an application [jena] via GitHub
  • Re: [I] Provide an API to start a Fuseki server inside an application [jena] via GitHub
• [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
  • Re: [I] Clarification on removal of config upload endpoint [jena] via GitHub
• [I] Idle timeout expired [jena] via GitHub
  • Re: [I] Idle timeout expired [jena] via GitHub
  • Re: [I] Idle timeout expired [jena] via GitHub
  • Re: [I] Idle timeout expired [jena] via GitHub
  • Re: [I] Idle timeout expired [jena] via GitHub
  • Re: [I] Idle timeout expired [jena] via GitHub
• [I] Tidy up jena-permissions [jena] via GitHub
  • Re: [I] Tidy up jena-permissions [jena] via GitHub
• [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
  • Re: [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
  • Re: [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
  • Re: [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
  • Re: [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
  • Re: [I] jena-fuseki-war on tomcat - java.lang.NoClassDefFoundError: jakarta/faces/context/FacesContext [jena] via GitHub
• [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
  • Re: [I] Wrong prefix parsing when JSON-LD root is an array [jena] via GitHub
• [I] Upgarse JUint usage in jena-tdb2 testing [jena] via GitHub
  • Re: [I] Upgrade JUnit usage in jena-tdb2 testing [jena] via GitHub
• [I] Upgrade JUnit usage in jena-db testing [jena] via GitHub
  • Re: [I] Upgrade JUnit usage in jena-db testing [jena] via GitHub
• [I] Upgrade JUnit usage in jena-base testing [jena] via GitHub
  • Re: [I] Upgrade JUnit usage in jena-base testing [jena] via GitHub
• [I] COALESCE function has poor performance compared to IF(BOUND(...), ..., ...) pattern [jena] via GitHub
  • Re: [I] COALESCE function has poor performance compared to IF(BOUND(...), ..., ...) pattern [jena] via GitHub
  • Re: [I] COALESCE function has poor performance compared to IF(BOUND(...), ..., ...) pattern [jena] via GitHub
  • Re: [I] COALESCE function has poor performance compared to IF(BOUND(...), ..., ...) pattern [jena] via GitHub
• [I] New ontapi and Jena assembers. [jena] via GitHub
  • Re: [I] New ontapi and Jena assembers. [jena] via GitHub
  • Re: [I] New ontapi and Jena assembers. [jena] via GitHub
• [I] geof:Distance doesn't work for non Euclidian coordinates [jena] via GitHub
• Re: [I] try it! link [jena] via GitHub
  • Re: [I] try it! link [jena] via GitHub
• [I] Store the base database-create request graph [jena] via GitHub
  • Re: [I] Store the base database-create request graph [jena] via GitHub
• [I] Improve handling of duplicate database defintions. [jena] via GitHub
  • Re: [I] Improve handling of duplicate database defintions. [jena] via GitHub
• [I] Warning for unset SIS_DATA from fuseki server. [jena] via GitHub
  • Re: [I] Warning for unset SIS_DATA from fuseki server. [jena] via GitHub
  • Re: [I] Warning for unset SIS_DATA from fuseki server. [jena] via GitHub
• [I] Safe refresh? [jena] via GitHub
  • Re: [I] Safe refresh? [jena] via GitHub
  • Re: [I] Safe refresh? [jena] via GitHub
  • Re: [I] Safe refresh? [jena] via GitHub
  • Re: [I] Safe refresh? [jena] via GitHub
  • Re: [I] Safe refresh? [jena] via GitHub
• [I] IRI3986 parser does not handle paths with only slashes [jena] via GitHub
  • Re: [I] IRI3986 parser does not handle paths with only slashes [jena] via GitHub
• [I] Upgrade JUnit usage in jena-arq testing [jena] via GitHub
  • Re: [I] Upgrade JUnit usage in jena-arq testing [jena] via GitHub
• [I] Lang tag parsing does not match private use correctly. [jena] via GitHub
  • Re: [I] Lang tag parsing does not match private use correctly. [jena] via GitHub
• [I] RDF/XML parsing breaks on bad IRI for a namespace IRI [jena] via GitHub
  • Re: [I] RDF/XML parsing breaks on bad IRI for a namespace IRI [jena] via GitHub
• [I] uparse does not support --base [jena] via GitHub
  • Re: [I] uparse does not support --base [jena] via GitHub
• [I] `riot` does not log an error for a bad base direction. [jena] via GitHub
  • Re: [I] `riot` does not log an error for a bad base direction. [jena] via GitHub
• [I] Improve handling of database update requests to Fuseki [jena] via GitHub
  • Re: [I] Improve handling of database update requests to Fuseki [jena] via GitHub
  • Re: [I] Improve handling of database update requests to Fuseki [jena] via GitHub
  • Re: [I] Improve handling of database update requests to Fuseki [jena] via GitHub
  • Re: [I] Improve handling of database update requests to Fuseki [jena] via GitHub
  • Re: [I] Improve handling of database update requests to Fuseki [jena] via GitHub
• [I] Warnings logged by the build of jena-integration-tests about geosparql [jena] via GitHub
  • Re: [I] Warnings logged by the build of jena-integration-tests about geosparql [jena] via GitHub
  • Re: [I] Warnings logged by the build of jena-integration-tests about geosparql [jena] via GitHub
• [I] Reject surrogate codepoints that are \u or \U escaped. [jena] via GitHub
  • Re: [I] Reject surrogate codepoints that are \u or \U escaped. [jena] via GitHub
• Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
  • Re: [D] GeoSPARQL query internal error [jena] via GitHub
• [I] Support for `UNDEF` in `ParameterizedSparqlString` VALUES methods [jena] via GitHub
  • Re: [I] Support for `UNDEF` in `ParameterizedSparqlString` VALUES methods [jena] via GitHub
• [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
  • Re: [I] SPARQL Substitution on INSERT does not preserve Blank Node IDs [jena] via GitHub
• [I] Support for compressed data with graph store protocol [jena] via GitHub
  • Re: [I] Support for uploading compressed data with GSP and SPARQL [jena] via GitHub
• [I] ExprFunctionOp: Inconsistent Element and Op after transforms [jena] via GitHub
  • Re: [I] ExprFunctionOp: Inconsistent Element and Op after transforms [jena] via GitHub
• Re: [I] jena-reasoning-extended module proposal: Enhanced reasoning capabilities for Jena [jena] via GitHub
• Re: [I] jena-memory module proposal: Optimized memory management for Jena RDF data [jena] via GitHub
• Re: [I] jena-vector module proposal: Native vector and embedding support [jena] via GitHub
• Re: [I] jena-neural-sym module proposal: Neural-symbolic reasoning for Jena [jena] via GitHub
• Re: [I] jena-query-accelerator module proposal: Advanced SPARQL optimization and acceleration [jena] via GitHub
• [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
  • Re: [I] Unable to delete database folder after deleting in UI due to "Resource busy" error [jena] via GitHub
• [I] Deprecation for GraphMemFactory.createGraphMem. Prepare for migration to being a same-term graph. [jena] via GitHub
  • Re: [I] Deprecation for GraphMemFactory.createGraphMem. Prepare for migration to being a same-term graph. [jena] via GitHub
• [I] Upgrade JUnit usage in jena-core testing [jena] via GitHub
• [I] GeoSPARQL implementation not supporting distance in meters and transformations [jena] via GitHub
  • Re: [I] GeoSPARQL implementation not supporting distance in meters and transformations [jena] via GitHub

• Earlier messages
• Later messages