complexType "CorrespondenceType"
Namespace: |
|
Content: |
|
Defined: |
|
Includes: |
|
Used: |
|
XML Representation Summary |
<...> |
|
|
</...> |
Content Model Elements (1):
-
All Direct / Indirect Based Elements (1):
-
Annotation
Describes the commonalities and differences between two items using a textual description of both commonalities and differences plus an optional coding of the type of commonality, a commonality expresses as a 0 to 1 weighting factor (expressing degree of comparability) and a user defined correspondence property which is specific to an organization or community of use.
XML Source (w/o annotations (6); see within schema source)
<xs:sequence>
</xs:sequence>
</xs:complexType>
|
Content Element Detail (all declarations; defined within this component only; 5/5)
-
Common features of the compared objects. Supports multiple language versions of the same content as well as optional formatting of the content.
XML Source (w/o annotations (1); see within schema source)
-
A brief description describing the commonality of the two schemes/items, i.e., "Identical", "High", "Medium", "Low", "None". Supports the use of an external controlled vocabulary. The DDI Alliance has provided a controlled vocabulary (CommonalityType) to support this element at http://www.ddialliance.org/controlled-vocabularies.
Simple Content
XML Source (w/o annotations (1); see within schema source)
-
A value between 0 and 1 expressing the degree of commonality (0 indicates none, 1 indicates that they are identical).
Simple Content
maxInclusive: |
1
Identical
|
minInclusive: |
0
No commonality
|
XML Source (w/o annotations (1); see within schema source)
-
Description of the difference between the compared objects. Supports multiple language versions of the same content as well as optional formatting of the content.
XML Source (w/o annotations (1); see within schema source)
-
An alternate means of expressing commonality within a specific system. A system specific user defined correspondence expressed as a key/value pair. As this is specific to an individual system the use of controlled vocabularies for the key is strongly recommended.
XML Source (w/o annotations (1); see within schema source)