element ISO25964Interchange
diagram iso25964-1_v1.4_p3.png
namespace http://iso25964.org/
properties
content complex
children iso25964:Thesaurus iso25964:GroupRelationship iso25964:TopLevelRelationship iso25964:AssociativeRelationship iso25964:HierarchicalRelationship iso25964:CompoundEquivalence iso25964:SplitNonPreferredTerm
attributes
Name  Type  Use  Default  Fixed  annotation
scopederived by: xsd:string  full    
identity constraints
  Name  Refer  Selector  Field(s)  
unique  uc_ThesaurusTerm    iso25964:SplitNonPreferredTerm | iso25964:Thesaurus/iso25964:ThesaurusConcept/iso25964:PreferredTerm | iso25964:Thesaurus/iso25964:ThesaurusConcept/iso25964:SimpleNonPreferredTerm  iso25964:identifier  
source <xsd:element name="ISO25964Interchange">
 
<xsd:complexType>
   
<xsd:sequence>
     
<xsd:element name="Thesaurus" type="iso25964:ThesaurusStruct" minOccurs="1" maxOccurs="1">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">There should not be more than 1 (one) "created" date. See also VersionHistory

The optional attribute @dc:source of Thesaurus and ThesaurusTerm, which can be used to note the reference work or individual who contributed the term in question.

@language should be given as an alpha-2 code selected from ISO 639-1 if present in that list, or an alpha-3 code from ISO 639-2 if not. These codes may be extended where necessary with the additional codes described in RFC 4646[45] and listed in the IANA subtag registry[35] (see 12.4.5).
</xsd:documentation>
       
</xsd:annotation>
       
<xsd:unique name="uc_ThesaurusConcept_id">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">All ThesaurusConcept-s must have a unique thesaurus concept identifier.</xsd:documentation>
         
</xsd:annotation>
         
<xsd:selector xpath="iso25964:ThesaurusConcept"/>
         
<xsd:field xpath="iso25964:identifier"/>
       
</xsd:unique>
       
<xsd:unique name="uc_ThesaurusArray_id">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">All ThesaurusArray-s must have a unique thesaurus array identifier.</xsd:documentation>
         
</xsd:annotation>
         
<xsd:selector xpath="iso25964:ThesaurusArray"/>
         
<xsd:field xpath="iso25964:identifier"/>
       
</xsd:unique>
       
<xsd:unique name="uc_ConceptGroup">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">All ConceptGroup-s must have a unique concept group identifier.</xsd:documentation>
         
</xsd:annotation>
         
<xsd:selector xpath="iso25964:ConceptGroup"/>
         
<xsd:field xpath="iso25964:identifier"/>
       
</xsd:unique>
     
</xsd:element>
     
<xsd:choice minOccurs="0" maxOccurs="unbounded">
       
<xsd:element name="GroupRelationship" type="iso25964:GroupRelationship"/>
       
<xsd:element name="TopLevelRelationship" type="iso25964:TopLevelRelationship"/>
       
<xsd:element name="AssociativeRelationship" type="iso25964:AssociativeRelationship"/>
       
<xsd:element name="HierarchicalRelationship" type="iso25964:HierarchicalRelationship"/>
       
<xsd:element name="CompoundEquivalence" type="iso25964:CompoundEquivalence">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.</xsd:documentation>
         
</xsd:annotation>
       
</xsd:element>
       
<xsd:element name="SplitNonPreferredTerm">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.

@source notes the reference work or individual who contributed the term in question
</xsd:documentation>
         
</xsd:annotation>
         
<xsd:complexType>
           
<xsd:complexContent>
             
<xsd:extension base="iso25964:ThesaurusTerm"/>
           
</xsd:complexContent>
         
</xsd:complexType>
       
</xsd:element>
     
</xsd:choice>
   
</xsd:sequence>
   
<xsd:attribute name="scope" default="full">
     
<xsd:simpleType>
       
<xsd:restriction base="xsd:string">
         
<xsd:enumeration value="full">
           
<xsd:annotation>
             
<xsd:documentation xml:lang="en">The full thesaurus is being provided in the exchange document.</xsd:documentation>
           
</xsd:annotation>
         
</xsd:enumeration>
         
<xsd:enumeration value="update-only">
           
<xsd:annotation>
             
<xsd:documentation xml:lang="en">Only the updated parts of a complete thesaurus (compared to its previous version) are provided.

Note: The schema is not fully ready to support this value yet.
</xsd:documentation>
           
</xsd:annotation>
         
</xsd:enumeration>
         
<xsd:enumeration value="custom-selection">
           
<xsd:annotation>
             
<xsd:documentation xml:lang="en">A complete custom selection has been provided of the thesaurus.
Details are specified in the VersionHistory whit thisVersion = true

Examples:
- certain subset of the thesaurs languages
- only specific concept groups are available
</xsd:documentation>
           
</xsd:annotation>
         
</xsd:enumeration>
       
</xsd:restriction>
     
</xsd:simpleType>
   
</xsd:attribute>
 
</xsd:complexType>
 
<xsd:unique name="uc_ThesaurusTerm">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">All ThesaurusTerm-s (PreferredTerm, SimpleNonPreferredTerm and SplitNonPreferredTerm) have a unique thesaurus term identifier.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:SplitNonPreferredTerm | iso25964:Thesaurus/iso25964:ThesaurusConcept/iso25964:PreferredTerm | iso25964:Thesaurus/iso25964:ThesaurusConcept/iso25964:SimpleNonPreferredTerm"/>
   
<xsd:field xpath="iso25964:identifier"/>
 
</xsd:unique>
</xsd:element>

attribute ISO25964Interchange/@scope
type restriction of xsd:string
properties
isRef 0
default full
facets
Kind Value annotation 
enumeration full 
documentation
The full thesaurus is being provided in the exchange document.
enumeration update-only 
documentation
Only the updated parts of a complete thesaurus (compared to its previous version) are provided.

Note: The schema is not fully ready to support this value yet.
enumeration custom-selection 
documentation
A complete custom selection has been provided of the thesaurus.
Details are specified in the VersionHistory whit thisVersion = true

Examples:
- certain subset of the thesaurs languages
- only specific concept groups are available
source <xsd:attribute name="scope" default="full">
 
<xsd:simpleType>
   
<xsd:restriction base="xsd:string">
     
<xsd:enumeration value="full">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">The full thesaurus is being provided in the exchange document.</xsd:documentation>
       
</xsd:annotation>
     
</xsd:enumeration>
     
<xsd:enumeration value="update-only">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">Only the updated parts of a complete thesaurus (compared to its previous version) are provided.

Note: The schema is not fully ready to support this value yet.
</xsd:documentation>
       
</xsd:annotation>
     
</xsd:enumeration>
     
<xsd:enumeration value="custom-selection">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">A complete custom selection has been provided of the thesaurus.
Details are specified in the VersionHistory whit thisVersion = true

Examples:
- certain subset of the thesaurs languages
- only specific concept groups are available
</xsd:documentation>
       
</xsd:annotation>
     
</xsd:enumeration>
   
</xsd:restriction>
 
</xsd:simpleType>
</xsd:attribute>

element ISO25964Interchange/Thesaurus
diagram iso25964-1_v1.4_p4.png
namespace http://iso25964.org/
type iso25964:ThesaurusStruct
properties
isRef 0
content complex
children iso25964:identifier contributor coverage creator iso25964:date iso25964:created iso25964:modified description format language publisher relation rights source subject title type iso25964:ThesaurusConcept iso25964:ThesaurusArray iso25964:ConceptGroup iso25964:Version
identity constraints
  Name  Refer  Selector  Field(s)  
unique  uc_ThesaurusConcept_id    iso25964:ThesaurusConcept  iso25964:identifier  
unique  uc_ThesaurusArray_id    iso25964:ThesaurusArray  iso25964:identifier  
unique  uc_ConceptGroup    iso25964:ConceptGroup  iso25964:identifier  
annotation
documentation
There should not be more than 1 (one) "created" date. See also VersionHistory

The optional attribute @dc:source of Thesaurus and ThesaurusTerm, which can be used to note the reference work or individual who contributed the term in question.

@language should be given as an alpha-2 code selected from ISO 639-1 if present in that list, or an alpha-3 code from ISO 639-2 if not. These codes may be extended where necessary with the additional codes described in RFC 4646[45] and listed in the IANA subtag registry[35] (see 12.4.5).
source <xsd:element name="Thesaurus" type="iso25964:ThesaurusStruct" minOccurs="1" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">There should not be more than 1 (one) "created" date. See also VersionHistory

The optional attribute @dc:source of Thesaurus and ThesaurusTerm, which can be used to note the reference work or individual who contributed the term in question.

@language should be given as an alpha-2 code selected from ISO 639-1 if present in that list, or an alpha-3 code from ISO 639-2 if not. These codes may be extended where necessary with the additional codes described in RFC 4646[45] and listed in the IANA subtag registry[35] (see 12.4.5).
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:unique name="uc_ThesaurusConcept_id">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">All ThesaurusConcept-s must have a unique thesaurus concept identifier.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:ThesaurusConcept"/>
   
<xsd:field xpath="iso25964:identifier"/>
 
</xsd:unique>
 
<xsd:unique name="uc_ThesaurusArray_id">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">All ThesaurusArray-s must have a unique thesaurus array identifier.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:ThesaurusArray"/>
   
<xsd:field xpath="iso25964:identifier"/>
 
</xsd:unique>
 
<xsd:unique name="uc_ConceptGroup">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">All ConceptGroup-s must have a unique concept group identifier.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:ConceptGroup"/>
   
<xsd:field xpath="iso25964:identifier"/>
 
</xsd:unique>
</xsd:element>

element ISO25964Interchange/GroupRelationship
diagram iso25964-1_v1.4_p5.png
namespace http://iso25964.org/
type iso25964:GroupRelationship
properties
isRef 0
content complex
children iso25964:hasSubGroup iso25964:hasSuperGroup
source <xsd:element name="GroupRelationship" type="iso25964:GroupRelationship"/>

element ISO25964Interchange/TopLevelRelationship
diagram iso25964-1_v1.4_p6.png
namespace http://iso25964.org/
type iso25964:TopLevelRelationship
properties
isRef 0
content complex
children iso25964:hasTopConcept iso25964:isTopConceptOf
source <xsd:element name="TopLevelRelationship" type="iso25964:TopLevelRelationship"/>

element ISO25964Interchange/AssociativeRelationship
diagram iso25964-1_v1.4_p7.png
namespace http://iso25964.org/
type iso25964:AssociativeRelationship
properties
isRef 0
content complex
children iso25964:role iso25964:hasRelatedConcept iso25964:isRelatedConcept
source <xsd:element name="AssociativeRelationship" type="iso25964:AssociativeRelationship"/>

element ISO25964Interchange/HierarchicalRelationship
diagram iso25964-1_v1.4_p8.png
namespace http://iso25964.org/
type iso25964:HierarchicalRelationship
properties
isRef 0
content complex
children iso25964:role iso25964:hasHierRelConcept iso25964:isHierRelConcept
source <xsd:element name="HierarchicalRelationship" type="iso25964:HierarchicalRelationship"/>

element ISO25964Interchange/CompoundEquivalence
diagram iso25964-1_v1.4_p9.png
namespace http://iso25964.org/
type iso25964:CompoundEquivalence
properties
isRef 0
content complex
children iso25964:UFPlus iso25964:USEPlus
annotation
documentation
The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.
source <xsd:element name="CompoundEquivalence" type="iso25964:CompoundEquivalence">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ISO25964Interchange/SplitNonPreferredTerm
diagram iso25964-1_v1.4_p10.png
namespace http://iso25964.org/
type extension of iso25964:ThesaurusTerm
properties
isRef 0
content complex
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute
annotation
documentation
The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.

@source notes the reference work or individual who contributed the term in question
source <xsd:element name="SplitNonPreferredTerm">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The classes SplitNonPreferredTerm and CompoundEquivalence enable representation of complex concepts by a combination of terms, as described in 8.5.

@source notes the reference work or individual who contributed the term in question
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:complexType>
   
<xsd:complexContent>
     
<xsd:extension base="iso25964:ThesaurusTerm"/>
   
</xsd:complexContent>
 
</xsd:complexType>
</xsd:element>


XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy