imported>Apease at 20:28, 20 April 2013

2013-04-20T20:28:28Z

New page

{{OntologySummit2013_Survey
|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
|Last version=2012-06-12
|License=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=Yes
|Identify number and ratio of concepts, relations, and subclassing=No
|Identify frequency of use of ontology language features in an ontology=Yes
|Identify age and use statistics of an ontology and its versions=No
|Assess the inferencing power of an ontology=Yes
|Rate ontologies on their popularity or review feedback=No
|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.
|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=Yes
|Provide statistics on ontology versioning and use=No
|Guide ontology development per a quality assurance methodology=Yes
|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 core ontologies for reuse=Yes
|Apply a style of ontological analysis to design=Yes
|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=Yes
|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=Yes
|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=Yes
|Assess correctness or performance of an ontology design=Yes
|Guide and facilitate modularization of ontology=Yes
|Guide ontology design for visualization=No
|Choose ontology language=Yes
|Choose formal logic language=Yes
|Choose RDF support=Yes
|Mix ontology languages=Yes
|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=Yes
|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=Yes
|Detect violations of domain, referential, or semantic integrity=Yes
|Overall, detect and correct coding errors or inconsistencies=No
|Ensure proper separation and coding of concepts and facts=Yes
|Ensure proper separation and coding of concepts and facts comments=because in an expressive logical language there is no such "proper" separation
|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=Yes
|Guide use of necessary and sufficient properties in concept definitions=No
|Guide use of existential versus universal quantification in class restrictions=No
|Guide use of existential versus universal quantification in class restrictions comments=This question seems to presuppose description logic
|Enforce proper use of conjunctions versus disjunctions=No
|Enforce proper use of conjunctions versus disjunctions comments=This question seems to presuppose description logic
|Ensure proper use and coding of relations=Yes
|Ensure proper use and coding of data types=No
|Assess and enforce consistency and completeness of range and domain constraints=No
|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=No
|Assess query precision and recall performance=No
|Assess query precision and recall performance comments=not a meaningful question for an expressive logic
|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=No
|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
|Integrate ontology with other ontologies=Yes
|Integrate ontology with other information system resources=Yes
|Assess or track user experience with ontology=No
|Enable user to modify or extend ontology to address deficiencies=Yes
|Create mappings from ontologies to and from data and data sources=Yes
|Promote reuse of ontology=Yes
|Capture ontology errors during use=No
|Profile use of ontology elements during use=No
|Compare and map between ontologies=Yes
|Track ontology changes and control versions=No
}}

SigmaKEE - Revision history

imported>Apease at 20:28, 20 April 2013