Package com.apelon.dts.client.concept

This package provides capability to access both Ontylog and thesaurus concepts in a DTS client application.

See:
Description

Class Summary

BaseConceptQuery	BaseConceptQuery is a base class for BaseLocalConceptQuery, BaseOntylogConceptQuery, DTSConceptQuery, and SearchQuery.
BaseLocalConceptQuery	Base class for creating or deleting concepts in a local namespace.
BaseOntylogConceptQuery	The BaseOntylogConceptQuery class provides access to Ontylog concepts.
ConceptAttributeSetDescriptor	ConceptAttributeSetDescriptor is a description of the set of concept attributes that should be retrieved by a given operation.
ConceptChild	Holds a child concept and an indicator of whether the child has children.
ConceptParent	Holds a parent concept and an indicator of whether the parent has parents.
DTSConcept	A DTS concept is the basic unit of information in the terminology knowledgebasebase.
DTSConceptQuery	DTSConceptQuery is a subclass of BaseConceptQuery.
DTSSearchOptions	The DTS search options pass information to be used in a search, other that actual search pattern.
NavChildContext	Provides a navigation context for building a child tree.
NavParentContext	Provides a navigation context for building a parent tree.
NavQuery	The NavQuery class provides navigation over the Ontylog concept hierarchy.
OntylogClassQuery	OntylogClassQueryServer supports queries on subconcept relationships within an Ontylog concept hierarchy.
OntylogConcept	An Ontylog concept extends a DTS concept by adding Ontylog hierarchy and role information.
OntylogConceptQuery	OntylogConceptQuery is a subclass of BaseOntylogConceptQuery.
OntylogExtConceptQuery	OntylogExtConceptQuery is a subclass of BaseLocalConceptQuery.
OntylogNavContext	Deprecated. This class is deprecated and will be removed in a future DTS release.
SearchQuery	An SearchQuery provides search methods for searching thesaurus or Ontylog concepts.
ThesaurusConceptQuery	A ThesaurusConceptQuery class provides access to thesaurus concepts.

Package com.apelon.dts.client.concept Description

This package provides capability to access both Ontylog and thesaurus concepts in a DTS client application. The naming convention used in this package is that class names with a prefix of DTS- pertain to both Ontylog and thesaurus concepts, whereas prefixes of Ontylog- or Thesaurus- pertain to only the named type of concept. Ontylog concepts are loaded from the TDE (Terminology Development Environment) and may have roles, subconcepts, and superconcepts, which thesaurus concepts do not. Common to both Ontylog and thesaurus concepts are properties, synonyms, and associations with other concepts. Thesaurus concepts do not come from TDE, but can be created within DTS.

The client APIs are a collection of classes for accessing concept information from the server. Each is created by establishing a connection with the server and then passing the server connection to a createInstance method. The following classes comprise the DTS APIs along with a brief description of their functions:

• BaseConceptQuery
• BaseOntylogConceptQuery
• DTSConceptQuery
• NavQuery
• OntylogClassQuery
• OntylogConceptQuery
• SearchQuery
• ThesaurusConceptQuery

BaseConceptQuery is the base class for the others. In DTS, roles and properties are simplified and presented as just name/value pairs, called attributes. This is unlike TDE where Roles have semantic relevance and properties do not. This difference is motivated by the fact that in runtime read-only applications, users typically are only interested in attributes and not logical modifiers like some and all. This abstraction is handled by the class DTSAttribute. DTSConceptQuery is used to fetch Ontylog or thesaurus concepts, and their attributes. Which attributes are retrieved is customizable by specifying a ConceptAttributeSetDescriptor. One can fetch a single concept, or an array of concepts. OntylogConceptQuery adds access to role type information.

OntylogClassQuery provides answers to subsumption questions, e.g. is one concept a subconcept of another, or retrieves all descendant subconcepts of a concept. By computing the transitive closure over the database, these lookups are quite fast. NavQuery provides the ordered tree-like traversal of a taxonomy or a hierarchy implied by a chain of associations. One can fetch the roots of an Ontylog hierarchy or start with a specified concept in an association hierarchy, and for any concept fetch its immediate parents or children. For each concept retrieved, whether or not it is a leaf is also known.

Search methods common to both Ontylog and thesaurus concepts are available in SearchQuery. SearchQuery provides fetching of concepts based on matching of concept names, property, synonym, and role values. A DTSSearchOptions object is passed in each of the search methods to specify a search limit, a namespace to search in, and a ConceptAttributeSetDescriptor to indicate what extra attributes, such as properties or synonyms, to retrieve for found concepts.

ThesaurusConceptQuery provides methods for editing concepts in limited ways, such as editing their properties, syonyms, and associations.