imported>PeterYim at 00:09, 30 April 2013

2013-04-30T00:09:16Z

New page

{{OntologySummit2013_Survey
|Full name of the tool=HyQue
|Description of the tool=HyQue is a system that uses Semantic Web technologies to evaluate formalized hypotheses against experimental data through a combination of SPARQL queries and evaluation rules
|Link to the tool=http://hyque.semanticscience.org/
|Tool home page=http://hyque.semanticscience.org/
|Author=Alison Callahan, Nigam Shah, Michel Dumontier
|Contact=michel.dumontier@gmail.com
|Institutional sponsor=Carleton University
|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
|Rate ontologies on their popularity or review feedback=No
|Other ontology quality and fitness support for exploration phase (describe capability)=HyQue uses ontologies to organize and reason about the underlying linked data sources
|Distinguish between conceptual and operational ontologies and objectives=No
|Generate ontology application and performance requirements=Yes
|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=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=No
|Choose extant core ontologies for reuse=No
|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=No
|Guide ontology design for visualization=No
|Choose ontology language=No
|Choose formal logic language=No
|Choose RDF support=Yes
|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=Yes
|Enforce proper use and coding of URIs=Yes
|Produce the current terminological inferences of an ontology=Yes
|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=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=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 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=No
|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=No
|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=No
|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=No
|Track ontology changes and control versions=No
}}

HyQue - Revision history

imported>PeterYim at 00:09, 30 April 2013