<?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=XD_Tools</id>
	<title>XD Tools - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://ontologforum.com/index.php?action=history&amp;feed=atom&amp;title=XD_Tools"/>
	<link rel="alternate" type="text/html" href="https://ontologforum.com/index.php?title=XD_Tools&amp;action=history"/>
	<updated>2026-05-04T15:06:21Z</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=XD_Tools&amp;diff=2743&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=XD_Tools&amp;diff=2743&amp;oldid=prev"/>
		<updated>2016-01-09T08:52:58Z</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=eXtreme Design Tools&lt;br /&gt;
|Description of the tool=The tool provides a perspective - eXtreme Design - that groups all the user components: the ODP Registry browser and ODP Details view, the XD Selector. Other components can be activated in several ways within the interface, i.e. the XD Specialization Wizard, the XD Analyzer and the XD Annotation dialog.&lt;br /&gt;
&lt;br /&gt;
    ODP Registry and ODP Details view: through this view users can have access to a set of reusable OWL patterns that can be directly browsed and exploited in the modelling process, without necessarily having them locally stored. When a pattern is selected from the registry tree, all OWL annotations are visualised in the ODP Details view;&lt;br /&gt;
    XD Selector: The aim is to give support to the end-user with a component for proposing patterns to be reused to cover requirements expressed as competency questions. The user can query these basic selection services providing either simple keywords or a complete competency question (CQ). The XD Selector view displays as result a list of proposed ODPs to be reused in the current working ontology. By click on a result, details (ontology annotations) are shown in the ODP Details view.&lt;br /&gt;
    Specialization Wizard: The Specialization wizard is the component provided by XD Tools for guiding the user in the specialisation of Content ODPs. The wizard can be accessed either from the Navigation view, i.e. through the contextual menu activated while right-clicking on an ontology, from the ODP Registry view or from XD Selector's results view. When the process is finalised, a message is displayed with the option to open the dialog for ontology annotation, i.e. to annotate the new ontology module that has been created.&lt;br /&gt;
    XD Annotation dialog: It provides the facility to annotate the ontology using other vocabularies in addition to the annotation properties already provided by OWL/RDF. For the Content ODPs the CPAnnotationSchema[1] is supported[2]&lt;br /&gt;
    XD Analyzer: The aim of this tool is to provide suggestions and feedback to the user with respect to how good practices in ontology design have been followed, according to the XD methodology (for instance missing labels and comments, isolated entities, unused imported ontologies).&lt;br /&gt;
&lt;br /&gt;
|Link to the tool=http://stlab.istc.cnr.it/documents/XD/documentation/1.1/&lt;br /&gt;
|Tool home page=http://stlab.istc.cnr.it/stlab/XDTools&lt;br /&gt;
|Download page=http://extremedesign.sourceforge.net&lt;br /&gt;
|Author=Valentina Presutti, Aldo Gangemi, Enrico Daga, Eva Blomqvist&lt;br /&gt;
|Contact=valentina.presutti@cnr.it&lt;br /&gt;
|Institutional sponsor=CNR&lt;br /&gt;
|Find ontologies with specific domain coverage=Yes&lt;br /&gt;
|Find ontologies with specific domain coverage comments=In the context of the [[NeOn]] Toolkit (Watson plugin)&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=Yes&lt;br /&gt;
|Assess complexity of concept definitions (necessary and sufficient properties) and use of axioms comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Identify number and ratio of concepts, relations, and subclassing=Yes&lt;br /&gt;
|Identify number and ratio of concepts, relations, and subclassing comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Identify frequency of use of ontology language features in an ontology=Yes&lt;br /&gt;
|Identify frequency of use of ontology language features in an ontology comments=In the context of the [[NeOn]] Toolkit&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=Yes&lt;br /&gt;
|Assess the inferencing power of an ontology comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Rate ontologies on their popularity or review feedback=Yes&lt;br /&gt;
|Rate ontologies on their popularity or review feedback comments=In the context of the [[NeOn]] Toolkit&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;
|Organize and maintain a collection of related ontologies and ontology modules comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Provide statistics on ontology versioning and use=No&lt;br /&gt;
|Provide statistics on ontology versioning and use comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Guide ontology development per a quality assurance methodology=Yes&lt;br /&gt;
|Assess the reusability of a planned ontology=No&lt;br /&gt;
|Guide formulation of domain scope and detail requirements=Yes&lt;br /&gt;
|Guide formulation of goodness of design requirements=Yes&lt;br /&gt;
|Guide formulation of data and information requirements=Yes&lt;br /&gt;
|Guide formulation of semantic and reasoning requirements=Yes&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=Yes&lt;br /&gt;
|Choose metaphysical methodology=No&lt;br /&gt;
|Choose extant top ontology for reuse=Yes&lt;br /&gt;
|Choose extant top ontology for reuse comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Choose extant core ontologies for reuse=Yes&lt;br /&gt;
|Choose extant core ontologies for reuse comments=In the context of the [[NeOn]] Toolkit&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=Yes&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=Yes&lt;br /&gt;
|Offer ontology language patterns based on current ontology or design context=Yes&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=Yes&lt;br /&gt;
|Integrate selected design patterns into an ontology design=Yes&lt;br /&gt;
|Assess correctness or performance of an ontology design=Yes&lt;br /&gt;
|Guide and facilitate modularization of ontology=Yes&lt;br /&gt;
|Guide ontology design for visualization=No&lt;br /&gt;
|Choose ontology language=No&lt;br /&gt;
|Choose formal logic language=Yes&lt;br /&gt;
|Choose RDF support=Yes&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=Yes&lt;br /&gt;
|Feedback on consistency of granularity and regularity of domain ontology structure=Yes&lt;br /&gt;
|Manage lexical naming and annotation of ontology elements=Yes&lt;br /&gt;
|Ensure proper use and coding of RDF and Web resources=Yes&lt;br /&gt;
|Enforce proper use and coding of URIs=Yes&lt;br /&gt;
|Produce the current terminological inferences of an ontology=No&lt;br /&gt;
|Optimize query and inference performance=Yes&lt;br /&gt;
|Detect violations of domain, referential, or semantic integrity=Yes&lt;br /&gt;
|Overall, detect and correct coding errors or inconsistencies=Yes&lt;br /&gt;
|Overall, detect and correct coding errors or inconsistencies comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Ensure proper separation and coding of concepts and facts=Yes&lt;br /&gt;
|Ensure proper separation and coding of concepts and facts comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Ensure kind-of nature and consistency of subclassing=No&lt;br /&gt;
|Guide subclass versus class individual determinations=Yes&lt;br /&gt;
|Guide subclass versus class individual determinations comments=In the context of the [[NeOn]] Toolkit&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=Yes&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=Yes&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 data types=Yes&lt;br /&gt;
|Assess and enforce consistency and completeness of range and domain constraints=Yes&lt;br /&gt;
|Assess and enforce consistency and completeness of inverse relations=Yes&lt;br /&gt;
|Ensure proper use and coding of transitive relations=Yes&lt;br /&gt;
|Verify that ontology requirements are met=Yes&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=Yes&lt;br /&gt;
|Assess inferencing time performance comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Assess inferencing completeness performance=Yes&lt;br /&gt;
|Assess inferencing completeness performance comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Generate characteristic queries and tests=No&lt;br /&gt;
|Accept validation test sets or inputs=Yes&lt;br /&gt;
|Assure semantically adequate computability of ontology=No&lt;br /&gt;
|Assure mathematically complete computability of ontology=Yes&lt;br /&gt;
|Assure mathematically complete computability of ontology comments=In the context of the [[NeOn]] Toolkit&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=Yes&lt;br /&gt;
|Validate instance data conforming to an ontology comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Assess accuracy, correctness, and completeness of ontology terminological content=No&lt;br /&gt;
|Guide or adjust ontology in accord with validation results=Yes&lt;br /&gt;
|Export ontology in different languages=Yes&lt;br /&gt;
|Export ontology in different languages comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Integrate ontology with other ontologies=Yes&lt;br /&gt;
|Integrate ontology with other ontologies comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Integrate ontology with other information system resources=Yes&lt;br /&gt;
|Integrate ontology with other information system resources comments=In the context of the [[NeOn]] Toolkit&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;
|Create mappings from ontologies to and from data and data sources=Yes&lt;br /&gt;
|Create mappings from ontologies to and from data and data sources comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Promote reuse of ontology=Yes&lt;br /&gt;
|Capture ontology errors during use=Yes&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=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
|Track ontology changes and control versions=Yes&lt;br /&gt;
|Track ontology changes and control versions comments=In the context of the [[NeOn]] Toolkit&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>imported&gt;KennethBaclawski</name></author>
	</entry>
</feed>