ddi:group:3_0

Imports: ddi:reusable:3_0 (reusable.xsd)
Imports: ddi:archive:3_0 (archive.xsd)
Imports: ddi:comparative:3_0 (comparative.xsd)
Imports: ddi:conceptualcomponent:3_0 (conceptualcomponent.xsd)
Imports: ddi:datacollection:3_0 (datacollection.xsd)
Imports: ddi:logicalproduct:3_0 (logicalproduct.xsd)
Imports: ddi:physicaldataproduct:3_0 (physicaldataproduct.xsd)
Imports: ddi:studyunit:3_0 (studyunit.xsd)
Imports: ddi:ddiprofile:3_0 (ddiprofile.xsd)

Global Elements

Group (GroupType): Groups are used to document related data. They may contain subgroups or individual study items, and may also contain metadata which is applicable to all members of the group, and is subject to over-rides at the lower levels. Thus, metadata is inherited down the grouping structure. The purpose of groups is described using the attributes which summarize relationships along the dimensions of time, panel, geography, instrument and language. These attributes allow the purpose to be machine-actionable, while the group also includes an element for describing the purpose in human-readable format.

ResourcePackage (ResourcePackageType): The Resource is a specialized type of Group which is intended to hold re-usable metadata such as Category Schemes, Variables, etc. It is placed in the Resource construct for the purposes of being included by reference in other Groups and StudyUnits which describe studies, but does not directly describe existing studies itself.

Abstract (r:IdentifiedStructuredStringType): Human-readable summary of the grouped material.

Purpose (r:IdentifiedStructuredStringType): Human-readable explanation of why the creator published these objects.

Concepts (ConceptType): Lists, or references, the concepts describing the data that are being documented.

DataCollection (DataCollectionType): Shared documentation regarding data collection for all members of the group, subject to over-rides at a lower level.

LogicalProduct (LogicalProductType): Shared documentation regarding the logical data products of all members of the group, subject to over-rides at a lower level.

PhysicalDataProduct (PhysicalDataProductType): Shared documentation regarding the physical data products of all members of the group, subject to over-rides at a lower level.

StudyUnit (StudyUnitType): Description of an individual study being documented as a member of the group. The study unit description inherits all metadata found at higher levels - that is, all metadata and documentation describing the groups and subgroups of which the study unit is a member. This metadata and documentation may be over-ridden within the study unit.

SubGroup (SubGroupType): Subordinate group which inherits all the metadata provided in the higher-level groups and subgroups of which this subgroup is a member, subject to over-rides within the sub-group itself.

DDIProfileReference (r:ReferenceType): References a DDI Profile used by the group or resource package.

Reference (r:ReferenceType): References a module that is external to the group, sub-group, or resource package.


Complex Types

ResourcePackageType: The Resource Package is a specialized structure which is intended to hold reusable metadata such as Category Schemes, Variable Schemes, etc. These are placed in the Resource Package for the purpose of being included by reference in Groups and StudyUnits. The Resource Package has a similar structure to the Group.

GroupType: Groups are used to document related data. They may contain subgroups or individual study items, and may also contain metadata which is applicable to all members of the group, and is subject to over-rides at the lower levels. Thus, metadata is inherited down the grouping structure. The purpose of groups is described using the attributes which summarize relationships along the dimensions of time, panel, geography, instrument and language. These attributes allow the purpose to be machine-actionable, while the group also includes an element for describing the purpose in human-readable format.

SubGroupType: The subgroup element is a container for a group that is a child of a higher-level group described in this module, but may also be a parent to other (subordinate) groups. A group can be fully described, or just referenced, within its subgroup container.

ConceptType: Allows for inclusion of a fully marked up Conceptual Components module or referencing such a module that is external to the instance.

DataCollectionType: Allows for inclusion of data collection information that is common to all members of the group, or referencing external data collection information.

LogicalProductType: Allows for inclusion of a logical product that is common to all members of the group, or referencing an external logical product.

PhysicalDataProductType: Allows for inclusion of a physical data product for reuse by reference.

StudyUnitType: Allows for inclusion of a study unit that belongs to the group as a direct child. Subgroups may also contain study units, and individual study units and subgroups may be members of a single group. Study units can be included in any group or subgroup either as in-line documentation/metadata or by reference.


Simple Types

TimeGroupCodeType: Indicates how all members of the group are related along the dimension of time. These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.

InstrumentGroupCodeType: Indicates how all members of the group are related in terms of the instruments used to collect data. These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.

PanelGroupCodeType: Indicates how all members of the group are related in terms of type of panel. These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.

GeographyGroupCodeType: Indicates how all members of the group are related along the dimension of geography. These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.

DataSetGroupCodeType: Indicates how all members of the group are related in terms of physical data products in relation to data collection efforts. These relationships are inferred by the markup author, and should be considered as her/his own interpretation of the data.

LanguageGroupCodeType: Indicates the panel relationships among all Study Units within the group and its sub-groups. This is an assertion of the relationship, and it is incumbent on the creating user or application to make sure that the assertion is true.


Copyright © 2008 DDI Alliance, DDI Version 3.0 (2008-04-28)

This documentation is extracted from the inline documentation of DDI 3.0 XML Schema and is licensed under the terms of the GNU General Public License as the schema itself.