Schema iso25964-1_v1.4.xsd


schema location:  ..\iso25964-1_v1.4.xsd
attribute form default:  unqualified
element form default:  qualified
targetNamespace:  http://iso25964.org/
 
Elements  Groups  Complex types  Simple types 
created  ThesaurusMetadataGroup  AssociativeRelationship  date 
date  CompoundEquivalence  Identifier 
ISO25964Interchange  ConceptGroupLabel 
lexicalValue  ConceptGroupStruct 
modified  CustomConceptAttribute 
CustomNote 
CustomTermAttribute 
Definition 
EditorialNote 
GroupRelationship 
HierarchicalRelationship 
HistoryNote 
NodeLabel 
Note 
PreferredTerm 
ScopeNote 
SimpleNonPreferredTerm 
SplitNonPreferredTerm 
ThesaurusArrayStruct 
ThesaurusConceptStruct 
ThesaurusStruct 
ThesaurusTerm 
TopLevelRelationship 
VersionHistory 


schema location:  http://dublincore.org/schemas/xmls/qdc/2008/02/11/dc.xsd
attribute form default:  unqualified
element form default:  qualified
targetNamespace:  http://purl.org/dc/elements/1.1/
 
Elements  Groups  Complex types 
any  elementsGroup  elementContainer 
contributor  SimpleLiteral 
coverage 
creator 
date 
description 
format 
identifier 
language 
publisher 
relation 
rights 
source 
subject 
title 
type 


schema location:  altova://ystream/xml.xsd
attribute form default: 
element form default: 
targetNamespace:  http://www.w3.org/XML/1998/namespace
 
Attributes  Attr. groups 
base  specialAttrs 
id 
lang 
space 


element created
diagram iso25964-1_v1.4_p1.png
namespace http://iso25964.org/
type iso25964:date
properties
content simple
used by
complexTypes ConceptGroupLabel NodeLabel Note ThesaurusConceptStruct ThesaurusTerm
group ThesaurusMetadataGroup
source <xsd:element name="created" type="iso25964:date"/>

element date
diagram iso25964-1_v1.4_p2.png
namespace http://iso25964.org/
type iso25964:date
properties
content simple
used by
complexType VersionHistory
group ThesaurusMetadataGroup
source <xsd:element name="date" type="iso25964:date"/>

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>

element lexicalValue
diagram iso25964-1_v1.4_p11.png
namespace http://iso25964.org/
type extension of xsd:string
properties
content complex
used by
complexTypes ConceptGroupLabel CustomConceptAttribute CustomTermAttribute NodeLabel Note ThesaurusTerm
attributes
Name  Type  Use  Default  Fixed  annotation
langderived by: xsd:language      
documentation
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="lexicalValue">
 
<xsd:complexType>
   
<xsd:simpleContent>
     
<xsd:extension base="xsd:string">
       
<xsd:attribute ref="xml:lang">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">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:attribute>
     
</xsd:extension>
   
</xsd:simpleContent>
 
</xsd:complexType>
</xsd:element>

element modified
diagram iso25964-1_v1.4_p12.png
namespace http://iso25964.org/
type iso25964:date
properties
content simple
used by
complexTypes ConceptGroupLabel NodeLabel Note ThesaurusConceptStruct ThesaurusTerm
group ThesaurusMetadataGroup
source <xsd:element name="modified" type="iso25964:date"/>

group ThesaurusMetadataGroup
diagram iso25964-1_v1.4_p13.png
namespace http://iso25964.org/
children iso25964:identifier contributor coverage creator iso25964:date iso25964:created iso25964:modified description format language publisher relation rights source subject title type
used by
complexType ThesaurusStruct
source <xsd:group name="ThesaurusMetadataGroup">
 
<xsd:sequence>
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">Metadata sheet</xsd:documentation>
   
</xsd:annotation>
   
<xsd:element name="identifier" type="iso25964:Identifier" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Identifier for the thesaurus as a whole</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:contributor" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Person or organization who contributed to the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:coverage" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Spatial or temporal coverage of the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:creator" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Person or organization primarily responsible for making</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="iso25964:date" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Any date associated with the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="iso25964:created" minOccurs="0">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The date the thesaurus was created</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="iso25964:modified" minOccurs="0">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A date when this version was modified</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:description" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">An account of the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:format" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The file format or physical medium of the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:language" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Codes showing languages supported by the thesaurus

It 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 and listed in the IANA subtag registry (see section 12.4.5 of the standard).
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:publisher" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Entity responsible for publication</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:relation" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A related publication</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:rights" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Copyright or other rights information</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:source" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Resource from which the thesaurus was derived

Used by a thesaurus variant to refer the URI of the original thesaurus for which it is a variant.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:subject" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Index terms indicating the subject content</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:title" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Title of the thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element ref="dc:type" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The genre of the vocabulary, e.g. "thesaurus"</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:group>

element ThesaurusMetadataGroup/identifier
diagram iso25964-1_v1.4_p14.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 1
maxOcc unbounded
content simple
annotation
documentation
Identifier for the thesaurus as a whole
source <xsd:element name="identifier" type="iso25964:Identifier" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Identifier for the thesaurus as a whole</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType AssociativeRelationship
diagram iso25964-1_v1.4_p15.png
namespace http://iso25964.org/
children iso25964:role iso25964:hasRelatedConcept iso25964:isRelatedConcept
used by
element ISO25964Interchange/AssociativeRelationship
source <xsd:complexType name="AssociativeRelationship">
 
<xsd:sequence>
   
<xsd:element name="role" type="xsd:string" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The typical (and implied) associative relationship role is: RT

Associative Relationship role types should form a controlled vocabulary.
If subtypes of RT are defined, hierarchical levels should be separated by a solidus (forward slash): /
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="hasRelatedConcept" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of the related thesaurus concept of the associative relationship.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="isRelatedConcept" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of the thesaurus concept for which the associative relation is specified.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element AssociativeRelationship/role
diagram iso25964-1_v1.4_p16.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
The typical (and implied) associative relationship role is: RT

Associative Relationship role types should form a controlled vocabulary.
If subtypes of RT are defined, hierarchical levels should be separated by a solidus (forward slash): /
source <xsd:element name="role" type="xsd:string" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The typical (and implied) associative relationship role is: RT

Associative Relationship role types should form a controlled vocabulary.
If subtypes of RT are defined, hierarchical levels should be separated by a solidus (forward slash): /
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element AssociativeRelationship/hasRelatedConcept
diagram iso25964-1_v1.4_p17.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of the related thesaurus concept of the associative relationship.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
source <xsd:element name="hasRelatedConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of the related thesaurus concept of the associative relationship.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element AssociativeRelationship/isRelatedConcept
diagram iso25964-1_v1.4_p18.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of the thesaurus concept for which the associative relation is specified.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
source <xsd:element name="isRelatedConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of the thesaurus concept for which the associative relation is specified.

Example: "sport event" RT "sport manifestation"
- ./role = RT
- ./isRelatedConcept = identifier of the concept with Preferred Term "sport event"
- ./hasRelatedConcept = identifier of the concept with Preferred Term "sport manifestation"
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType CompoundEquivalence
diagram iso25964-1_v1.4_p19.png
namespace http://iso25964.org/
children iso25964:UFPlus iso25964:USEPlus
used by
element ISO25964Interchange/CompoundEquivalence
source <xsd:complexType name="CompoundEquivalence">
 
<xsd:sequence>
   
<xsd:element name="UFPlus" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Identifier of the SplitNonPreferredTerm.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="USEPlus" type="iso25964:Identifier" minOccurs="2" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Identifier of (one of ) the preferred term(s).</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element CompoundEquivalence/UFPlus
diagram iso25964-1_v1.4_p20.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
Identifier of the SplitNonPreferredTerm.
source <xsd:element name="UFPlus" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Identifier of the SplitNonPreferredTerm.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element CompoundEquivalence/USEPlus
diagram iso25964-1_v1.4_p21.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 2
maxOcc unbounded
content simple
annotation
documentation
Identifier of (one of ) the preferred term(s).
source <xsd:element name="USEPlus" type="iso25964:Identifier" minOccurs="2" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Identifier of (one of ) the preferred term(s).</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType ConceptGroupLabel
diagram iso25964-1_v1.4_p22.png
namespace http://iso25964.org/
children iso25964:lexicalValue iso25964:created iso25964:modified
used by
element ConceptGroupStruct/ConceptGroupLabel
source <xsd:complexType name="ConceptGroupLabel">
 
<xsd:sequence>
   
<xsd:element ref="iso25964:lexicalValue" minOccurs="1" maxOccurs="1"/>
   
<xsd:element ref="iso25964:created" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:modified" minOccurs="0" maxOccurs="1"/>
 
</xsd:sequence>
</xsd:complexType>

complexType ConceptGroupStruct
diagram iso25964-1_v1.4_p23.png
namespace http://iso25964.org/
children iso25964:identifier iso25964:conceptGroupType iso25964:notation iso25964:Member iso25964:ConceptGroupLabel
used by
element ThesaurusStruct/ConceptGroup
source <xsd:complexType name="ConceptGroupStruct">
 
<xsd:sequence>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>
   
<xsd:element name="conceptGroupType" type="xsd:string" minOccurs="1" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A label identifying the type of group, e.g. "microthesaurus", "theme", or "subject category"</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="Member" type="iso25964:Identifier" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of the concepts belonging to the concept group.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="ConceptGroupLabel" type="iso25964:ConceptGroupLabel" minOccurs="1" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A label providing a verbal description of the group. A group should have one label per language.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element ConceptGroupStruct/identifier
diagram iso25964-1_v1.4_p24.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>

element ConceptGroupStruct/conceptGroupType
diagram iso25964-1_v1.4_p25.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
content simple
annotation
documentation
A label identifying the type of group, e.g. "microthesaurus", "theme", or "subject category"
source <xsd:element name="conceptGroupType" type="xsd:string" minOccurs="1" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A label identifying the type of group, e.g. "microthesaurus", "theme", or "subject category"</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ConceptGroupStruct/notation
diagram iso25964-1_v1.4_p26.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc unbounded
content simple
annotation
documentation
This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
source <xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ConceptGroupStruct/Member
diagram iso25964-1_v1.4_p27.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 0
maxOcc unbounded
content simple
annotation
documentation
The identifier of the concepts belonging to the concept group.
source <xsd:element name="Member" type="iso25964:Identifier" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of the concepts belonging to the concept group.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ConceptGroupStruct/ConceptGroupLabel
diagram iso25964-1_v1.4_p28.png
namespace http://iso25964.org/
type iso25964:ConceptGroupLabel
properties
isRef 0
minOcc 1
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified
annotation
documentation
A label providing a verbal description of the group. A group should have one label per language.
source <xsd:element name="ConceptGroupLabel" type="iso25964:ConceptGroupLabel" minOccurs="1" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A label providing a verbal description of the group. A group should have one label per language.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType CustomConceptAttribute
diagram iso25964-1_v1.4_p29.png
namespace http://iso25964.org/
children iso25964:lexicalValue iso25964:customAttributeType
used by
element ThesaurusConceptStruct/CustomConceptAttribute
source <xsd:complexType name="CustomConceptAttribute">
 
<xsd:sequence>
   
<xsd:element ref="iso25964:lexicalValue"/>
   
<xsd:element name="customAttributeType" type="xsd:string"/>
 
</xsd:sequence>
</xsd:complexType>

element CustomConceptAttribute/customAttributeType
diagram iso25964-1_v1.4_p30.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
content simple
source <xsd:element name="customAttributeType" type="xsd:string"/>

complexType CustomNote
diagram iso25964-1_v1.4_p31.png
namespace http://iso25964.org/
type extension of iso25964:Note
properties
base iso25964:Note
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo iso25964:noteType
used by
element ThesaurusConceptStruct/CustomNote
source <xsd:complexType name="CustomNote">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:Note">
     
<xsd:sequence>
       
<xsd:element name="noteType" type="xsd:string" minOccurs="0"/>
     
</xsd:sequence>
   
</xsd:extension>
 
</xsd:complexContent>
</xsd:complexType>

element CustomNote/noteType
diagram iso25964-1_v1.4_p32.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
source <xsd:element name="noteType" type="xsd:string" minOccurs="0"/>

complexType CustomTermAttribute
diagram iso25964-1_v1.4_p33.png
namespace http://iso25964.org/
children iso25964:lexicalValue iso25964:customAttributeType
used by
element ThesaurusTerm/CustomTermAttribute
source <xsd:complexType name="CustomTermAttribute">
 
<xsd:sequence>
   
<xsd:element ref="iso25964:lexicalValue"/>
   
<xsd:element name="customAttributeType" type="xsd:string"/>
 
</xsd:sequence>
</xsd:complexType>

element CustomTermAttribute/customAttributeType
diagram iso25964-1_v1.4_p34.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
content simple
source <xsd:element name="customAttributeType" type="xsd:string"/>

complexType Definition
diagram iso25964-1_v1.4_p35.png
namespace http://iso25964.org/
type extension of iso25964:Note
properties
base iso25964:Note
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo source
used by
element ThesaurusTerm/Definition
source <xsd:complexType name="Definition">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:Note">
     
<xsd:sequence>
       
<xsd:element ref="dc:source" minOccurs="0" maxOccurs="1">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">The person(s) or document(s) from which the definition was taken</xsd:documentation>
         
</xsd:annotation>
       
</xsd:element>
     
</xsd:sequence>
   
</xsd:extension>
 
</xsd:complexContent>
</xsd:complexType>

complexType EditorialNote
diagram iso25964-1_v1.4_p36.png
namespace http://iso25964.org/
type extension of iso25964:Note
properties
base iso25964:Note
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
used by
element ThesaurusTerm/EditorialNote
source <xsd:complexType name="EditorialNote">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:Note"/>
 
</xsd:complexContent>
</xsd:complexType>

complexType GroupRelationship
diagram iso25964-1_v1.4_p37.png
namespace http://iso25964.org/
children iso25964:hasSubGroup iso25964:hasSuperGroup
used by
element ISO25964Interchange/GroupRelationship
source <xsd:complexType name="GroupRelationship">
 
<xsd:sequence>
   
<xsd:element name="hasSubGroup" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a ConceptGroup that is a sub-group of ../hasSuperGroup.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="hasSuperGroup" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a ConceptGroup that is a super-group of ../hasSubGroup.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element GroupRelationship/hasSubGroup
diagram iso25964-1_v1.4_p38.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a ConceptGroup that is a sub-group of ../hasSuperGroup.
source <xsd:element name="hasSubGroup" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a ConceptGroup that is a sub-group of ../hasSuperGroup.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element GroupRelationship/hasSuperGroup
diagram iso25964-1_v1.4_p39.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a ConceptGroup that is a super-group of ../hasSubGroup.
source <xsd:element name="hasSuperGroup" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a ConceptGroup that is a super-group of ../hasSubGroup.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType HierarchicalRelationship
diagram iso25964-1_v1.4_p40.png
namespace http://iso25964.org/
children iso25964:role iso25964:hasHierRelConcept iso25964:isHierRelConcept
used by
element ISO25964Interchange/HierarchicalRelationship
source <xsd:complexType name="HierarchicalRelationship">
 
<xsd:sequence>
   
<xsd:element name="role" type="xsd:string" minOccurs="1" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">For custom relationship types, the text given in the "role" attribute should be composed of (a) the name of the parent relationship type, followed by (b) the symbol forward slash "/", and finally (c) the name of the custom relationship type. If necessary, custom relationship types can be subdivided further in the same way.

The text in the 'role' attribute of HierarchicalRelationship may be one of the following, where NTX indicates some further subdivision of NTI:
NT
NT/NTP
NT/NTI
NT/NTG
NT/NTI/NTX
BT
BT/BTP
BT/BTI
BT/BTG
BT/BTI/BTX
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="hasHierRelConcept" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept identifed by a hierarchical relationship.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="isHierRelConcept" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept for which the hierarchical relationship is defined.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element HierarchicalRelationship/role
diagram iso25964-1_v1.4_p41.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
content simple
annotation
documentation
For custom relationship types, the text given in the "role" attribute should be composed of (a) the name of the parent relationship type, followed by (b) the symbol forward slash "/", and finally (c) the name of the custom relationship type. If necessary, custom relationship types can be subdivided further in the same way.

The text in the 'role' attribute of HierarchicalRelationship may be one of the following, where NTX indicates some further subdivision of NTI:
NT
NT/NTP
NT/NTI
NT/NTG
NT/NTI/NTX
BT
BT/BTP
BT/BTI
BT/BTG
BT/BTI/BTX
source <xsd:element name="role" type="xsd:string" minOccurs="1" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">For custom relationship types, the text given in the "role" attribute should be composed of (a) the name of the parent relationship type, followed by (b) the symbol forward slash "/", and finally (c) the name of the custom relationship type. If necessary, custom relationship types can be subdivided further in the same way.

The text in the 'role' attribute of HierarchicalRelationship may be one of the following, where NTX indicates some further subdivision of NTI:
NT
NT/NTP
NT/NTI
NT/NTG
NT/NTI/NTX
BT
BT/BTP
BT/BTI
BT/BTG
BT/BTI/BTX
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element HierarchicalRelationship/hasHierRelConcept
diagram iso25964-1_v1.4_p42.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a thesaurus concept identifed by a hierarchical relationship.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
source <xsd:element name="hasHierRelConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept identifed by a hierarchical relationship.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element HierarchicalRelationship/isHierRelConcept
diagram iso25964-1_v1.4_p43.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a thesaurus concept for which the hierarchical relationship is defined.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
source <xsd:element name="isHierRelConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept for which the hierarchical relationship is defined.

Example: in the relationship "cow milk" BT "milk":
- ./role = BT
- ./isHierRelConcept = identifier of concept with Preferred Term "cow milk"
- ./hasHierRelConcept = identifier of concept with Preferred Term "milk"
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType HistoryNote
diagram iso25964-1_v1.4_p44.png
namespace http://iso25964.org/
type extension of iso25964:Note
properties
base iso25964:Note
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
used by
elements ThesaurusConceptStruct/HistoryNote ThesaurusTerm/HistoryNote
source <xsd:complexType name="HistoryNote">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:Note"/>
 
</xsd:complexContent>
</xsd:complexType>

complexType NodeLabel
diagram iso25964-1_v1.4_p45.png
namespace http://iso25964.org/
children iso25964:lexicalValue iso25964:created iso25964:modified
used by
element ThesaurusArrayStruct/NodeLabel
source <xsd:complexType name="NodeLabel">
 
<xsd:sequence>
   
<xsd:element ref="iso25964:lexicalValue" minOccurs="1" maxOccurs="1"/>
   
<xsd:element ref="iso25964:created" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:modified" minOccurs="0" maxOccurs="1"/>
 
</xsd:sequence>
</xsd:complexType>

complexType Note
diagram iso25964-1_v1.4_p46.png
namespace http://iso25964.org/
properties
abstract true
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
used by
complexTypes CustomNote Definition EditorialNote HistoryNote ScopeNote
annotation
documentation
@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:complexType name="Note" abstract="true">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">@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:sequence>
   
<xsd:element ref="iso25964:lexicalValue" minOccurs="1" maxOccurs="1"/>
   
<xsd:element ref="iso25964:created" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:modified" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The date when the note was last modified</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="0" maxOccurs="1"/>
   
<xsd:element name="refersTo" type="iso25964:Identifier" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The association between Note and ThesaurusConcept enables any note for one concept to refer to any other concept in the thesaurus. This capability is particularly useful for scope notes (see 5.3).</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element Note/identifier
diagram iso25964-1_v1.4_p47.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 0
maxOcc 1
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="0" maxOccurs="1"/>

element Note/refersTo
diagram iso25964-1_v1.4_p48.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 0
maxOcc unbounded
content simple
annotation
documentation
The association between Note and ThesaurusConcept enables any note for one concept to refer to any other concept in the thesaurus. This capability is particularly useful for scope notes (see 5.3).
source <xsd:element name="refersTo" type="iso25964:Identifier" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The association between Note and ThesaurusConcept enables any note for one concept to refer to any other concept in the thesaurus. This capability is particularly useful for scope notes (see 5.3).</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType PreferredTerm
diagram iso25964-1_v1.4_p49.png
namespace http://iso25964.org/
type extension of iso25964:ThesaurusTerm
properties
base iso25964:ThesaurusTerm
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute
used by
element ThesaurusConceptStruct/PreferredTerm
source <xsd:complexType name="PreferredTerm">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:ThesaurusTerm"/>
 
</xsd:complexContent>
</xsd:complexType>

complexType ScopeNote
diagram iso25964-1_v1.4_p50.png
namespace http://iso25964.org/
type extension of iso25964:Note
properties
base iso25964:Note
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
used by
element ThesaurusConceptStruct/ScopeNote
source <xsd:complexType name="ScopeNote">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:Note"/>
 
</xsd:complexContent>
</xsd:complexType>

complexType SimpleNonPreferredTerm
diagram iso25964-1_v1.4_p51.png
namespace http://iso25964.org/
type extension of iso25964:ThesaurusTerm
properties
base iso25964:ThesaurusTerm
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute iso25964:hidden iso25964:role
used by
element ThesaurusConceptStruct/SimpleNonPreferredTerm
source <xsd:complexType name="SimpleNonPreferredTerm">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:ThesaurusTerm">
     
<xsd:sequence>
       
<xsd:element name="hidden" type="xsd:boolean" minOccurs="0" maxOccurs="1">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">A yes/no flag to show whether the term may be excluded from some forms of output, e.g. for misspellings of a term.</xsd:documentation>
         
</xsd:annotation>
       
</xsd:element>
       
<xsd:element name="role" type="xsd:string" minOccurs="0" maxOccurs="1">
         
<xsd:annotation>
           
<xsd:documentation xml:lang="en">Specification of a kind of equivalence relationship. This will normally be USE, linking the source SimpleNonPreferredTerm to the target PreferredTerm</xsd:documentation>
         
</xsd:annotation>
       
</xsd:element>
     
</xsd:sequence>
   
</xsd:extension>
 
</xsd:complexContent>
</xsd:complexType>

element SimpleNonPreferredTerm/hidden
diagram iso25964-1_v1.4_p52.png
namespace http://iso25964.org/
type xsd:boolean
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
A yes/no flag to show whether the term may be excluded from some forms of output, e.g. for misspellings of a term.
source <xsd:element name="hidden" type="xsd:boolean" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A yes/no flag to show whether the term may be excluded from some forms of output, e.g. for misspellings of a term.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element SimpleNonPreferredTerm/role
diagram iso25964-1_v1.4_p53.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
Specification of a kind of equivalence relationship. This will normally be USE, linking the source SimpleNonPreferredTerm to the target PreferredTerm
source <xsd:element name="role" type="xsd:string" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Specification of a kind of equivalence relationship. This will normally be USE, linking the source SimpleNonPreferredTerm to the target PreferredTerm</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType SplitNonPreferredTerm
diagram iso25964-1_v1.4_p54.png
namespace http://iso25964.org/
type extension of iso25964:ThesaurusTerm
properties
base iso25964:ThesaurusTerm
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute
source <xsd:complexType name="SplitNonPreferredTerm">
 
<xsd:complexContent>
   
<xsd:extension base="iso25964:ThesaurusTerm"/>
 
</xsd:complexContent>
</xsd:complexType>

complexType ThesaurusArrayStruct
diagram iso25964-1_v1.4_p55.png
namespace http://iso25964.org/
children iso25964:identifier iso25964:ordered iso25964:notation iso25964:NodeLabel iso25964:hasSuperOrdinateConcept iso25964:hasSuperOrdinateArray iso25964:hasMemberConcept iso25964:hasMemberArray
used by
element ThesaurusStruct/ThesaurusArray
source <xsd:complexType name="ThesaurusArrayStruct">
 
<xsd:sequence>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>
   
<xsd:element name="ordered" type="xsd:boolean">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The value 'true' indicates that the concepts and sub-arrays of the array are ordered.  This imposed order is reflected by the XML document order of the XML document instance.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="NodeLabel" type="iso25964:NodeLabel" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">@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:element>
   
<xsd:choice minOccurs="0">
     
<xsd:element name="hasSuperOrdinateConcept" type="iso25964:Identifier">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">The identifier of the thesaurus concept under which this array appears.
(case that this array is not a sub-array)
</xsd:documentation>
       
</xsd:annotation>
     
</xsd:element>
     
<xsd:element name="hasSuperOrdinateArray" type="iso25964:Identifier">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">The identifier of the thesaurus array under which this thesaurus sub-array appears.
(case that this array is a sub-array)
</xsd:documentation>
       
</xsd:annotation>
     
</xsd:element>
   
</xsd:choice>
   
<xsd:choice maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">If the thesaurus array is ordered the member identifiers are listed in the order required for the array.</xsd:documentation>
     
</xsd:annotation>
     
<xsd:element name="hasMemberConcept" type="iso25964:Identifier">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">The identifier of a member concept of this thesaurus array.</xsd:documentation>
       
</xsd:annotation>
     
</xsd:element>
     
<xsd:element name="hasMemberArray" type="iso25964:Identifier">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">The identifier of a sub-array of this Thesaurus Array.</xsd:documentation>
       
</xsd:annotation>
     
</xsd:element>
   
</xsd:choice>
 
</xsd:sequence>
</xsd:complexType>

element ThesaurusArrayStruct/identifier
diagram iso25964-1_v1.4_p56.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>

element ThesaurusArrayStruct/ordered
diagram iso25964-1_v1.4_p57.png
namespace http://iso25964.org/
type xsd:boolean
properties
isRef 0
content simple
annotation
documentation
The value 'true' indicates that the concepts and sub-arrays of the array are ordered.  This imposed order is reflected by the XML document order of the XML document instance.
source <xsd:element name="ordered" type="xsd:boolean">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The value 'true' indicates that the concepts and sub-arrays of the array are ordered.  This imposed order is reflected by the XML document order of the XML document instance.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusArrayStruct/notation
diagram iso25964-1_v1.4_p58.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc unbounded
content simple
annotation
documentation
This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
source <xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusArrayStruct/NodeLabel
diagram iso25964-1_v1.4_p59.png
namespace http://iso25964.org/
type iso25964:NodeLabel
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified
annotation
documentation
@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="NodeLabel" type="iso25964:NodeLabel" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">@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:element>

element ThesaurusArrayStruct/hasSuperOrdinateConcept
diagram iso25964-1_v1.4_p60.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of the thesaurus concept under which this array appears.
(case that this array is not a sub-array)
source <xsd:element name="hasSuperOrdinateConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of the thesaurus concept under which this array appears.
(case that this array is not a sub-array)
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusArrayStruct/hasSuperOrdinateArray
diagram iso25964-1_v1.4_p61.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of the thesaurus array under which this thesaurus sub-array appears.
(case that this array is a sub-array)
source <xsd:element name="hasSuperOrdinateArray" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of the thesaurus array under which this thesaurus sub-array appears.
(case that this array is a sub-array)
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusArrayStruct/hasMemberConcept
diagram iso25964-1_v1.4_p62.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a member concept of this thesaurus array.
source <xsd:element name="hasMemberConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a member concept of this thesaurus array.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusArrayStruct/hasMemberArray
diagram iso25964-1_v1.4_p63.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a sub-array of this Thesaurus Array.
source <xsd:element name="hasMemberArray" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a sub-array of this Thesaurus Array.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType ThesaurusConceptStruct
diagram iso25964-1_v1.4_p64.png
namespace http://iso25964.org/
children iso25964:identifier iso25964:created iso25964:modified iso25964:status iso25964:notation iso25964:topConcept iso25964:PreferredTerm iso25964:SimpleNonPreferredTerm iso25964:ScopeNote iso25964:HistoryNote iso25964:CustomNote iso25964:CustomConceptAttribute
used by
element ThesaurusStruct/ThesaurusConcept
annotation
documentation
When a concept has an array of narrower concepts, the relationship to this array is not given here. To avoid redundancy, the relationship is given in one direction only, from ThesaurusArray using the child element hasSuperOrdinateConcept.
source <xsd:complexType name="ThesaurusConceptStruct">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">When a concept has an array of narrower concepts, the relationship to this array is not given here. To avoid redundancy, the relationship is given in one direction only, from ThesaurusArray using the child element hasSuperOrdinateConcept.</xsd:documentation>
 
</xsd:annotation>
 
<xsd:sequence>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>
   
<xsd:element ref="iso25964:created" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:modified" minOccurs="0" maxOccurs="1"/>
   
<xsd:element name="status" type="xsd:string" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="topConcept" type="xsd:boolean" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A true/false label indicating whether the concept is at the top of a hierarchy, i.e. has no broader concepts</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="PreferredTerm" type="iso25964:PreferredTerm" minOccurs="1" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The term used as a label for this concept. There should be one preferred term per language.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="SimpleNonPreferredTerm" type="iso25964:SimpleNonPreferredTerm" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Alternative terms by which this concept could be sought

The co-occurrence of the SimpleNonPreferredTerm and the PreferredTerm under the same ThesaurusConcept implies the existence of an Equivalence relation where that SimpleNonPreferredTerm has an identical language specification as the PreferredTerm.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="ScopeNote" type="iso25964:ScopeNote" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note defining or clarifying the scope of the concept within this thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="HistoryNote" type="iso25964:HistoryNote" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note recording changes to this concept within this thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="CustomNote" type="iso25964:CustomNote" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note of any other kind relating to this concept</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="CustomConceptAttribute" type="iso25964:CustomConceptAttribute" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">An additional attribute of a concept</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element ThesaurusConceptStruct/identifier
diagram iso25964-1_v1.4_p65.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>

element ThesaurusConceptStruct/status
diagram iso25964-1_v1.4_p66.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).
source <xsd:element name="status" type="xsd:string" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/notation
diagram iso25964-1_v1.4_p67.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc unbounded
content simple
annotation
documentation
This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
source <xsd:element name="notation" type="xsd:string" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept, ThesaurusArray and ConceptGroup (see 12.1.3 and 12.2.5.2).
If the thesaurus uses an expressive notation, then applying it to node labels will allow them to be shown in the correct place in hierarchical displays.
If there is no expressive notation, some other means should be found of outputting the node labels correctly in the display, such as a sort code attribute that is not displayed to users. In this event, the same attribute will be required at the display level for preferred terms.
The system of notation used for ConceptGroup may be quite distinct from that used for ThesaurusConcept, and one of these systems may be present without the other.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/topConcept
diagram iso25964-1_v1.4_p68.png
namespace http://iso25964.org/
type xsd:boolean
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
A true/false label indicating whether the concept is at the top of a hierarchy, i.e. has no broader concepts
source <xsd:element name="topConcept" type="xsd:boolean" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A true/false label indicating whether the concept is at the top of a hierarchy, i.e. has no broader concepts</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/PreferredTerm
diagram iso25964-1_v1.4_p69.png
namespace http://iso25964.org/
type iso25964:PreferredTerm
properties
isRef 0
minOcc 1
maxOcc unbounded
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 term used as a label for this concept. There should be one preferred term per language.
source <xsd:element name="PreferredTerm" type="iso25964:PreferredTerm" minOccurs="1" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The term used as a label for this concept. There should be one preferred term per language.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/SimpleNonPreferredTerm
diagram iso25964-1_v1.4_p70.png
namespace http://iso25964.org/
type iso25964:SimpleNonPreferredTerm
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute iso25964:hidden iso25964:role
annotation
documentation
Alternative terms by which this concept could be sought

The co-occurrence of the SimpleNonPreferredTerm and the PreferredTerm under the same ThesaurusConcept implies the existence of an Equivalence relation where that SimpleNonPreferredTerm has an identical language specification as the PreferredTerm.
source <xsd:element name="SimpleNonPreferredTerm" type="iso25964:SimpleNonPreferredTerm" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Alternative terms by which this concept could be sought

The co-occurrence of the SimpleNonPreferredTerm and the PreferredTerm under the same ThesaurusConcept implies the existence of an Equivalence relation where that SimpleNonPreferredTerm has an identical language specification as the PreferredTerm.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/ScopeNote
diagram iso25964-1_v1.4_p71.png
namespace http://iso25964.org/
type iso25964:ScopeNote
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
annotation
documentation
A note defining or clarifying the scope of the concept within this thesaurus
source <xsd:element name="ScopeNote" type="iso25964:ScopeNote" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note defining or clarifying the scope of the concept within this thesaurus</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/HistoryNote
diagram iso25964-1_v1.4_p72.png
namespace http://iso25964.org/
type iso25964:HistoryNote
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
annotation
documentation
A note recording changes to this concept within this thesaurus
source <xsd:element name="HistoryNote" type="iso25964:HistoryNote" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note recording changes to this concept within this thesaurus</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/CustomNote
diagram iso25964-1_v1.4_p73.png
namespace http://iso25964.org/
type iso25964:CustomNote
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo iso25964:noteType
annotation
documentation
A note of any other kind relating to this concept
source <xsd:element name="CustomNote" type="iso25964:CustomNote" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note of any other kind relating to this concept</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusConceptStruct/CustomConceptAttribute
diagram iso25964-1_v1.4_p74.png
namespace http://iso25964.org/
type iso25964:CustomConceptAttribute
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:customAttributeType
annotation
documentation
An additional attribute of a concept
source <xsd:element name="CustomConceptAttribute" type="iso25964:CustomConceptAttribute" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">An additional attribute of a concept</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType ThesaurusStruct
diagram iso25964-1_v1.4_p75.png
namespace http://iso25964.org/
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
used by
element ISO25964Interchange/Thesaurus
source <xsd:complexType name="ThesaurusStruct">
 
<xsd:sequence>
   
<xsd:group ref="iso25964:ThesaurusMetadataGroup"/>
   
<xsd:element name="ThesaurusConcept" type="iso25964:ThesaurusConceptStruct" minOccurs="1" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Each concept in the thesaurus is represented by one preferred term per language, and by any number of nonpreferred terms. The notation, scope note and broader/narrower/related term relationships apply to the concept as a whole, rather than to its preferred term. A unique identifier may be assigned to each concept. In some systems, the concept is identified only by its preferred term or by the identifier of its preferred term, but this has disadvantages if the spelling of the term changes.

This schema requires the identifier on the concept.
</xsd:documentation>
     
</xsd:annotation>
     
<xsd:unique name="uc_lang_of_preferred_term">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">There shall not be 2 preferred term with the same xml:lang attribute value.</xsd:documentation>
       
</xsd:annotation>
       
<xsd:selector xpath="iso25964:PreferredTerm/iso25964:lexicalValue"/>
       
<xsd:field xpath="@xml:lang"/>
     
</xsd:unique>
   
</xsd:element>
   
<xsd:element name="ThesaurusArray" minOccurs="0" maxOccurs="unbounded">
     
<xsd:complexType>
       
<xsd:complexContent>
         
<xsd:extension base="iso25964:ThesaurusArrayStruct"/>
       
</xsd:complexContent>
     
</xsd:complexType>
     
<xsd:unique name="uc_memberConcept">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">A Thesaurus array cannot contain the same member concept twice.</xsd:documentation>
       
</xsd:annotation>
       
<xsd:selector xpath="iso25964:hasMemberConcept"/>
       
<xsd:field xpath="."/>
     
</xsd:unique>
     
<xsd:unique name="uc_memberArray">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">A Thesaurus array cannot contain the same member array twice.</xsd:documentation>
       
</xsd:annotation>
       
<xsd:selector xpath="iso25964:hasMemberArray"/>
       
<xsd:field xpath="."/>
     
</xsd:unique>
   
</xsd:element>
   
<xsd:element name="ConceptGroup" type="iso25964:ConceptGroupStruct" minOccurs="0" maxOccurs="unbounded">
     
<xsd:unique name="uc_groupMember">
       
<xsd:annotation>
         
<xsd:documentation xml:lang="en">A concept group cannot containe a member concept twice.</xsd:documentation>
       
</xsd:annotation>
       
<xsd:selector xpath="iso25964:Member"/>
       
<xsd:field xpath="."/>
     
</xsd:unique>
   
</xsd:element>
   
<xsd:element name="Version" type="iso25964:VersionHistory" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The VersionHistory optionally allows any copy of a thesaurus to carry a record of versions or editions that have been created.

Although the class is optional and might not be needed when only one version exists, adoption is highly recommended as soon as there is more than one. Each version should be identified by an identifier or a date or both.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element ThesaurusStruct/ThesaurusConcept
diagram iso25964-1_v1.4_p76.png
namespace http://iso25964.org/
type iso25964:ThesaurusConceptStruct
properties
isRef 0
minOcc 1
maxOcc unbounded
content complex
children iso25964:identifier iso25964:created iso25964:modified iso25964:status iso25964:notation iso25964:topConcept iso25964:PreferredTerm iso25964:SimpleNonPreferredTerm iso25964:ScopeNote iso25964:HistoryNote iso25964:CustomNote iso25964:CustomConceptAttribute
identity constraints
  Name  Refer  Selector  Field(s)  
unique  uc_lang_of_preferred_term    iso25964:PreferredTerm/iso25964:lexicalValue  @xml:lang  
annotation
documentation
Each concept in the thesaurus is represented by one preferred term per language, and by any number of nonpreferred terms. The notation, scope note and broader/narrower/related term relationships apply to the concept as a whole, rather than to its preferred term. A unique identifier may be assigned to each concept. In some systems, the concept is identified only by its preferred term or by the identifier of its preferred term, but this has disadvantages if the spelling of the term changes.

This schema requires the identifier on the concept.
source <xsd:element name="ThesaurusConcept" type="iso25964:ThesaurusConceptStruct" minOccurs="1" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">Each concept in the thesaurus is represented by one preferred term per language, and by any number of nonpreferred terms. The notation, scope note and broader/narrower/related term relationships apply to the concept as a whole, rather than to its preferred term. A unique identifier may be assigned to each concept. In some systems, the concept is identified only by its preferred term or by the identifier of its preferred term, but this has disadvantages if the spelling of the term changes.

This schema requires the identifier on the concept.
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:unique name="uc_lang_of_preferred_term">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">There shall not be 2 preferred term with the same xml:lang attribute value.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:PreferredTerm/iso25964:lexicalValue"/>
   
<xsd:field xpath="@xml:lang"/>
 
</xsd:unique>
</xsd:element>

element ThesaurusStruct/ThesaurusArray
diagram iso25964-1_v1.4_p77.png
namespace http://iso25964.org/
type extension of iso25964:ThesaurusArrayStruct
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:identifier iso25964:ordered iso25964:notation iso25964:NodeLabel iso25964:hasSuperOrdinateConcept iso25964:hasSuperOrdinateArray iso25964:hasMemberConcept iso25964:hasMemberArray
identity constraints
  Name  Refer  Selector  Field(s)  
unique  uc_memberConcept    iso25964:hasMemberConcept  .  
unique  uc_memberArray    iso25964:hasMemberArray  .  
source <xsd:element name="ThesaurusArray" minOccurs="0" maxOccurs="unbounded">
 
<xsd:complexType>
   
<xsd:complexContent>
     
<xsd:extension base="iso25964:ThesaurusArrayStruct"/>
   
</xsd:complexContent>
 
</xsd:complexType>
 
<xsd:unique name="uc_memberConcept">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">A Thesaurus array cannot contain the same member concept twice.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:hasMemberConcept"/>
   
<xsd:field xpath="."/>
 
</xsd:unique>
 
<xsd:unique name="uc_memberArray">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">A Thesaurus array cannot contain the same member array twice.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:hasMemberArray"/>
   
<xsd:field xpath="."/>
 
</xsd:unique>
</xsd:element>

element ThesaurusStruct/ConceptGroup
diagram iso25964-1_v1.4_p78.png
namespace http://iso25964.org/
type iso25964:ConceptGroupStruct
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:identifier iso25964:conceptGroupType iso25964:notation iso25964:Member iso25964:ConceptGroupLabel
identity constraints
  Name  Refer  Selector  Field(s)  
unique  uc_groupMember    iso25964:Member  .  
source <xsd:element name="ConceptGroup" type="iso25964:ConceptGroupStruct" minOccurs="0" maxOccurs="unbounded">
 
<xsd:unique name="uc_groupMember">
   
<xsd:annotation>
     
<xsd:documentation xml:lang="en">A concept group cannot containe a member concept twice.</xsd:documentation>
   
</xsd:annotation>
   
<xsd:selector xpath="iso25964:Member"/>
   
<xsd:field xpath="."/>
 
</xsd:unique>
</xsd:element>

element ThesaurusStruct/Version
diagram iso25964-1_v1.4_p79.png
namespace http://iso25964.org/
type iso25964:VersionHistory
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:identifier iso25964:date iso25964:versionNote iso25964:currentVersion iso25964:thisVersion
annotation
documentation
The VersionHistory optionally allows any copy of a thesaurus to carry a record of versions or editions that have been created.

Although the class is optional and might not be needed when only one version exists, adoption is highly recommended as soon as there is more than one. Each version should be identified by an identifier or a date or both.
source <xsd:element name="Version" type="iso25964:VersionHistory" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The VersionHistory optionally allows any copy of a thesaurus to carry a record of versions or editions that have been created.

Although the class is optional and might not be needed when only one version exists, adoption is highly recommended as soon as there is more than one. Each version should be identified by an identifier or a date or both.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType ThesaurusTerm
diagram iso25964-1_v1.4_p80.png
namespace http://iso25964.org/
properties
abstract true
children iso25964:lexicalValue iso25964:identifier iso25964:created iso25964:modified source iso25964:status iso25964:Definition iso25964:HistoryNote iso25964:EditorialNote iso25964:CustomTermAttribute
used by
element ISO25964Interchange/SplitNonPreferredTerm
complexTypes PreferredTerm SimpleNonPreferredTerm SplitNonPreferredTerm
annotation
documentation
The wording of the term.

The identifier and date attributes of ThesaurusTerm are essential for the provision of a good updating service because if the spelling of a term changes, a constant Term identifier facilitates continuity during successive updates. The use of a concept identifier is strongly recommended to promote interoperability among networked search applications.
source <xsd:complexType name="ThesaurusTerm" abstract="true">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The wording of the term.

The identifier and date attributes of ThesaurusTerm are essential for the provision of a good updating service because if the spelling of a term changes, a constant Term identifier facilitates continuity during successive updates. The use of a concept identifier is strongly recommended to promote interoperability among networked search applications.
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:sequence>
   
<xsd:element ref="iso25964:lexicalValue" minOccurs="1" maxOccurs="1"/>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>
   
<xsd:element ref="iso25964:created" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:modified" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="dc:source" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">Notes the reference work or individual who contributed the term in question</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="status" type="xsd:string" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="Definition" type="iso25964:Definition" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note giving definitions of a term, not necessarily limited to the scope of the concept labelled by the term in this thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="HistoryNote" type="iso25964:HistoryNote" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note recording changes to this term within this thesaurus</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="EditorialNote" type="iso25964:EditorialNote" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">A note for use by the thesaurus editors during the editing process</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="CustomTermAttribute" type="iso25964:CustomTermAttribute" minOccurs="0" maxOccurs="unbounded">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The model includes classes CustomConceptAttribute and CustomTermAttribute for custom attributes of concepts and terms. These enable recording of custom information about concepts and terms.
These are included as separate classes rather than as normal attributes so that the administrator of the thesaurus management system can specify the values of custom attributes that can be assigned. The classes have an attribute customAttributeType, allowing the administrator to specify which type of attribute is being used. Values of customAttributeType should normally be taken from a controlled list.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element ThesaurusTerm/identifier
diagram iso25964-1_v1.4_p81.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="1" maxOccurs="1"/>

element ThesaurusTerm/status
diagram iso25964-1_v1.4_p82.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).
source <xsd:element name="status" type="xsd:string" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">This is an optional attribute of ThesaurusConcept and ThesaurusTerm, which records whether they are, for example, approved, candidates, superseded or deprecated (see 13.6.2).</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusTerm/Definition
diagram iso25964-1_v1.4_p83.png
namespace http://iso25964.org/
type iso25964:Definition
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo source
annotation
documentation
A note giving definitions of a term, not necessarily limited to the scope of the concept labelled by the term in this thesaurus
source <xsd:element name="Definition" type="iso25964:Definition" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note giving definitions of a term, not necessarily limited to the scope of the concept labelled by the term in this thesaurus</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusTerm/HistoryNote
diagram iso25964-1_v1.4_p84.png
namespace http://iso25964.org/
type iso25964:HistoryNote
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
annotation
documentation
A note recording changes to this term within this thesaurus
source <xsd:element name="HistoryNote" type="iso25964:HistoryNote" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note recording changes to this term within this thesaurus</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusTerm/EditorialNote
diagram iso25964-1_v1.4_p85.png
namespace http://iso25964.org/
type iso25964:EditorialNote
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:created iso25964:modified iso25964:identifier iso25964:refersTo
annotation
documentation
A note for use by the thesaurus editors during the editing process
source <xsd:element name="EditorialNote" type="iso25964:EditorialNote" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">A note for use by the thesaurus editors during the editing process</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element ThesaurusTerm/CustomTermAttribute
diagram iso25964-1_v1.4_p86.png
namespace http://iso25964.org/
type iso25964:CustomTermAttribute
properties
isRef 0
minOcc 0
maxOcc unbounded
content complex
children iso25964:lexicalValue iso25964:customAttributeType
annotation
documentation
The model includes classes CustomConceptAttribute and CustomTermAttribute for custom attributes of concepts and terms. These enable recording of custom information about concepts and terms.
These are included as separate classes rather than as normal attributes so that the administrator of the thesaurus management system can specify the values of custom attributes that can be assigned. The classes have an attribute customAttributeType, allowing the administrator to specify which type of attribute is being used. Values of customAttributeType should normally be taken from a controlled list.
source <xsd:element name="CustomTermAttribute" type="iso25964:CustomTermAttribute" minOccurs="0" maxOccurs="unbounded">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The model includes classes CustomConceptAttribute and CustomTermAttribute for custom attributes of concepts and terms. These enable recording of custom information about concepts and terms.
These are included as separate classes rather than as normal attributes so that the administrator of the thesaurus management system can specify the values of custom attributes that can be assigned. The classes have an attribute customAttributeType, allowing the administrator to specify which type of attribute is being used. Values of customAttributeType should normally be taken from a controlled list.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType TopLevelRelationship
diagram iso25964-1_v1.4_p87.png
namespace http://iso25964.org/
children iso25964:hasTopConcept iso25964:isTopConceptOf
used by
element ISO25964Interchange/TopLevelRelationship
source <xsd:complexType name="TopLevelRelationship">
 
<xsd:sequence>
   
<xsd:element name="hasTopConcept" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a top level concept.
This concept is the top level concept of the related concept (see ../isTopConceptOf) according to a hierarchical relationship of the thesaurus.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="isTopConceptOf" type="iso25964:Identifier">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept.
The related top level concept is identified by ../hasTopConcept.
</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element TopLevelRelationship/hasTopConcept
diagram iso25964-1_v1.4_p88.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a top level concept.
This concept is the top level concept of the related concept (see ../isTopConceptOf) according to a hierarchical relationship of the thesaurus.
source <xsd:element name="hasTopConcept" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a top level concept.
This concept is the top level concept of the related concept (see ../isTopConceptOf) according to a hierarchical relationship of the thesaurus.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element TopLevelRelationship/isTopConceptOf
diagram iso25964-1_v1.4_p89.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
content simple
annotation
documentation
The identifier of a thesaurus concept.
The related top level concept is identified by ../hasTopConcept.
source <xsd:element name="isTopConceptOf" type="iso25964:Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">The identifier of a thesaurus concept.
The related top level concept is identified by ../hasTopConcept.
</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

complexType VersionHistory
diagram iso25964-1_v1.4_p90.png
namespace http://iso25964.org/
children iso25964:identifier iso25964:date iso25964:versionNote iso25964:currentVersion iso25964:thisVersion
used by
element ThesaurusStruct/Version
source <xsd:complexType name="VersionHistory">
 
<xsd:sequence>
   
<xsd:element name="identifier" type="iso25964:Identifier" minOccurs="0" maxOccurs="1"/>
   
<xsd:element ref="iso25964:date" minOccurs="0" maxOccurs="1"/>
   
<xsd:element name="versionNote" type="xsd:string" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">versionNote can be used to explain the nature of the version, e.g. whether it is an updated version, an extract or a translation, or to explain its relationship to other versions.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="currentVersion" type="xsd:boolean" minOccurs="0" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">currentVersion is a Boolean (true/false) flag to indicate for each version whether it is still current or whether it has been superseded or withdrawn. More than one version can be current simultaneously.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
   
<xsd:element name="thisVersion" type="xsd:boolean" minOccurs="1" maxOccurs="1">
     
<xsd:annotation>
       
<xsd:documentation xml:lang="en">thisVersion is a Boolean flag to indicate which of the versions listed is the one to which this history is attached.</xsd:documentation>
     
</xsd:annotation>
   
</xsd:element>
 
</xsd:sequence>
</xsd:complexType>

element VersionHistory/identifier
diagram iso25964-1_v1.4_p91.png
namespace http://iso25964.org/
type iso25964:Identifier
properties
isRef 0
minOcc 0
maxOcc 1
content simple
source <xsd:element name="identifier" type="iso25964:Identifier" minOccurs="0" maxOccurs="1"/>

element VersionHistory/versionNote
diagram iso25964-1_v1.4_p92.png
namespace http://iso25964.org/
type xsd:string
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
versionNote can be used to explain the nature of the version, e.g. whether it is an updated version, an extract or a translation, or to explain its relationship to other versions.
source <xsd:element name="versionNote" type="xsd:string" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">versionNote can be used to explain the nature of the version, e.g. whether it is an updated version, an extract or a translation, or to explain its relationship to other versions.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element VersionHistory/currentVersion
diagram iso25964-1_v1.4_p93.png
namespace http://iso25964.org/
type xsd:boolean
properties
isRef 0
minOcc 0
maxOcc 1
content simple
annotation
documentation
currentVersion is a Boolean (true/false) flag to indicate for each version whether it is still current or whether it has been superseded or withdrawn. More than one version can be current simultaneously.
source <xsd:element name="currentVersion" type="xsd:boolean" minOccurs="0" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">currentVersion is a Boolean (true/false) flag to indicate for each version whether it is still current or whether it has been superseded or withdrawn. More than one version can be current simultaneously.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

element VersionHistory/thisVersion
diagram iso25964-1_v1.4_p94.png
namespace http://iso25964.org/
type xsd:boolean
properties
isRef 0
content simple
annotation
documentation
thisVersion is a Boolean flag to indicate which of the versions listed is the one to which this history is attached.
source <xsd:element name="thisVersion" type="xsd:boolean" minOccurs="1" maxOccurs="1">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">thisVersion is a Boolean flag to indicate which of the versions listed is the one to which this history is attached.</xsd:documentation>
 
</xsd:annotation>
</xsd:element>

simpleType date
namespace http://iso25964.org/
type union of (xsd:date, xsd:dateTime)
used by
elements created date modified
source <xsd:simpleType name="date">
 
<xsd:union memberTypes="xsd:date xsd:dateTime"/>
</xsd:simpleType>

simpleType Identifier
namespace http://iso25964.org/
type xsd:string
properties
base xsd:string
used by
elements HierarchicalRelationship/hasHierRelConcept ThesaurusArrayStruct/hasMemberArray ThesaurusArrayStruct/hasMemberConcept AssociativeRelationship/hasRelatedConcept GroupRelationship/hasSubGroup GroupRelationship/hasSuperGroup ThesaurusArrayStruct/hasSuperOrdinateArray ThesaurusArrayStruct/hasSuperOrdinateConcept TopLevelRelationship/hasTopConcept ThesaurusConceptStruct/identifier ThesaurusTerm/identifier Note/identifier ThesaurusArrayStruct/identifier ConceptGroupStruct/identifier VersionHistory/identifier ThesaurusMetadataGroup/identifier HierarchicalRelationship/isHierRelConcept AssociativeRelationship/isRelatedConcept TopLevelRelationship/isTopConceptOf ConceptGroupStruct/Member Note/refersTo CompoundEquivalence/UFPlus CompoundEquivalence/USEPlus
annotation
documentation
The identifier simple type is specified and and used instead of the DC identifier because dc:identifier does not have a simple type.  As such the dc:identifier does not allow to specify uniqueness constraints as needed on all elements except Thesaurus.
source <xsd:simpleType name="Identifier">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="dc">The identifier simple type is specified and and used instead of the DC identifier because dc:identifier does not have a simple type.  As such the dc:identifier does not allow to specify uniqueness constraints as needed on all elements except Thesaurus.</xsd:documentation>
 
</xsd:annotation>
 
<xsd:restriction base="xsd:string"/>
</xsd:simpleType>

element any
diagram iso25964-1_v1.4_p95.png
namespace http://purl.org/dc/elements/1.1/
type SimpleLiteral
properties
content complex
mixed true
abstract true
used by
group elementsGroup
attributes
Name  Type  Use  Default  Fixed  annotation
langderived by: xsd:languageoptional      
documentation
<div>
<h3>lang (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
<h4>Notes</h4>
<p>
      Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility. 
     </p>
<p>
      See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
       http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
      and the IANA language subtag registry at
      <a href="http://www.iana.org/assignments/language-subtag-registry">
       http://www.iana.org/assignments/language-subtag-registry</a>
      for further information.
     </p>
<p>
      The union allows for the 'un-declaration' of xml:lang with
      the empty string.
     </p>
</div>
source <xsd:element name="any" type="SimpleLiteral" abstract="true"/>

element contributor
diagram iso25964-1_v1.4_p96.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="contributor" substitutionGroup="any"/>

element coverage
diagram iso25964-1_v1.4_p97.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="coverage" substitutionGroup="any"/>

element creator
diagram iso25964-1_v1.4_p98.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="creator" substitutionGroup="any"/>

element date
diagram iso25964-1_v1.4_p99.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
source <xsd:element name="date" substitutionGroup="any"/>

element description
diagram iso25964-1_v1.4_p100.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="description" substitutionGroup="any"/>

element format
diagram iso25964-1_v1.4_p101.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="format" substitutionGroup="any"/>

element identifier
diagram iso25964-1_v1.4_p102.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
source <xsd:element name="identifier" substitutionGroup="any"/>

element language
diagram iso25964-1_v1.4_p103.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="language" substitutionGroup="any"/>

element publisher
diagram iso25964-1_v1.4_p104.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="publisher" substitutionGroup="any"/>

element relation
diagram iso25964-1_v1.4_p105.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="relation" substitutionGroup="any"/>

element rights
diagram iso25964-1_v1.4_p106.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="rights" substitutionGroup="any"/>

element source
diagram iso25964-1_v1.4_p107.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
complexTypes Definition ThesaurusTerm
group ThesaurusMetadataGroup
source <xsd:element name="source" substitutionGroup="any"/>

element subject
diagram iso25964-1_v1.4_p108.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="subject" substitutionGroup="any"/>

element title
diagram iso25964-1_v1.4_p109.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="title" substitutionGroup="any"/>

element type
diagram iso25964-1_v1.4_p110.png
namespace http://purl.org/dc/elements/1.1/
properties
substGrp any
used by
group ThesaurusMetadataGroup
source <xsd:element name="type" substitutionGroup="any"/>

group elementsGroup
diagram iso25964-1_v1.4_p111.png
namespace http://purl.org/dc/elements/1.1/
children any
used by
complexType elementContainer
annotation
documentation

        This group is included as a convenience for schema authors
            who need to refer to all the elements in the
            http://purl.org/dc/elements/1.1/ namespace.
   
source <xsd:group name="elementsGroup">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">
        This group is included as a convenience for schema authors
            who need to refer to all the elements in the
            http://purl.org/dc/elements/1.1/ namespace.
   
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:sequence>
   
<xsd:choice minOccurs="0" maxOccurs="unbounded">
     
<xsd:element ref="any"/>
   
</xsd:choice>
 
</xsd:sequence>
</xsd:group>

complexType elementContainer
diagram iso25964-1_v1.4_p112.png
namespace http://purl.org/dc/elements/1.1/
children any
annotation
documentation

    This complexType is included as a convenience for schema authors who need to define a root
    or container element for all of the DC elements.
   
source <xsd:complexType name="elementContainer">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">
    This complexType is included as a convenience for schema authors who need to define a root
    or container element for all of the DC elements.
   
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:choice>
   
<xsd:group ref="elementsGroup"/>
 
</xsd:choice>
</xsd:complexType>

complexType SimpleLiteral
diagram iso25964-1_v1.4_p113.png
namespace http://purl.org/dc/elements/1.1/
type restriction of xsd:anyType
properties
base xs:anyType
mixed true
used by
element any
attributes
Name  Type  Use  Default  Fixed  annotation
langderived by: xsd:languageoptional      
documentation
<div>
<h3>lang (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
<h4>Notes</h4>
<p>
      Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility. 
     </p>
<p>
      See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
       http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
      and the IANA language subtag registry at
      <a href="http://www.iana.org/assignments/language-subtag-registry">
       http://www.iana.org/assignments/language-subtag-registry</a>
      for further information.
     </p>
<p>
      The union allows for the 'un-declaration' of xml:lang with
      the empty string.
     </p>
</div>
annotation
documentation

            This is the default type for all of the DC elements.
            It permits text content only with optional
            xml:lang attribute.
            Text is allowed because mixed="true", but sub-elements
            are disallowed because minOccurs="0" and maxOccurs="0"
            are on the xs:any tag.

        This complexType allows for restriction or extension permitting
            child elements.
   
source <xsd:complexType name="SimpleLiteral" mixed="true">
 
<xsd:annotation>
   
<xsd:documentation xml:lang="en">
            This is the default type for all of the DC elements.
            It permits text content only with optional
            xml:lang attribute.
            Text is allowed because mixed="true", but sub-elements
            are disallowed because minOccurs="0" and maxOccurs="0"
            are on the xs:any tag.

        This complexType allows for restriction or extension permitting
            child elements.
   
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:complexContent>
   
<xsd:restriction base="xs:anyType">
     
<xsd:sequence>
       
<xsd:any processContents="lax" minOccurs="0" maxOccurs="0"/>
     
</xsd:sequence>
     
<xsd:attribute ref="xml:lang" use="optional"/>
   
</xsd:restriction>
 
</xsd:complexContent>
</xsd:complexType>

attribute base
namespace http://www.w3.org/XML/1998/namespace
type xsd:anyURI
used by
attributeGroup specialAttrs
annotation
documentation
<div>
<h3>base (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       provides a URI to be used as the base for interpreting any
       relative URIs in the scope of the element on which it
       appears; its value is inherited.  This name is reserved
       by virtue of its definition in the XML Base specification.</p>
<p>
      See <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
      for information about this attribute.
     </p>
</div>
source <xsd:attribute name="base" type="xs:anyURI">
 
<xsd:annotation>
   
<xsd:documentation>
     
<div>
       
<h3>base (as an attribute name)</h3>
       
<p>
       denotes an attribute whose value
       provides a URI to be used as the base for interpreting any
       relative URIs in the scope of the element on which it
       appears; its value is inherited.  This name is reserved
       by virtue of its definition in the XML Base specification.
</p>
       
<p>
      See
<a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
      for information about this attribute.
    
</p>
     
</div>
   
</xsd:documentation>
 
</xsd:annotation>
</xsd:attribute>

attribute id
namespace http://www.w3.org/XML/1998/namespace
type xsd:ID
used by
attributeGroup specialAttrs
annotation
documentation
<div>
<h3>id (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       should be interpreted as if declared to be of type ID.
       This name is reserved by virtue of its definition in the
       xml:id specification.</p>
<p>
      See <a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>
      for information about this attribute.
     </p>
</div>
source <xsd:attribute name="id" type="xs:ID">
 
<xsd:annotation>
   
<xsd:documentation>
     
<div>
       
<h3>id (as an attribute name)</h3>
       
<p>
       denotes an attribute whose value
       should be interpreted as if declared to be of type ID.
       This name is reserved by virtue of its definition in the
       xml:id specification.
</p>
       
<p>
      See
<a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>
      for information about this attribute.
    
</p>
     
</div>
   
</xsd:documentation>
 
</xsd:annotation>
</xsd:attribute>

attribute lang
namespace http://www.w3.org/XML/1998/namespace
type union of (xsd:language, restriction of xsd:string)
used by
element lexicalValue
complexType SimpleLiteral
attributeGroup specialAttrs
annotation
documentation
<div>
<h3>lang (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
<h4>Notes</h4>
<p>
      Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility. 
     </p>
<p>
      See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
       http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
      and the IANA language subtag registry at
      <a href="http://www.iana.org/assignments/language-subtag-registry">
       http://www.iana.org/assignments/language-subtag-registry</a>
      for further information.
     </p>
<p>
      The union allows for the 'un-declaration' of xml:lang with
      the empty string.
     </p>
</div>
source <xsd:attribute name="lang">
 
<xsd:annotation>
   
<xsd:documentation>
     
<div>
       
<h3>lang (as an attribute name)</h3>
       
<p>
       denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.
</p>
     
</div>
     
<div>
       
<h4>Notes</h4>
       
<p>
      Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility. 
    
</p>
       
<p>
      See BCP 47 at
<a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
       http://www.rfc-editor.org/rfc/bcp/bcp47.txt
</a>
      and the IANA language subtag registry at
     
<a href="http://www.iana.org/assignments/language-subtag-registry">
       http://www.iana.org/assignments/language-subtag-registry
</a>
      for further information.
    
</p>
       
<p>
      The union allows for the 'un-declaration' of xml:lang with
      the empty string.
    
</p>
     
</div>
   
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:simpleType>
   
<xsd:union memberTypes="xs:language">
     
<xsd:simpleType>
       
<xsd:restriction base="xs:string">
         
<xsd:enumeration value=""/>
       
</xsd:restriction>
     
</xsd:simpleType>
   
</xsd:union>
 
</xsd:simpleType>
</xsd:attribute>

attribute space
namespace http://www.w3.org/XML/1998/namespace
type restriction of xsd:NCName
used by
attributeGroup specialAttrs
facets
Kind Value annotation 
enumeration default 
enumeration preserve 
annotation
documentation
<div>
<h3>space (as an attribute name)</h3>
<p>
       denotes an attribute whose
       value is a keyword indicating what whitespace processing
       discipline is intended for the content of the element; its
       value is inherited.  This name is reserved by virtue of its
       definition in the XML specification.</p>
</div>
source <xsd:attribute name="space">
 
<xsd:annotation>
   
<xsd:documentation>
     
<div>
       
<h3>space (as an attribute name)</h3>
       
<p>
       denotes an attribute whose
       value is a keyword indicating what whitespace processing
       discipline is intended for the content of the element; its
       value is inherited.  This name is reserved by virtue of its
       definition in the XML specification.
</p>
     
</div>
   
</xsd:documentation>
 
</xsd:annotation>
 
<xsd:simpleType>
   
<xsd:restriction base="xs:NCName">
     
<xsd:enumeration value="default"/>
     
<xsd:enumeration value="preserve"/>
   
</xsd:restriction>
 
</xsd:simpleType>
</xsd:attribute>

attributeGroup specialAttrs
namespace http://www.w3.org/XML/1998/namespace
attributes
Name  Type  Use  Default  Fixed  annotation
basexsd:anyURI      
documentation
<div>
<h3>base (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       provides a URI to be used as the base for interpreting any
       relative URIs in the scope of the element on which it
       appears; its value is inherited.  This name is reserved
       by virtue of its definition in the XML Base specification.</p>
<p>
      See <a href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a>
      for information about this attribute.
     </p>
</div>
langderived by: xsd:language      
documentation
<div>
<h3>lang (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
<h4>Notes</h4>
<p>
      Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility. 
     </p>
<p>
      See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">
       http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>
      and the IANA language subtag registry at
      <a href="http://www.iana.org/assignments/language-subtag-registry">
       http://www.iana.org/assignments/language-subtag-registry</a>
      for further information.
     </p>
<p>
      The union allows for the 'un-declaration' of xml:lang with
      the empty string.
     </p>
</div>
spacederived by: xsd:NCName      
documentation
<div>
<h3>space (as an attribute name)</h3>
<p>
       denotes an attribute whose
       value is a keyword indicating what whitespace processing
       discipline is intended for the content of the element; its
       value is inherited.  This name is reserved by virtue of its
       definition in the XML specification.</p>
</div>
idxsd:ID      
documentation
<div>
<h3>id (as an attribute name)</h3>
<p>
       denotes an attribute whose value
       should be interpreted as if declared to be of type ID.
       This name is reserved by virtue of its definition in the
       xml:id specification.</p>
<p>
      See <a href="http://www.w3.org/TR/xml-id/">http://www.w3.org/TR/xml-id/</a>
      for information about this attribute.
     </p>
</div>
source <xsd:attributeGroup name="specialAttrs">
 
<xsd:attribute ref="xml:base"/>
 
<xsd:attribute ref="xml:lang"/>
 
<xsd:attribute ref="xml:space"/>
 
<xsd:attribute ref="xml:id"/>
</xsd:attributeGroup>


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