imported>TorstenHahmann: TorstenHahmann moved page Macleod/ to Macleod: removed unwanted backslash in title

2013-04-05T02:33:50Z

TorstenHahmann moved page Macleod/ to Macleod: removed unwanted backslash in title

New page

{{OntologySummit2013_Survey
|Full name of the tool=Macleod - Common Logic Environment for Ontology Development
|Description of the tool=This program consists of a set of scripts designed for key reasoning tasks frequently encountered in ontology design and verification. At the moment it focuses on automating tasks that can be accomplished independent of the semantic of concepts and relations. These tasks are consistency checking of ontologies and their modules as well as checking whether competency questions, providing as ''lemmas'', are entailed.

While the program primarily targets first-order ontologies specified in the Common Logic (CL) syntax, some parts of it can also be used for reasoning about ontologies in LADR (Prover9/Mace4) or TPTP syntax (accepted by many first-order theorem provers and model finders). The tasks are accomplished by running existing automated theorem provers and model finders in parallel to establish consistency or inconsistency of an ontology or a module thereof, or to prove a sentence from an ontology (or module) or to find a counterexample of the sentence.
Moreover, the tool exploits the modularity of ontologies, which manifests itself in its file CL imports structure.

In the near future it will be integrated with COLORE to provide design, verification, and other reasoning support for all ontologies in the repository.
|Link to the tool=https://github.com/thahmann/macleod
|Tool home page=https://github.com/thahmann/macleod
|Download page=https://github.com/thahmann/macleod/archive/master.zip
|Author=Torsten Hahmann
|Contact=torsten@cs.toronto.edu
|Institutional sponsor=University of Toronto
|License=GNU GPL
|Find ontologies with specific domain coverage=No
|Compare domain coverage across ontologies=No
|Assess or characterize breadth of domain coverage of an ontology=No
|Assess or characterize depth or detail of domain coverage of an ontology=No
|Assess or characterize use considerations of ontology including licensing, training, cost, updating, software requirements, and security=No
|Assess complexity of concept definitions (necessary and sufficient properties) and use of axioms=No
|Identify number and ratio of concepts, relations, and subclassing=No
|Identify frequency of use of ontology language features in an ontology=No
|Identify age and use statistics of an ontology and its versions=No
|Assess the inferencing power of an ontology=Yes
|Assess the inferencing power of an ontology comments=proving formally expressed compentency questions
|Rate ontologies on their popularity or review feedback=No
|Distinguish between conceptual and operational ontologies and objectives=No
|Generate ontology application and performance requirements=No
|Organize and track the life cycle requirements and progression of an ontology=No
|Organize and maintain a collection of related ontologies and ontology modules=No
|Provide statistics on ontology versioning and use=No
|Guide ontology development per a quality assurance methodology=No
|Assess the reusability of a planned ontology=No
|Guide formulation of domain scope and detail requirements=No
|Guide formulation of goodness of design requirements=No
|Guide formulation of data and information requirements=No
|Guide formulation of semantic and reasoning requirements=No
|Guide formulation of interface requirements=No
|Guide formulation of level of effort requirements=No
|Facilitate framing a set of competency questions exemplifying ontology objectives=No
|Choose metaphysical methodology=No
|Choose extant top ontology for reuse=Yes
|Choose extant top ontology for reuse comments=any from COLORE
|Choose extant core ontologies for reuse=Yes
|Choose extant core ontologies for reuse comments=any from COLORE
|Apply a style of ontological analysis to design=No
|Guide design to optimize normalization, factoring, and simplicity of ontology=No
|Guide application of open world or closed world semantics=No
|Guide ontology design to achieve inferencing requirements=No
|Guide ontology design to achieve scalability requirements=No
|Enable adjustable query and inference performance=No
|Offer application patterns based on current ontology or design context=No
|Offer ontology language patterns based on current ontology or design context=No
|Offer methodology patterns based on current ontology or design context=No
|Offer other patterns based on current ontology or design context=No
|Integrate selected design patterns into an ontology design=No
|Assess correctness or performance of an ontology design=No
|Guide and facilitate modularization of ontology=Yes
|Guide ontology design for visualization=No
|Choose ontology language=No
|Choose formal logic language=No
|Choose RDF support=No
|Mix ontology languages=No
|Generate ontology code from requirements specification=No
|Generate or enforce selected design patterns in ontology code=No
|Feedback on consistency of granularity and regularity of domain ontology structure=No
|Manage lexical naming and annotation of ontology elements=No
|Ensure proper use and coding of RDF and Web resources=No
|Enforce proper use and coding of URIs=No
|Produce the current terminological inferences of an ontology=No
|Optimize query and inference performance=No
|Detect violations of domain, referential, or semantic integrity=No
|Overall, detect and correct coding errors or inconsistencies=Yes
|Ensure proper separation and coding of concepts and facts=No
|Ensure kind-of nature and consistency of subclassing=Yes
|Guide subclass versus class individual determinations=No
|Monitor depth of subclassing consistency across a domain ontology=No
|Generate prototypical instances (individuals) to help verify class intent and class subsumption=No
|Detect and guide use of multiple inheritance=No
|Guide use of disjointness axioms=No
|Guide use of necessary and sufficient properties in concept definitions=No
|Guide use of existential versus universal quantification in class restrictions=No
|Enforce proper use of conjunctions versus disjunctions=No
|Ensure proper use and coding of relations=No
|Ensure proper use and coding of data types=No
|Assess and enforce consistency and completeness of range and domain constraints=Yes
|Assess and enforce consistency and completeness of inverse relations=No
|Ensure proper use and coding of transitive relations=No
|Verify that ontology requirements are met=Yes
|Verify that ontology requirements are met comments=through competency questions
|Assess query precision and recall performance=No
|Assess query time performance=No
|Assess inferencing time performance=No
|Assess inferencing completeness performance=No
|Generate characteristic queries and tests=No
|Accept validation test sets or inputs=Yes
|Assure semantically adequate computability of ontology=No
|Assure mathematically complete computability of ontology=No
|Verify that two ontologies are interoperable=Yes
|Verify that two ontologies are interoperable comments=interpretations can be proved
|Validate the intended functionality of software using the ontology=No
|Validate instance data conforming to an ontology=No
|Assess accuracy, correctness, and completeness of ontology terminological content=No
|Guide or adjust ontology in accord with validation results=No
|Export ontology in different languages=Yes
|Export ontology in different languages comments=currently supported: TPTP, LADR (Prover9/Mace4)
|Integrate ontology with other ontologies=No
|Integrate ontology with other information system resources=No
|Assess or track user experience with ontology=No
|Enable user to modify or extend ontology to address deficiencies=No
|Create mappings from ontologies to and from data and data sources=No
|Promote reuse of ontology=Yes
|Promote reuse of ontology comments=through mappings/interpretaions
|Capture ontology errors during use=No
|Profile use of ontology elements during use=No
|Compare and map between ontologies=Yes
|Compare and map between ontologies comments=mappings/interpretations between ontologies
|Track ontology changes and control versions=Yes
|Track ontology changes and control versions comments=within COLORE
}}

Macleod - Revision history

imported>TorstenHahmann: TorstenHahmann moved page Macleod/ to Macleod: removed unwanted backslash in title