October 18, 2003

Editing of NCI Thesaurus V 2.0 was completed on September 29, 2003.  
Release version 2.0 corresponds to 03.09d (i.e. the fourth build in September
2003) in our development cycle.

This directory contains seven files:

	ReadMe.txt		This file
	NCI_THESAURUS_license.txt	A description of the licensing terms of the NCI Thesaurus
	ThesaurusTermsofUse.htm		As above, in html format for web browsing
	ThesaurusV2_0XML.zip	The NCI Thesaurus version 2.0 in Apelon's XML format
	ThesaurusV2_0Flat.zip	The NCI Thesaurus v2.0 in flat file format
	ThesaurusV2_0OWL.zip	The NCI Thesaurus v2.0 in OWL
	ontylog.dtd		The Apelon XML's document type definition, from Apelon, Inc.

The NCI_THESAURUS_license.txt file contains the terms of use for the 
NCI Thesaurus.  Please refer to the NCI_THESAURUS_license.txt
file for the exact licensing terms. 


The zip files unpack the following files:
	ThesaurusV2_0XML.zip	ThesaurusV2_0.xml
	ThesaurusV2_0Flat.zip	ThesaurusV2_0.txt
	ThesaurusV2_0OWL.zip	Thesaurus.owl
	
In all three formats below, the ontology is in a defined state, i.e. 
relations are as stated by the editors, no inferred relations are
specified.

The ThesaurusV2_0.xml file contains the entire terminology and associated 
ontologic constructions from the NCI Thesaurus, including properties, roles, 
and kinds.  The DTD for the XML is as defined by Apelon, Inc, whose editing 
tools are being used in the construction of the Thesaurus.  Properties of 
use only to the EVS (e.g. editor notes) are absent in the released terminology. 


The ThesaurusV2_0.txt flat file is in tab-delimited format.  Included in this 
format are all the terms associated with NCI Thesaurus concepts (names and 
synonyms), a text definition of the concept (if one is present), and stated 
parent-child relations, sufficient to reconstruct the hierarchy.  The fields 
are:

	code <tab> concept name <tab> parents <tab> synonyms <tab> definition

The "parents" field contains the concept name(s) of the superconcept(s).
If a "parents" or "synonyms" field contains multiple entries, these 
are pipe-delimited.  For root concepts without "parents", this field
contains the string "root_node".  The first entry in the "synonyms" field 
is the preferred name of the concept.  If no preferred name has been stated
for the concept, this field contains the concept name.  The 
"definition" field contains only one definition if more than one 
definition is associated with the concept; not all concepts contain 
definitions.  

The Thesaurus.owl file contains the entire terminology expressed in the OWL 
web ontology language (http://www.w3.org/TR/owl-ref/), with the exception of
the Ontylog namespace declaration, which was deemed unnecessary.  The Ontylog
Roles where converted to restrictions on OWL properties, and most of the 
concept annotations in Ontylog properties were converted to OWL 
AnnotationProperty; as in the Ontylog xml file, properties of use only to 
the EVS (e.g. editor notes) are absent in the OWL file.  Because 
Roles in Ontylog are mapped from a domain kind to a range kind, the OWL 
version of the Thesaurus has each kind as a root class to facilitate the 
conversion of Roles to OWL properties.

For additional information, please see the Release Notes of caCORE 2.0.