Euler is an inference engine supporting logic based proofs.
It is a backward-chaining reasoner enhanced with Euler path detection.
Via N3 it is interoperable with W3C Cwm.
See DONE,
README,
INSTALL,
BUILD,
GUIDE,
FAQ and
LICENSE.
Things are described in N3 thanks to
Tim Berners-Lee and
Dan Connolly.
The current reasoning engine is EYE developed by Jos De Roo.
See Also
Ontologies
- agent - general description of agents and the roles they can play
- bioSKOSSchemes - formal description of SKOS Schemes of biological terminologies/coding systems and their datatypes
- care - general description of human care (onset)
- coding - formal general description of coding
- computer - formal description of digital computer
- countries - description of country codes as standardized in ISO 3166-1 version 2006
- decisionSupport - description of decision support
- digitalProcedure - description of a digital procedure
- document - general description of document
- environment - general description of environment
- event - formal general description of events, actions, their time and other relations
- foster - description of general concepts
- genomeAbnormality - general description of genome abnormality
- human - general description of human
- humanBody - general description of human body
- languages - description of language codes as standardized in ISO 639
- organism - general description of organism
- organization - general description of organization and the roles it can play
- physicalResource - formal general description of physical resource
- quantities - description of quantities, as an extension of the NASA 'SWEET' ontologies
- space - formal description of space
- sparql - general description of SPARQL domain
- sparqlAnalysis - description of RDF data analysis using SPARQL
- sparqlAnalysisTemplate - description of SPARQL query templates for RDF data analysis
- substanceForms - high level description of substance forms (onset)
- time - for formal temporal reasoning,using the Unix Epoch time
- units - description of units, as an extension of NASA's sciUnits ontology
- weekScheme - general description of a working week scheme
- workflow - description of how work in a organization or other system is planned and executed
Theories
Test Cases
Test Cases Performance
Test Cases SHOULD
- have a THIS part and a THAT part such that assuming the THIS part implies the THAT part
- have explicit assumptions because assumptions should be checked
- make issues observable (both issues w.r.t. requirements and designissues)
- lead to test results which are one of passing, failing, undecided or no-data
- be in the following state: proposed, approved, extra-credit or obsoleted
Conclusions
- first support simple and then more complex systems
- RDF and OWL enable optimal reuse of data in networked environment
- a bit like going from cpu/memory/network/IOhardware to engines/triples/webservices/IOsoftware
- or from avoid-hardware-wiring to avoid-software-wiring...
- and promising for automatic software component generation
Jos De Roo
