complexType "DataRelationshipType"
Namespace:
Content:
complex, 6 attributes, 16 elements
Defined:
Includes:
definitions of 5 elements
Used:
XML Representation Summary
<...
   
 = 
("Add" | "Update" | "Delete")
 = 
(xs:string | xs:string)
 = 
("Agency" | "Maintainable") : "Agency"
 = 
xs:boolean
 = 
(xs:dateTime | xs:date | xs:gYearMonth | xs:gYear | xs:duration)
 = 
"true"
   
>
   
Content: 
</...>
Content Model Elements (16):
DataRelationshipName, LogicalRecord, RecordRelationship, r:Agency, r:BasedOnObject, r:Description, r:ID, r:Label, r:MaintainableObject, r:URN, r:UserAttributePair, r:UserID, r:Version, r:VersionRationale, r:VersionResponsibility, r:VersionResponsibilityReference
All Direct / Indirect Based Elements (1):
DataRelationship
Known Usage Locations
Annotation
Describes the relationships among logical records in the dataset. Date Relationship is needed to create the appropriate link between the logical record and the physical storage description. Data Relationship is optional because a logical product can contain only a category scheme and/or code scheme. In addition to the standard name, label, and description, it contains structures to describe the LogicalRecord and RecordRelationship.
Type Definition Detail
Type Derivation Tree
r:AbstractIdentifiableType (extension)
      r:VersionableType (extension)
          DataRelationshipType
XML Source (w/o annotations (6); see within schema source)
<xs:complexType name="DataRelationshipType">
<xs:complexContent>
<xs:extension base="r:VersionableType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="DataRelationshipName"/>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="r:Label"/>
<xs:element minOccurs="0" ref="r:Description"/>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="LogicalRecord"/>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="RecordRelationship"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Content Element Detail (all declarations; defined within this component only; 5/16)
DataRelationshipName
Type:
r:NameType, complex content
A name for the DataRelationship. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="DataRelationshipName"/>

LogicalRecord
Type:
LogicalRecordType, complex content
A logical record is a description of all of the elements (variables or NCubes) related to a single case or analysis unit. Required to link a description of a physical record structure to its logical record.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="LogicalRecord"/>

r:Description
Type:
r:StructuredStringType, complex content
A description of the content and purpose of the DataRelationship. May be expressed in multiple languages and supports the use of structured content.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" ref="r:Description"/>

r:Label
Type:
r:LabelType, complex content
A display label for the DataRelationship. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="r:Label"/>

RecordRelationship
Type:
RecordRelationshipType, complex content
Describes the relationship between records of different types or of the same type within a longitudinal study. Identifies the key and linking value relationships. All relationships are pairwise. Multiple pairwise relationships maybe needed to clarify all record relationships within a logical product or data set.
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" ref="RecordRelationship"/>

XML schema documentation generated with DocFlex/XML RE 1.9.0 using DocFlex/XML XSDDoc 2.8.0 template set