All Downloads are FREE. Search and download functionalities are using the official Maven repository.

Download all versions of integraal-backward-chaining JAR files with all dependencies

Search JAR files by class name

integraal-backward-chaining from group fr.lirmm.graphik (version 1.5.1)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.5.1
Last update 05. September 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.4.3)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.4.3
Last update 17. July 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.4.2)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.4.2
Last update 06. July 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.5.0)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.5.0
Last update 21. June 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.4.1)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.4.1
Last update 31. May 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.4.0)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.4.0
Last update 28. May 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.3.0)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.3.0
Last update 28. May 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.2.1)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.2.1
Last update 22. May 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.2.0)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.2.0
Last update 15. April 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!

integraal-backward-chaining from group fr.lirmm.graphik (version 1.1.0)

InteGraal has been designed in a modular way, in order to facilitate software reuse and extension. It should make it easy to test new scenarios and techniques, in particular by combining algorithms. The main features of Graal are currently the following: (1) internal storage to store data by using a SQL or RDF representation (Postgres, MySQL, HSQL, SQLite, Remote SPARQL endpoints, Local in-memory triplestores) as well as a native in-memory representation (2) data-integration capabilities for exploiting federated heterogeneous data-sources through mappings able to target systems such as SQL, RDF, and black-box (e.g. Web-APIs) (3) algorithms for query-answering over heterogeneous and federated data based on query rewriting and/or forward chaining (or chase)

Group: fr.lirmm.graphik Artifact: integraal-backward-chaining
Show documentation Show source 
 

0 downloads
Artifact integraal-backward-chaining
Group fr.lirmm.graphik
Version 1.1.0
Last update 19. March 2024
Tags: through been reuse software data main scenarios remote heterogeneous features answering rewriting should mysql chaining triplestores order based using modular test sqlite query particular easy integraal apis techniques following integration facilitate algorithms extension internal memory sources storage representation chase local federated native systems hsql designed make postgres over graal endpoints capabilities forward black combining store exploiting target such mappings currently able well sparql
Organization not specified
URL https://gitlab.inria.fr/rules/integraal/integraal-backward-chaining
License Apache License, Version 2.0
Dependencies amount 11
Dependencies integraal-model, integraal-core, integraal-unifiers, integraal-util, integraal-query-evaluation, integraal-storage, guava, commons-lang3, integraal-io, slf4j-api, logback-classic,
There are maybe transitive dependencies!



Page 1 from 2 (items total 12)


© 2015 - 2024 Weber Informatics LLC | Privacy Policy