<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://ontologforum.com/index.php?action=history&amp;feed=atom&amp;title=RepOSE</id>
	<title>RepOSE - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://ontologforum.com/index.php?action=history&amp;feed=atom&amp;title=RepOSE"/>
	<link rel="alternate" type="text/html" href="https://ontologforum.com/index.php?title=RepOSE&amp;action=history"/>
	<updated>2026-04-23T04:19:58Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.0</generator>
	<entry>
		<id>https://ontologforum.com/index.php?title=RepOSE&amp;diff=844&amp;oldid=prev</id>
		<title>imported&gt;KennethBaclawski: Fix PurpleMediaWiki references</title>
		<link rel="alternate" type="text/html" href="https://ontologforum.com/index.php?title=RepOSE&amp;diff=844&amp;oldid=prev"/>
		<updated>2016-01-09T08:37:08Z</updated>

		<summary type="html">&lt;p&gt;Fix PurpleMediaWiki references&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{OntologySummit2013_Survey&lt;br /&gt;
|Full name of the tool=Repair of Ontological Structure Environment&lt;br /&gt;
|Description of the tool=RepOSE is a system for debugging, i.e. detecting and repairing defects in ontologies and alignments. It deals with modeling and semantic defects. We have focused on debugging missing and wrong is-a structure and mappings. [[RepOSE]] exists in different versions of which one is currently available for download.&lt;br /&gt;
|Link to the tool=http://www.ida.liu.se/~patla/research/RepOSE/&lt;br /&gt;
|Tool home page=http://www.ida.liu.se/~patla/research/RepOSE/&lt;br /&gt;
|Download page=http://www.ida.liu.se/~patla/research/RepOSE/&lt;br /&gt;
|Author=Patrick Lambrix (main contact)&lt;br /&gt;
|Contact=patrick.lambrix@liu.se&lt;br /&gt;
|Last version=(for download) RepOSE-T-MI&lt;br /&gt;
|License=educational, research and non-commercial purposes&lt;br /&gt;
|Find ontologies with specific domain coverage=No&lt;br /&gt;
|Compare domain coverage across ontologies=No&lt;br /&gt;
|Assess or characterize breadth of domain coverage of an ontology=No&lt;br /&gt;
|Assess or characterize depth or detail of domain coverage of an ontology=No&lt;br /&gt;
|Assess or characterize use considerations of ontology including licensing, training, cost, updating, software requirements, and security=No&lt;br /&gt;
|Assess complexity of concept definitions (necessary and sufficient properties) and use of axioms=No&lt;br /&gt;
|Identify number and ratio of concepts, relations, and subclassing=No&lt;br /&gt;
|Identify frequency of use of ontology language features in an ontology=No&lt;br /&gt;
|Identify age and use statistics of an ontology and its versions=No&lt;br /&gt;
|Assess the inferencing power of an ontology=No&lt;br /&gt;
|Rate ontologies on their popularity or review feedback=No&lt;br /&gt;
|Distinguish between conceptual and operational ontologies and objectives=No&lt;br /&gt;
|Generate ontology application and performance requirements=No&lt;br /&gt;
|Organize and track the life cycle requirements and progression of an ontology=No&lt;br /&gt;
|Organize and maintain a collection of related ontologies and ontology modules=No&lt;br /&gt;
|Provide statistics on ontology versioning and use=No&lt;br /&gt;
|Guide ontology development per a quality assurance methodology=No&lt;br /&gt;
|Assess the reusability of a planned ontology=No&lt;br /&gt;
|Guide formulation of domain scope and detail requirements=No&lt;br /&gt;
|Guide formulation of goodness of design requirements=No&lt;br /&gt;
|Guide formulation of data and information requirements=No&lt;br /&gt;
|Guide formulation of semantic and reasoning requirements=No&lt;br /&gt;
|Guide formulation of interface requirements=No&lt;br /&gt;
|Guide formulation of level of effort requirements=No&lt;br /&gt;
|Facilitate framing a set of competency questions exemplifying ontology objectives=No&lt;br /&gt;
|Choose metaphysical methodology=No&lt;br /&gt;
|Choose extant top ontology for reuse=No&lt;br /&gt;
|Choose extant core ontologies for reuse=No&lt;br /&gt;
|Apply a style of ontological analysis to design=No&lt;br /&gt;
|Guide design to optimize normalization, factoring, and simplicity of ontology=No&lt;br /&gt;
|Guide application of open world or closed world semantics=No&lt;br /&gt;
|Guide ontology design to achieve inferencing requirements=No&lt;br /&gt;
|Guide ontology design to achieve scalability requirements=No&lt;br /&gt;
|Enable adjustable query and inference performance=No&lt;br /&gt;
|Offer application patterns based on current ontology or design context=No&lt;br /&gt;
|Offer ontology language patterns based on current ontology or design context=No&lt;br /&gt;
|Offer methodology patterns based on current ontology or design context=No&lt;br /&gt;
|Offer other patterns based on current ontology or design context=No&lt;br /&gt;
|Integrate selected design patterns into an ontology design=No&lt;br /&gt;
|Assess correctness or performance of an ontology design=Yes&lt;br /&gt;
|Assess correctness or performance of an ontology design comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Guide and facilitate modularization of ontology=No&lt;br /&gt;
|Guide ontology design for visualization=No&lt;br /&gt;
|Choose ontology language=No&lt;br /&gt;
|Choose formal logic language=No&lt;br /&gt;
|Choose RDF support=No&lt;br /&gt;
|Mix ontology languages=No&lt;br /&gt;
|Generate ontology code from requirements specification=No&lt;br /&gt;
|Generate or enforce selected design patterns in ontology code=No&lt;br /&gt;
|Feedback on consistency of granularity and regularity of domain ontology structure=No&lt;br /&gt;
|Manage lexical naming and annotation of ontology elements=No&lt;br /&gt;
|Ensure proper use and coding of RDF and Web resources=No&lt;br /&gt;
|Enforce proper use and coding of URIs=No&lt;br /&gt;
|Produce the current terminological inferences of an ontology=No&lt;br /&gt;
|Optimize query and inference performance=No&lt;br /&gt;
|Detect violations of domain, referential, or semantic integrity=Yes&lt;br /&gt;
|Detect violations of domain, referential, or semantic integrity comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Overall, detect and correct coding errors or inconsistencies=Yes&lt;br /&gt;
|Overall, detect and correct coding errors or inconsistencies comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Ensure proper separation and coding of concepts and facts=No&lt;br /&gt;
|Ensure kind-of nature and consistency of subclassing=No&lt;br /&gt;
|Guide subclass versus class individual determinations=No&lt;br /&gt;
|Monitor depth of subclassing consistency across a domain ontology=No&lt;br /&gt;
|Generate prototypical instances (individuals) to help verify class intent and class subsumption=No&lt;br /&gt;
|Detect and guide use of multiple inheritance=No&lt;br /&gt;
|Guide use of disjointness axioms=No&lt;br /&gt;
|Guide use of necessary and sufficient properties in concept definitions=No&lt;br /&gt;
|Guide use of existential versus universal quantification in class restrictions=No&lt;br /&gt;
|Enforce proper use of conjunctions versus disjunctions=No&lt;br /&gt;
|Ensure proper use and coding of relations=Yes&lt;br /&gt;
|Ensure proper use and coding of relations comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Ensure proper use and coding of data types=No&lt;br /&gt;
|Assess and enforce consistency and completeness of range and domain constraints=No&lt;br /&gt;
|Assess and enforce consistency and completeness of inverse relations=No&lt;br /&gt;
|Ensure proper use and coding of transitive relations=No&lt;br /&gt;
|Verify that ontology requirements are met=No&lt;br /&gt;
|Assess query precision and recall performance=No&lt;br /&gt;
|Assess query time performance=No&lt;br /&gt;
|Assess inferencing time performance=No&lt;br /&gt;
|Assess inferencing completeness performance=No&lt;br /&gt;
|Generate characteristic queries and tests=No&lt;br /&gt;
|Accept validation test sets or inputs=No&lt;br /&gt;
|Assure semantically adequate computability of ontology=No&lt;br /&gt;
|Assure mathematically complete computability of ontology=No&lt;br /&gt;
|Verify that two ontologies are interoperable=No&lt;br /&gt;
|Validate the intended functionality of software using the ontology=No&lt;br /&gt;
|Validate instance data conforming to an ontology=No&lt;br /&gt;
|Assess accuracy, correctness, and completeness of ontology terminological content=Yes&lt;br /&gt;
|Assess accuracy, correctness, and completeness of ontology terminological content comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Guide or adjust ontology in accord with validation results=Yes&lt;br /&gt;
|Guide or adjust ontology in accord with validation results comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Export ontology in different languages=No&lt;br /&gt;
|Integrate ontology with other ontologies=No&lt;br /&gt;
|Integrate ontology with other information system resources=No&lt;br /&gt;
|Assess or track user experience with ontology=No&lt;br /&gt;
|Enable user to modify or extend ontology to address deficiencies=Yes&lt;br /&gt;
|Enable user to modify or extend ontology to address deficiencies comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings.&lt;br /&gt;
|Create mappings from ontologies to and from data and data sources=No&lt;br /&gt;
|Promote reuse of ontology=No&lt;br /&gt;
|Capture ontology errors during use=Yes&lt;br /&gt;
|Capture ontology errors during use comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings. &lt;br /&gt;
|Profile use of ontology elements during use=No&lt;br /&gt;
|Compare and map between ontologies=Yes&lt;br /&gt;
|Compare and map between ontologies comments=RepOSE supports detection and repairing of missing and wrong is-a structure and mappings. &lt;br /&gt;
|Track ontology changes and control versions=No&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>imported&gt;KennethBaclawski</name></author>
	</entry>
</feed>