Ontolog Forum
General
| Full name of the tool | Sigma Knowledge Engineering Environment |
| Description of the tool | Sigma knowledge engineering system is an system for developing, viewing and debugging theories in first order logic. It works with Knowledge Interchange Format (KIF) and is optimized for the Suggested Upper Merged Ontology (SUMO) www.ontologyportal.org |
| Link to the tool | http://sigmakee.sourceforge.net |
| Tool home page | http://sigmakee.sourceforge.net |
| Download page | http://sigmakee.sourceforge.net |
| Author | Adam Pease |
| Contact | Adam Pease |
| Institutional sponsor | |
| Last version | 2012-06-12 |
| License | GPL |
| Mailing List |
Exploration
| Find ontologies with specific domain coverage | No |
| -- comment | Optional remarks |
| Compare domain coverage across ontologies | No |
| -- comment | Optional remarks |
| Assess or characterize breadth of domain coverage of an ontology | No |
| -- comment | Optional remarks |
| Assess or characterize depth or detail of domain coverage of an ontology | No |
| -- comment | Optional remarks |
| Assess or characterize use considerations of ontology including licensing, training, cost, updating, software requirements, and security | No |
| -- comment | Optional remarks |
| Assess complexity of concept definitions (necessary and sufficient properties) and use of axioms | Yes |
| -- comment | Optional remarks |
| Identify number and ratio of concepts, relations, and subclassing | No |
| -- comment | Optional remarks |
| Identify frequency of use of ontology language features in an ontology | Yes |
| -- comment | Optional remarks |
| Identify age and use statistics of an ontology and its versions | No |
| -- comment | Optional remarks |
| Assess the inferencing power of an ontology | Yes |
| -- comment | Optional remarks |
| Rate ontologies on their popularity or review feedback | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for exploration phase (describe capability) | Sigma can do full first order and higher order consistency checking of ontologies through automated theorem proving. Sigma also provides a number of other static checks on the ontologies and their mappings to WordNet. |
Management
| Distinguish between conceptual and operational ontologies and objectives | No |
| -- comment | Optional remarks |
| Generate ontology application and performance requirements | No |
| -- comment | Optional remarks |
| Organize and track the life cycle requirements and progression of an ontology | No |
| -- comment | Optional remarks |
| Organize and maintain a collection of related ontologies and ontology modules | Yes |
| -- comment | Optional remarks |
| Provide statistics on ontology versioning and use | No |
| -- comment | Optional remarks |
| Guide ontology development per a quality assurance methodology | Yes |
| -- comment | Optional remarks |
| Assess the reusability of a planned ontology | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for management phase (describe capability) |
Design
| Does SigmaKEE guide formulation of ontology requirements? | |
| Guide formulation of domain scope and detail requirements | No |
| -- comment | Optional remarks |
| Guide formulation of goodness of design requirements | No |
| -- comment | Optional remarks |
| Guide formulation of data and information requirements | No |
| -- comment | Optional remarks |
| Guide formulation of semantic and reasoning requirements | No |
| -- comment | Optional remarks |
| Guide formulation of interface requirements | No |
| -- comment | Optional remarks |
| Guide formulation of level of effort requirements | No |
| -- comment | Optional remarks |
| Facilitate framing a set of competency questions exemplifying ontology objectives | No |
| -- comment | Optional remarks |
| Choose metaphysical methodology | No |
| -- comment | Optional remarks |
| Does SigmaKEE allow one to choose an extant ontology for reuse? | |
| Choose extant top ontology for reuse | Yes |
| -- comment | Optional remarks |
| Choose extant core ontologies for reuse | Yes |
| -- comment | Optional remarks |
| Apply a style of ontological analysis to design | Yes |
| -- comment | Optional remarks |
| Guide design to optimize normalization, factoring, and simplicity of ontology | No |
| -- comment | Optional remarks |
| Guide application of open world or closed world semantics | No |
| -- comment | Optional remarks |
| Guide ontology design to achieve inferencing requirements | Yes |
| -- comment | Optional remarks |
| Guide ontology design to achieve scalability requirements | No |
| -- comment | Optional remarks |
| Enable adjustable query and inference performance | No |
| -- comment | Optional remarks |
| Does SigmaKEE offer design patterns based on current ontology or design context? | |
| Offer application patterns based on current ontology or design context | No |
| -- comment | Optional remarks |
| Offer ontology language patterns based on current ontology or design context | Yes |
| -- comment | Optional remarks |
| Offer methodology patterns based on current ontology or design context | No |
| -- comment | Optional remarks |
| Offer other patterns based on current ontology or design context | No |
| -- comment | Optional remarks |
| Integrate selected design patterns into an ontology design | Yes |
| -- comment | Optional remarks |
| Assess correctness or performance of an ontology design | Yes |
| -- comment | Optional remarks |
| Guide and facilitate modularization of ontology | Yes |
| -- comment | Optional remarks |
| Guide ontology design for visualization | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for design phase (describe capability) | |
Build
General Development
| Does SigmaKEE allow one to choose an ontology language? | |
| Choose ontology language | Yes |
| -- comment | Optional remarks |
| Choose formal logic language | Yes |
| -- comment | Optional remarks |
| Choose RDF support | Yes |
| -- comment | Optional remarks |
| Mix ontology languages | Yes |
| -- comment | Optional remarks |
| Generate ontology code from requirements specification | No |
| -- comment | Optional remarks |
| Generate or enforce selected design patterns in ontology code | No |
| -- comment | Optional remarks |
| Feedback on consistency of granularity and regularity of domain ontology structure | No |
| -- comment | Optional remarks |
| Manage lexical naming and annotation of ontology elements | Yes |
| -- comment | Optional remarks |
| Ensure proper use and coding of RDF and Web resources | No |
| -- comment | Optional remarks |
| Enforce proper use and coding of URIs | No |
| -- comment | Optional remarks |
| Produce the current terminological inferences of an ontology | No |
| -- comment | Optional remarks |
| Optimize query and inference performance | Yes |
| -- comment | Optional remarks |
| Detect violations of domain, referential, or semantic integrity | Yes |
| -- comment | Optional remarks |
| Overall, detect and correct coding errors or inconsistencies | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for build phase (describe capability) | |
Concept Development
| Ensure proper separation and coding of concepts and facts | Yes |
| -- comment | because in an expressive logical language there is no such "proper" separation |
| Ensure kind-of nature and consistency of subclassing | Yes |
| -- comment | Optional remarks |
| Guide subclass versus class individual determinations | No |
| -- comment | Optional remarks |
| Monitor depth of subclassing consistency across a domain ontology | No |
| -- comment | Optional remarks |
| Generate prototypical instances (individuals) to help verify class intent and class subsumption | No |
| -- comment | Optional remarks |
| Detect and guide use of multiple inheritance | No |
| -- comment | Optional remarks |
| Guide use of disjointness axioms | Yes |
| -- comment | Optional remarks |
| Guide use of necessary and sufficient properties in concept definitions | No |
| -- comment | Optional remarks |
| Guide use of existential versus universal quantification in class restrictions | No |
| -- comment | This question seems to presuppose description logic |
| Enforce proper use of conjunctions versus disjunctions | No |
| -- comment | This question seems to presuppose description logic |
Relationship Development
| Ensure proper use and coding of relations | Yes |
| -- comment | Optional remarks |
| Ensure proper use and coding of data types | No |
| -- comment | Optional remarks |
| Assess and enforce consistency and completeness of range and domain constraints | No |
| -- comment | Optional remarks |
| Assess and enforce consistency and completeness of inverse relations | No |
| -- comment | Optional remarks |
| Ensure proper use and coding of transitive relations | No |
| -- comment | Optional remarks |
Validation
| Verify that ontology requirements are met | No |
| -- comment | Optional remarks |
| Can SigmaKEE assess query performance? | |
| Assess query precision and recall performance | No |
| -- comment | not a meaningful question for an expressive logic |
| Assess query time performance | No |
| -- comment | Optional remarks |
| Can SigmaKEE assess inference performance? | |
| Assess inferencing time performance | No |
| -- comment | Optional remarks |
| Assess inferencing completeness performance | No |
| -- comment | Optional remarks |
| Generate characteristic queries and tests | No |
| -- comment | Optional remarks |
| Accept validation test sets or inputs | Yes |
| -- comment | Optional remarks |
| Can SigmaKEE assure computability of ontology? | |
| Assure semantically adequate computability of ontology | No |
| -- comment | Optional remarks |
| Assure mathematically complete computability of ontology | No |
| -- comment | Optional remarks |
| Verify that two ontologies are interoperable | No |
| -- comment | Optional remarks |
| Validate the intended functionality of software using the ontology | No |
| -- comment | Optional remarks |
| Validate instance data conforming to an ontology | No |
| -- comment | Optional remarks |
| Assess accuracy, correctness, and completeness of ontology terminological content | No |
| -- comment | Optional remarks |
| Guide or adjust ontology in accord with validation results | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for validation phase (describe capability) | |
Integration and Use
| Export ontology in different languages | Yes |
| -- comment | Optional remarks |
| Integrate ontology with other ontologies | Yes |
| -- comment | Optional remarks |
| Integrate ontology with other information system resources | Yes |
| -- comment | Optional remarks |
| Assess or track user experience with ontology | No |
| -- comment | Optional remarks |
| Enable user to modify or extend ontology to address deficiencies | Yes |
| -- comment | Optional remarks |
| Create mappings from ontologies to and from data and data sources | Yes |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for integration and use phase (describe capability) |
Maintenance
| Promote reuse of ontology | Yes |
| -- comment | Optional remarks |
| Capture ontology errors during use | No |
| -- comment | Optional remarks |
| Profile use of ontology elements during use | No |
| -- comment | Optional remarks |
| Compare and map between ontologies | Yes |
| -- comment | Optional remarks |
| Track ontology changes and control versions | No |
| -- comment | Optional remarks |
| Other ontology quality and fitness support for maintenance phase (describe capability) |