# t_attribute

Notes:
A URI for access, normally expressed as a URL


Notes:
The mime type. Supports the use of an controlled vocabulary.


Notes:
Indicates address type (i.e. home, office, mailing, etc.)


Notes:
Number and street including office or suite number. May use multiple lines.


Notes:
City, place, or local area used as part of an address.


Notes:
A major subnational division such as a state or province used to identify a major region within an address.


Notes:
Time zone of the location expressed as code.


Notes:
Clarifies when the identification information is accurate.


Notes:
Specify the level privacy for the address as public, restricted, or private. Supports the use of an external controlled vocabulary


Notes:
Set to "true" if this is the preferred location for contacting the organization or individual.


Notes:
Geographic coordinates corresponding to the address.


Notes:
The region covered by the agent at this address


Notes:
The type or purpose of the location (i.e. regional office, distribution center, home)


Notes:
Full name of the contributor. Language equivalents should be expressed within the International String structure.


Notes:
The role of the of the Agent within the context of the parent property name with information on the extent to which the role applies. Allows for use of external controlled vocabularies. Reference should be made to the vocabulary within the structure of the role. Recommended role for contributors can be found in the CASRAI Contributor Roles Vocabulary (CRediT) http://dictionary.casrai.org/Contributor_Roles, or the OPENRIF contribution ontology https://github.com/openrif/contribution-ontology


Notes:
The effective dates of the relation. A structured DateRange with start and end Date (both with the structure of Date and supporting the use of ISO and non-ISO date structures); Use to relate a period with a start and end date.


Notes:
Provides semantic context for the relationship


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list


Notes:
Type of relation in terms of totality with respect to an associated collection.


Notes:
Full authoritative title. List any additional titles for this item as AlternativeTitle.


Notes:
An alternative title by which a data collection is commonly referred, or an abbreviation  for the title.


Notes:
Person, corporate body, or agency responsible for the substantive and intellectual content of the described object.


Notes:
Person or organization responsible for making the resource available in its present form.


Notes:
The name of a contributing author or creator, who worked in support of the primary creator given above.


Notes:
A date associated with the annotated object (not the coverage period). Use typeOfDate to specify the type of date such as Version, Publication, Submitted, Copyrighted, Accepted, etc.


Notes:
Language of the intellectual content of the described object. Multiple languages are supported by the structure itself as defined in the transformation to specific bindings. Use language codes supported by xs:language which include the 2 and 3 character and extended structures defined by RFC4646 or its successors. Supports multiple language codes.


Notes:
An identifier or locator. Contains identifier and Managing agency (ISBN, ISSN, DOI, local archive). Indicates if it is a URI.


Notes:
Provide the type of the resource. This supports the use of a controlled vocabulary. It should be appropriate to the level of the annotation.


Notes:
The name or identifier of source information for the annotated object.


Notes:
Means of identifying the current version of the annotated object.


Notes:
The agent responsible for the version. May have an associated role.


Notes:
A summary description (abstract) of the annotated object.


Notes:
Provide the identifier, managing agency, and type of resource related to this object. Use to specify related resources similar to Dublin Core isPartOf and hasPart to indicate collection/series membership for objects where there is an identifiable record. If not an identified object use the relationship to ExternalMaterial using a type that indicates a series description.


Notes:
A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.


Notes:
Information about rights held in and over the resource. Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.


Notes:
Use to specify the type of date. This may reflect the refinements of dc:date such as dateAccepted, dateCopyrighted, dateSubmitted, etc.


Notes:
Specify the type of area covered i.e. Total, Land, Water, etc. Supports the use of an external controlled vocabulary.


Notes:
Records the measurement unit, for example, Square Kilometer, Square Mile. Supports the use of an external controlled vocabulary.


Notes:
The area measure expressed as a decimal for the measurement unit designated.


Notes:
The type of audio clip provided. Supports the use of a controlled vocabulary.


Notes:
The point to begin the audio clip. If no point is provided the assumption is that the start point is the beginning of the clip provided.


Notes:
The point to end the audio clip. If no point is provided the assumption is that the end point is the end of the clip provided.


Notes:
Textual description of the rationale/purpose for the based on reference to inform users as to the extent and implication of the version change. May be expressed in multiple languages.


Notes:
RationaleCode is primarily for internal processing flags within an organization or system. Supports the use of an external controlled vocabulary.


Notes:
The affiliation of this person to an organization. This is generally an organization or sub-organization name and should be related to the specific role within which the individual is being listed.


Notes:
SQL SELECT statement that describes the selection of the LogicalRecord from the Dataset


Notes:
Provides an alternative to or supplements the SQL data description.


Notes:
Provides an index for the member within an ordered array


Notes:
Index value of member in an ordered array


Notes:
Type of category statistic. Supports the use of an external controlled vocabulary. DDI strongly recommends the use of a controlled vocabulary.


Notes:
The value of the identified type of statistic for the category. May be repeated to provide unweighted or weighted values and different computation bases.


Notes:
Value of the category to which the statistics apply


Notes:
The value of the filter variable to which the category statistic is restricted


Notes:
Number of characters from beginning of the document, indicating the inclusive start of the text range.


Notes:
Number of characters from the beginning of the document, indicating the inclusive end of the text segment.


Notes:
can be used to describe a text segment as start and length


Notes:
Indicates the level within which the CodeItem resides


Notes:
Type of relation in terms of totality with respect to an associated collection


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumeration list


Notes:
Designates the programming language used for the command. Supports the use of a controlled vocabulary.


Notes:
Content of the command itself expressed in the language designated in Programming Language.


Notes:
A description of the purpose and use of the command code provided. Supports multiple languages.


Notes:
Identifies and provides a link to an external copy of the command, for example, a SAS Command Code script. Designates the programming language of the command file as well as the URI for the file.


Notes:
This is an in-line provision of the command itself. It provides the programming language used as well as the command.


Notes:
A description of the location of the file. This may not be machine actionable. It supports a description expressed in multiple languages.


Notes:
RelationSpecification Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list


Notes:
type of relation in terms of totality with respect to an associated collection.


Notes:
The condition on which the associated text varies expressed by a command code. For example, a command that inserts an age by calculating the difference between today’s date and a previously defined date of birth.


Notes:
The number of units to off-set the date for this item expressed as a decimal.


Notes:
If set to "true" the date is offset the number of units specified PRIOR to the default date of the data. A setting of "false" indicates a date the specified number of units in the FUTURE from the default date of the data.


Notes:
A description of the common features of the two items using a StructuredString to support multiple language versions of the same content as well as optional formatting of the content.


Notes:
A description of the differences between the two items using a StructuredString to support multiple language versions of the same content as well as optional formatting of the content.


Notes:
Commonality expressed as a term or code. Supports the use of an external controlled vocabulary. If repeated, clarify each external controlled vocabulary used.


Notes:
Allows specification of exact match, close match, or disjoint. These relationships can be further defined by describing commonalities or differences or providing additional controlled vocabulary description of relationship.


Notes:
The type of relationship between the two CustomItems. The verb in the sentence describing the relationship between the source (subject) and the target (object).


Notes:
Strongly recommend that ALL dates be expressed in an ISO format at a minimum. A single point in time expressed in an ISO standard structure. Note that while it supports an ISO date range structure this should be used in Date only when the single date is unclear i.e. occurring at some time between two dates.


Notes:
A simple date expressed in a non-ISO date format, including a specification of the date format and calendar used.


Notes:
The date (time) designating the beginning of the period or range.


Notes:
The date (time) designating the end of the period or range.


Notes:
Indicates that the value is included in the range. Set to false if the range includes numbers up to but no including the designated value.


Notes:
The bounding value expressed as an xs:double


Notes:
This is the head of a substitution group and is never used directly as an element name. Instead it is replaced with either LiteralText or ConditionalText.


Notes:
If textual structure (e.g. size, color, font, etc.) is required to understand the meaning of the content change value to "true".


Notes:
Specifies the language of the intended audience. This is particularly important for clarifying the primary language of a mixed language textual string, for example when language testing and using a foreign word withing the question text. Supports the inclusion of multiple languages.


Notes:
Explanation of the intent of some decision or object. Supports the use of multiple languages and structured tex


Notes:
Provides the relative order of TextContent objects in a dynamic text with more than one TextContent object. Uses integer value.


Notes:
Indicates the type of service used. Supports the use of a controlled vocabulary.


Notes:
Time period during which the account is valid.


Notes:
Specify the level privacy for the address as public, restricted, or private. Supports the use of an external controlled vocabulary.


Notes:
Set to "true" if this is the preferred address.


Notes:
The condition to verify if the parent IfThenElse condition is false.


Notes:
The email address expressed as a string (should follow the Internet format specification - RFC 5322) e.g. user@server.ext, more complex and flexible examples are also supported by the format.


Notes:
Code indicating the type of e-mail address. Supports the use of an external controlled vocabulary. (e.g. home, office)


Notes:
Time period for which the e-mail address is valid.


Notes:
Set to true if this is the preferred email


Notes:
The ID of the code list (controlled vocabulary) that the content was taken from.


Notes:
The name of the agency maintaining the code list.


Notes:
The version number of the code list (default is 1.0).


Notes:
If the value of the string is "Other" or the equivalent from the codelist, this attribute can provide a more specific value not found in the codelist.


Notes:
The URN or URL of the controlled vocabulary


Notes:
The value of the entry of the controlled vocabulary. If no controlled vocabulary is used the term is entered here and none of the properties defining the controlled vocabulary location are used.


Notes:
Language of the content value if applicable


Notes:
The default setting states that leading and trailing white space will be removed and multiple adjacent white spaces will be treated as a single white space. If the existance of any of these white spaces is critical to the understanding of the content, change the value of this attribute to "preserve".


Notes:
The number or other means of identifying the form.


Notes:
A statement regarding the use, coverage, and purpose of the form.


Notes:
Set to "true" if the form is required. Set to "false" if the form is optional.


Notes:
Index number expressed as an integer. The position of the member in an ordered array. Optional for unordered Collections.


Notes:
Provides information on the spatial relationship between the parent and child.


Notes:
Provide a semantic that provides a context for the relationship using and External Controlled Vocabulary


Notes:
Type of relation in terms of its totality using an enumeration list.


Notes:
An aggregation of the units of the child Unit Type will result in exhaustive coverage of the parent Unit Type


Notes:
A reference to the location of the image using a URI.


Notes:
Brief description of the image type. Supports the use of an external controlled vocabulary.


Notes:
Provides the resolution of the image in dots per inch to assist in selecting the appropriate image for various uses.


Notes:
Language of image. Supports the indication of multiple languages. Supports use of codes defined by the RFC 1766.


Notes:
A comma-delimited list of x,y coordinates, listed as a set of adjacent points for rectangles and polygons, and as a center-point and a radius for circles (x,y,r).


Notes:
A fixed set of valid responses includes Rectangle, Circle, and Polygon.


Notes:
Title that precedes the name of the individual, such as Ms., or Dr.


Notes:
Middle name or initial of the individual


Notes:
Last (family) name /surname of the individual


Notes:
Title that follows the name of the individual, such as Esq.


Notes:
This provides a means of providing a full name as a single object for display or print such as identification badges etc. For example a person with the name of William Grace for official use may prefer a display name of Bill Grace on a name tag or other informal publication.


Notes:
Clarifies when the name information is accurate.


Notes:
An abbreviation or acronym for the name. This may be expressed in multiple languages. It is assumed that if only a single language is provided that it may be used in any of the other languages within which the name itself is expressed.


Notes:
The type of individual name provided. the use of a controlled vocabulary is strongly recommended. At minimum his should include, e.g. PreviousFormalName, Nickname (or CommonName), Other.


Notes:
Sex allows for the specification of male, female or neutral. The purpose of providing this information is to assist others in the appropriate use of pronouns when addressing the individual. Note that many countries/languages may offer a neutral pronoun form.


Notes:
If more than one name for the object is provided, use the isPreferred attribute to indicate which is the preferred name content. All other names should be set to isPreferred="false".


Notes:
A name may be specific to a particular context, i.e. common usage, business, social, etc.. Identify the context related to the specified name. Supports the use of an external controlled vocabulary.


Notes:
The legal or formal name of the individual should have the isFormal attribute set to true. To avoid confusion only one individual name should have the isFormal attribute set to true. Use the TypeOfIndividualName to further differentiate the type and applied usage when multiple names are provided.


Notes:
Relationship between the source and target InstanceVariables or to the setValue if provided


Notes:
A set value for the key source Instance Variables


Notes:
Describes the relationship between the source and target members using both controlled vocabularies and descriptive text. In this context the correspondence refers to the two instance variables, not their value. The relationship would normally be exactMatch.


Notes:
An identifier as it should be listed for identification purposes.


Notes:
The identification of the Agency which assigns and manages the identifier, i.e., ISBN, ISSN, DOI, etc.


Notes:
A non-formatted string of text with an attribute that designates the language of the text. Repeat this object to express the same content in another language.


Notes:
Supports the optional use of XHTML formatting tags within the string structure. In addition to the language designation and information regarding translation, the attribute isPlain can be set to true to indicate that the content should be treated as plain unstructured text, including any XHTML formatting tags. Repeat the content element to provide multiple language versions of the same content.


Notes:
Indicate the locality specification for content that is specific to a geographic area. May be a country code, sub-country code, or area name.


Notes:
Allows for the specification of a starting date and ending date for the period that this label is valid.


Notes:
A positive integer indicating the maximum number of characters in the label.


Notes:
Indicates the language of content. Note that language allows for a simple 2 or 3 character language code or a language code extended by a country code , for example en-au for English as used in Australia.


Notes:
Indicates whether content is a translation (true) or an original (false).


Notes:
Indicates whether content is translatable (true) or not (false). An example of something that is not translatable would be a MNEMONIC of an object or a number.


Notes:
List the language code of the source. Repeat of multiple language sources are used.


Notes:
The date the content was translated. Provision of translation date allows user to verify if translation was available during data collection or other time linked activity.


Notes:
Supports specification of scope for the contained content. Use with the language specification to filter application of content.


Notes:
Indicates that the content is to be treated as plain text (no formatting). You may use DDIProfile to fix the value of this attribute to 'true' in cases where you wish to indicate that your system treats all content should be treated as plain text.


Notes:
Uses a enumerated value to specify the structuring elements used.


Notes:
If the value of structureUsed is Other enter the structue type.


Notes:
Provides an association between a level number and optional concept which defines it within an ordered array. Use is required.


Notes:
A display label for the object. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
Number of lines from beginning of the document.


Notes:
Number of characters from start of the line specified in StartLine.


Notes:
Number of characters from the start of the line specified in EndLine.


Notes:
The value of the static text string. Supports the optional use of XHTML formatting tags within the string structure. If the content of a literal text contains more than one language, i.e. "What is your understanding of the German word 'Gesundheit'?", the foreign language element should be placed in a separate LiteralText component with the appropriate xmlang value and, in this case, isTranslatable set to "false". If the existence of white space is critical to the understanding of the content (such as inclusion of a leading or trailing white space), set the attribute of Text xml:space to "preserve".


Notes:
Type of identifier, specifying the context of the identifier.


Notes:
The time period for which this name is accurate and in use.


Notes:
Date from which the Map became valid. The date must be defined if the Map belongs to a floating CorrespondenceTable. Date at which the Map became invalid. The date must be defined if the Map belongs to a floating Correspondence Table and is no longer valid.


Notes:
Type of correspondence in terms of commonalities and differences between two members.


Notes:
A display label for the OrderedMemberCorrespondence. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
Explanation of the ways in which some decision or object is employed. Supports the use of multiple languages and structured text.


Notes:
This is the date expressed in a non-ISO compliant structure. Primarily used to retain legacy content or to express non-Gregorian calender dates.


Notes:
Indicate the structure of the date provided in NonISODate. For example if the NonISODate contained 4/1/2000 the Historical Date Format would be mm/dd/yyyy. The use of a controlled vocabulary is strongly recommended to support interoperability.


Notes:
Specifies the type of calendar used (e.g., Gregorian, Julian, Jewish).


Notes:
A display label for the number range. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
High or top value on the range expressed as an xs:decimal within an isInclusive Boolean flag.


Notes:
High or top value on the range expressed as an xs:double within an isInclusive Boolean flag.


Notes:
Low or bottom value on the range expressed as an xs:double within an isInclusive Boolean flag.


Notes:
Regular expression defining the allowed syntax of the number.


Notes:
Default value is False. The High or top code represents the value expressed and anything higher.


Notes:
Default value is False. The Low or bottom code represents the value expressed and anything lower.


Notes:
Bounding value expressed as an xs:double


Notes:
A name may be specific to a particular context, i.e., a type of software, or a section of a registry. Identify the context related to the specified name.


Notes:
The type of organization name provided. the use of a controlled vocabulary is strongly recommended. At minimum this should include, e.g. PreviousFormalName, Nickname (or CommonName), Other.


Notes:
The legal or formal name of the organization should have the isFormal attribute set to true. To avoid confusion only one organization name should have the isFormal attribute set to true. Use the TypeOfOrganizationName to further differentiate the type and applied usage when multiple names are provided.


Notes:
The term attributed to the parent class, for example the role of a Contributor.


Notes:
Describes the extent to which the parent term applies for the specific case using an external controlled vocabulary. When associated with a role from the CASRAI Contributor Roles Taxonomy an appropriate vocabulary should be specified as either ‘lead’, ‘equal’, or ‘supporting’.


Notes:
A URI for the boundary file containing the polygon


Notes:
The PolygonLinkCode is the identifier of the specific polygon within the file. For example in an NHGIS file the LinkCodeForPolygon for Tract 101.01 in Hennepin County in Minnesota is 2700530010101.


Notes:
The format of the shape file existing at the location indicated by the sibling ExternalURI element.


Notes:
A geographic point defined by a latitude and longitude. A minimum of 4 points is required as the first and last point should be identical in order to close the polygon. Note that a triangle has three sides and requires 3 unique points plus a fourth point replicating the first point in order to close the polygon.


Notes:
The period for which this image is effective/valid.


Notes:
Specify the level privacy for the image as public, restricted, or private. Supports the use of an external controlled vocabulary.


Notes:
Set to "true" if the value is included in the range.


Notes:
Textual description of the rationale/purpose for the version change to inform users as to the extent and implication of the version change. May be expressed in multiple languages.


Notes:
If the date is for a subset of data only such as a referent date for residence 5 years ago, use Subject to specify the coverage of the data this date applies to. May be repeated to reflect multiple subjects.


Notes:
If the date is for a subset of data only such as a referent date for residence 5 years ago, use keyword to specify the coverage of the data this date applies to. May be repeated to reflect multiple keywords.


Notes:
The type of relationship between the annotated object and the related resource. Standard usage may include: describesDate, isDescribedBy,  isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires, etc.


Notes:
Describes the type and length of the audio segment.


Notes:
Describes the type and length of the video segment.


Notes:
An X-Pointer expression identifying a node in the XML document.


Notes:
Defines the segment of textual content used by the parent object. Can identify a set of lines and or characters used to define the segment


Notes:
Defines the shape and area of an image used as part of a location representation. The shape is defined as a Rectangle, Circle, or Polygon and Coordinates provides the information required to define it.


Notes:
The value of the coordinate expressed as a string.


Notes:
Identifies the type of point coordinate system using a controlled vocabulary. Point formats include decimal degree, degrees minutes seconds, decimal minutes, meters, and feet.


Notes:
A URI for the spatial file containing the line


Notes:
The lineLinkCode is the identifier of the specific line within the file.


Notes:
A geographic point defined by a latitude and longitude. A minimum of 2 points is required in order to define the line.


Notes:
An X coordinate (latitudinal equivalent) value and format expressed using the Spatial Coordinate structure.


Notes:
A Y coordinate (longitudinal equivalent) value and format expressed using the Spatial Coordinate structure.


Notes:
Provides the types of the two spatial objects.


Notes:
Defines the relationship of the two spatial objects


Notes:
Set to "true" if the statistic is weighted using the weight designated in VariableStatistics.


Notes:
Defines the cases included in determining the statistic. The options are total=all cases, valid and missing (invalid); validOnly=Only valid values, missing (invalid) are not included in the calculation; missingOnly=Only missing (invalid) cases included in the calculation.


Notes:
Indicate the type of numeric value as decimal, float, double


Notes:
The value of the statistic expressed as a decimal, float, or double.


Notes:
Type of summary statistic, such as count, mean, mode, median, etc. Supports the use of an external controlled vocabulary. DDI strongly recommends the use of a controlled vocabulary.


Notes:
The value of the statistics and whether it is weighted and/or includes missing values. May expressed as xs:decimal and/or xs:double


Notes:
Default value is True. The information is for the primary sample unit or universe. Change to False if the information relates to a secondary or sub- sample universe.


Notes:
The target size of the sample expressed as an integer.


Notes:
The target size of the sample expressed as an integer (70% expressed as .7)


Notes:
The telephone number including country code if appropriate.


Notes:
Indicates type of telephone number provided (home, fax, office, cell, etc.). Supports the use of a controlled vocabulary.


Notes:
Time period during which the telephone number is valid.


Notes:
Specify the level privacy for the telephone number as public, restricted, or private. Supports the use of an external controlled vocabulary.


Notes:
Set to "true" if this is the preferred telephone number for contact.


Notes:
Specification of the line and offset for the beginning and end of the segment.


Notes:
Specification of the character offset for the beginning and end of the segment.


Notes:
Uses a controlled vocabulary entry to classify the description provided.


Notes:
A short natural language account of the characteristics of the object.


Notes:
Optional use of a controlled vocabulary to specifically type the associated content.


Notes:
Content of the property expressed as a simple string.


Notes:
The actual content of this value as a string


Notes:
The usual setting "collapse" states that leading and trailing white space will be removed and multiple adjacent white spaces will be treated as a single white space. When setting to "replace" all occurrences of #x9 (tab), #xA (line feed) and #xD (carriage return) are replaced with #x20 (space) but leading and trailing spaces will be retained. If the existence of any of these white spaces is critical to the understanding of the content, change the value of this attribute to "preserve".


Notes:
The type of video clip provided. Supports the use of a controlled vocabulary.


Notes:
The point to begin the video clip. If no point is provided the assumption is that the start point is the beginning of the clip provided.


Notes:
The point to end the video clip. If no point is provided the assumption is that the end point is the end of the clip provided.


Notes:
Set to "true" if this is the preferred URL.


Notes:
The type of URL for example personal, project, organization, division, etc.


Notes:
Index value of WorkflowStep in an ordered array


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list. Use if all relations within this relation structure are of the same specification.


Notes:
Restricted to CategoryRelation. CategoryRelations making up the relation structure.


Notes:
MemberIndicator Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.


Notes:
Natural language statement conveying the meaning of a concept, differentiating it from other concepts. Supports the use of multiple languages and structured text.


Notes:
A structured display label providing a fully human readable display for the identification of the object. Supports the use of multiple languages and structured text.


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list.  Use if all relations within this relation structure are of the same specification.


Notes:
Restricted to ConceptRelation. ConceptRelations making up the relation structure.


Notes:
Whether the collection is a bag or a set: a bag is a collection with duplicates allowed, a set is a collection without duplicates.


Notes:
Explanation of the intent of some decision or object. Supports the use of multiple languages and structured text.


Notes:
If members are ordered set to true, if unordered set to false.


Notes:
A display label for the CollectionCorrespondence. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
Realization of correspondence in Comparison for mapping similar concepts.


Notes:
Immutable characteristics of the variable such as, geographic designator, weight, temporal designation, etc.


Notes:
The data type of this variable. Supports the optional use of an external controlled vocabulary.


Notes:
This should match a platformType of the RepresentedVariable on which the InstanceVariable is based (if one exists). It is drawn from the same external controlled vocabulary used by the RepreentedVariable's platformType.  A sample list for the external controlled vocabulary is:  A sample list would be:  • BlankString - A Blank string indicates missing. Comparison is based on lexical order.  • EmptyString - An empty string indicates missing. Use in comparisons returns missing.   • Rstyle - Codes drawn from  NA and the IEEE 754 values of  NaN  -Inf   +Inf.   Comparisons return NA.   • SASNumeric - codes drawn from . ._ .A .B .C .D .E .F .G .H .I .J .K .L .M .N .O .P .Q .R .S .T .U .V .W .X .Y .Z    Sentinel code treated as less than any substantive value   • SPSSstyle - System missing (a dot) a set of individual values drawn from the same datatype as the SubstantiveValueDomain, and a range of values  drawn from the same datatype as the SubstantiveValueDomain.  Comparisons return system missing.  Some functions substitute with valid values (e.g. SUM replaces missing values with 0)   • StataNumeric - codes drawn from . ._ .A .B .C .D .E .F .G .H .I .J .K .L .M .N .O .P .Q .R .S .T .U .V .W .X .Y .Z  Sentinel code treated as greater than any substantive value  • Unrestricted - No restrictions on codes for sentinel values. Use in comparisons is indeterminate.


Notes:
The time period associated with the Population


Notes:
The unit in which the data values are measured (kg, pound, euro).


Notes:
The data type intended to be used by this variable. Supports the optional use of an external controlled vocabulary.


Notes:
Default value is True. The description statement of a universe is generally stated in inclusive terms such as "All persons with university degree". Occasionally a universe is defined by what it excludes, i.e., "All persons except those with university degree". In this case the value would be changed to "false".


Notes:
A semantic term defining the factor used for defining this group


Notes:
Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
Member relations that comprise the relation structure


Notes:
Provides the standard weight used for weighted analysis of data expressed as an xs:float. This element is referenced by the variable and/or statistics calculated using the standard weight.


Notes:
The total number of responses to this variable. This element is especially useful if the number of responses does not match added case counts. It may also be used to sum the frequencies for variable categories.


Notes:
Statistic that provides a summary value, filtered or unfiltered, weighted or unweighted, expressed as an xs:decimal or xs:double


Notes:
Statistics that provides a category specific values, filtered or unfiltered, weighted or unweighted, expressed as an xs:decimal or xs:double


Notes:
A term identifying the subject of the algorithm being described. Supports the use of a controlled vocabulary


Notes:
Short natural language account of the information obtained from the combination of properties and relationships associated with an object. Supports the use of multiple languages and structured text.


Notes:
A term describing the subject of the design. Supports the use of an external controlled vocabulary


Notes:
A term describing the subject of the Methodology. Supports the use of a controlled vocabulary


Notes:
A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided, provide a context to differentiate usage.


Notes:
Explanation of the reasons some decision was made or some object exists. Supports the use of multiple languages and structured text.


Notes:
Provides a high level overview or summary of the class. Can be used to inform end-users or as part of an executive summary. Supports the use of multiple languages and structured text. Edit


Notes:
Provides a high level overview or summary of the class. Can be used to inform end-users or as part of an executive summary. Supports the use of multiple languages and structured text.


Notes:
A linguistic signifier. Human  understandable name (word, phrase, or  mnemonic) that reflects the ISO/IEC  11179-5 naming principles. If more than  one name is provided provide a context to  differentiate usage.


Notes:
Explanation of the ways in which some  decision or object is employed. Supports  the use of multiple languages and  structured text.


Notes:
Explanation of the reasons some decision  was made or some object exists. Supports  the use of multiple languages and  structured text.


Notes:
Short natural language account of the  information obtained from the  combination of properties and  relationships associated with an object.  Supports the use of multiple languages  and structured text.


Notes:
A perceivable object used to denote a signified.


Notes:
Perceivable object in the extension of the signifier. The actual content of this value as a string.


Notes:
Bindings used to pass data into and out of a Process Step.


Notes:
Specifies where the service can be accessed.


Notes:
A description of the boundaries of the polygon either in-line or by a reference to an external file containing the boundaries. Repeatable to describe non-contiguous areas such as islands or Native American Reservations in some parts of the United States.


Notes:
A description of a the boundaries of a polygon internal to the bounding polygon which should be excluded. For example, for the bounding polygon describing the State of Brandenburg in Germany, the Excluding Polygon would describe the boundary of Berlin, creating hole within Brandenburg which is occupied by Berlin.


Notes:
A time for which the polygon is an accurate description of the area. This may be a range (without an end date if currently still valid) or a single date when the shape was know to be valid if a range is not available.


Notes:
Means of describing the area covered by the geographic extent either in its entirety (total area) or specific subsets (land, water, urban, rural, etc.) providing a definition and measurement.


Notes:
Identifies the centroid of a polygon as a specific point


Notes:
The geographic extent is a single point.


Notes:
The period for which the Geographic Unit is valid. Note that the geographic extent, name, or composition change within the valid period of this unit.


Notes:
The Geographic Unit supercedes (follows immediately in time) the described geographic unit. Repeat for multiple geographic units.


Notes:
The Geographic Unit is superceded by (precedes immediately in time) the described geographic unit. Repeat for multiple geographic units.


Notes:
Define the code and Unit Type that is a member of the Geographic Unit Classification. They may be unordered or ordered and assigned to a specific level.


Notes:
The date the classification enters production use and the date on which the Classification was superseded by a successor version or otherwise ceased to be valid. (Source: GSIM Statistical Classification)


Notes:
Indicates if the Classification is currently valid.


Notes:
Indicates if the Classification is a floating classification. In a floating classification, a validity period should be defined for all Classification Items which will allow the display of the item structure and content at different points of time. (Source: GSIM StatisticalClassification/Floating)


Notes:
Provides semantic context for the relationship context for the relationship using an External Controlled Vocabulary. Examples might include "parent-child", or "immediate supervisee"


Notes:
Controlled Vocabulary to specify whether the relation is total, partial or unknown.


Notes:
MemberRelation used to define the relationship of members within the collection


Notes:
Define the code and Unit Type that is a member of the Geographic Unit Type Classification. They may be unordered or ordered and assigned to a specific level.


Notes:
The date the statistical classification enters production use and the date on which the Classification was superseded by a successor version or otherwise ceased to be valid. (Source: GSIM Statistical Classification)


Notes:
Indicates if the Statistical Classification is currently valid.


Notes:
Indicates if the Classification is a floating classification. In a floating statistical classification, a validity period should be defined for all Classification Items which will allow the display of the item structure and content at different points of time. (Source: GSIM StatisticalClassification/Floating)


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an enumeration list.  Use if all relations within this relation structure are of the same specification.


Notes:
Use when multiple physical segments are stored in a single file


Notes:
The number of segments in a Physical Data Product


Notes:
A physical description of the data store encompasses a description of its gross record structure. This structure consists of one or more PhysicalRecordSegments and their relationships. Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
Whether the dataset is a bag or a set: a bag is a collection with duplicates allowed, a set is a collection without duplicates.


Notes:
An explanation of the purpose of the physical dataset


Notes:
Intensional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.)


Notes:
Specifics of relations between InstanceVariables in the PhysicalLayout


Notes:
Use when each physical segment is stored in its own file.


Notes:
A PhysicalRecordSegment has a sequence of DataPoints. Think of these as the cells in the row of a (spreadsheet) table.


Notes:
The DataPointIndicators for this PhysicalRecordSegment have index values that indicate the order of the DataPoints.


Notes:
Indicates that the data are in a delimited format. If not set to true, is FixedWitdh must be set to true.


Notes:
The Delimiting character in the data. Must be used if isDelimited is true. "The separator between cells, set by the delimiter property of a dialect description. The default is ,." see https://www.w3.org/TR/tabular-data-model/#encoding  From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  delimiter: “An atomic property that sets the delimiter flag to the single provided value, which MUST be a string. The default is ",".” From https://www.w3.org/TR/tabular-data-model/ 8 “The separator between cells, set by the delimiter property of a dialect description. The default is ,.” From http://specs.frictionlessdata.io/csv-dialect/ delimiter:  “specifies a one-character string to use as the field separator. Default = ,”


Notes:
Set to true if the file is fixed-width. If true, isDelimited must be set to false.


Notes:
"The string that is used to escape the quote character within escaped cells, or null"  see https://www.w3.org/TR/tabular-data-model/#encoding From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect   “ doupleQuote: A boolean atomic property that, if true, sets the escape character flag to ". If false, to \. The default is true.” From http://specs.frictionlessdata.io/csv-dialect/ doubleQuote: “controls the handling of quotes inside fields. If true, two consecutive quotes should be interpreted as one. Default = true”


Notes:
"The strings that can be used at the end of a row, set by the lineTerminators property of a dialect description. The default is [CRLF, LF]."  see https://www.w3.org/TR/tabular-data-model/#encoding From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  lineTerminators: “An atomic property that sets the line terminators flag to either an array containing the single provided string value, or the provided array. The default is ["\r\n", "\n"].” From http://specs.frictionlessdata.io/csv-dialect/ lineTerminator: “specifies the character sequence which should terminate rows. Default = \r\n”


Notes:
The string that is used around escaped cells, or null, set by the quoteChar property of a dialect description. The default is ". see https://www.w3.org/TR/tabular-data-model/#encoding From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  quoteChar: “An atomic property that sets the quote character flag to the single provided value, which MUST be a string or null. If the value is null, the escape character flag is also set to null. The default is '"'.” From http://specs.frictionlessdata.io/csv-dialect/ quoteChar: “specifies a one-character string to use as the quoting character. Default = "”


Notes:
A string used to indicate that an input line is a comment, a string which precedes a comment in the data file.  From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  commentPrefix: “An atomic property that sets the comment prefix flag to the single provided value, which MUST be a string. The default is "#".”


Notes:
The character encoding of the represented data. From https://www.w3.org/TR/tabular-metadata/ 5.9 Dialect: encoding: “An atomic property that sets the encoding flag to the single provided string value, which MUST be a defined in [encoding]. The default is "utf-8".”     From https://www.w3.org/TR/tabular-metadata/ 7.2 Encoding:  “CSV files should be encoded using UTF-8, and should be in Unicode Normal Form C as defined in [UAX15]. If a CSV file is not encoded using UTF-8, the encoding should be specified through the charset parameter in the Content-Type header:”


Notes:
True if the file contains a header containing column names. From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  header: “A boolean atomic property that, if true, sets the header row count flag to 1, and if false to 0, unless headerRowCount is provided, in which case the value provided for the header property is ignored. The default is true.” From http://specs.frictionlessdata.io/csv-dialect/ header: “indicates whether the file includes a header row. If true the first row in the file is a header row, not data. Default = true”


Notes:
The number of lines in the header From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  headerRowCount: “A numeric atomic property that sets the header row count flag to the single provided value, which MUST be a non-negative integer. The default is 1.”


Notes:
If True, blank rows are ignored. From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  skipBlankRows: “A boolean atomic property that sets the skip blank rows flag to the single provided boolean value. The default is false.”


Notes:
The number of columns to skip at the beginning of the row. From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  skipColumns: “A numeric atomic property that sets the skip columns flag to the single provided numeric value, which MUST be a non-negative integer. The default is 0.” See also https://www.w3.org/TR/tabular-metadata/ 8 skip columns: “The number of columns to skip at the beginning of each row, set by the skipColumns property of a dialect description. The default is 0. A value other than 0 will mean that the source numbers of columns will be different from their numbers.”


Notes:
If true skip spaces at the beginning of a line or following a delimiter. From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  skipInitialSpace: “A boolean atomic property that, if true, sets the trim flag to "start" and if false, to false. If the trim property is provided, the skipInitialSpace property is ignored. The default is false.” From http://specs.frictionlessdata.io/csv-dialect/ skipInitialSpace: “specifies how to interpret whitespace which immediately follows a delimiter; if false, it means that whitespace immediately after a delimiter should be treated as part of the following field. Default = true”


Notes:
Number of input rows to skip preceding the header or data From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  skipRows: “A numeric atomic property that sets the skip rows flag to the single provided numeric value, which MUST be a non-negative integer. The default is 0.” From https://www.w3.org/TR/tabular-metadata/ 8  skip rows: “The number of rows to skip at the beginning of the file, before a header row or tabular data, set by the skipRows property of a dialect description. The default is 0. A value greater than 0 will mean that the source numbers of rows will be different from their numbers.”


Notes:
Specifies which spaces to remove from a data value (start, end, both, neither) From https://www.w3.org/TR/tabular-metadata/  5.9 Dialect  trim: “An atomic property that, if the boolean true, sets the trim flag to true and if the boolean false to false. If the value provided is a string, sets the trim flag to the provided value, which MUST be one of "true", "false", "start", or "end". The default is true.”


Notes:
A string indicating a null value. From https://www.w3.org/TR/tabular-metadata/ 4.3 “null — the string or strings which cause the value of cells having string value matching any of these values to be null.” From Inherited 5.7 null: “An atomic property giving the string or strings used for null values within the data. If the string value of the cell is equal to any one of these values, the cell value is null. See Parsing Cells in [tabular-data-model] for more details. If not specified, the default for the null property is the empty string "". The value of this property becomes the null annotation for the described column.” From http://specs.frictionlessdata.io/csv-dialect/ nullSequence: “specifies the null sequence (for example \N). Not set by default”


Notes:
If True, the case of the labels in the header is significant. From http://specs.frictionlessdata.io/csv-dialect/ caseSensitiveHeader: “indicates that case in the header is meaningful. For example, columns CAT and Cat should not be equated. Default = false”


Notes:
Number cells, rows, columns starting from this value. This is a DDI notion allowing numbering of columns, rows, etc. from either 0 or 1. W3C appears to just use 1. From https://www.w3.org/TR/tabular-data-model/ 4.3 “number — the position of the column amongst the columns for the associated table, starting from 1.”


Notes:
If True, consecutive delimiters are treated the same way as a single delimiter, if false consiecutive delimiters indicate a missing value. From PHDD consecutiveDelimitersAsOne: “Indicates how consecutive delimiters should be handed by the software. Equivalent element in DDI 3.2: p:Delimiter/@treatConsecutiveDelimiterAsOne DDI 3.2 Documentation: http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/complexTypes/DelimiterType.html#a6”


Notes:
Short natural language account of the physical layout obtained from the combination of associated  properties and relationships. Supports the use of multiple languages and structured text.


Notes:
Indicates the direction in which columns are arranged in each row. From https://www.w3.org/TR/tabular-metadata/  5.3.2 tableDirection: “An atomic property that MUST have a single string value that is one of "rtl", "ltr", or "auto". Indicates whether the tables in the group should be displayed with the first column on the right, on the left, or based on the first character in the table that has a specific direction. The value of this property becomes the value of the table direction annotation for all the tables in the table group. See Bidirectional Tables in [tabular-data-model] for details. The default value for this property is "auto".”


Notes:
Indicates the reading order of text within cells. From https://www.w3.org/TR/tabular-metadata/ Inherited 5.7 textDirection: “An atomic property that MUST have a single string value that is one of "ltr", "rtl", "auto" or "inherit" (the default). Indicates whether the text within cells should be displayed as left-to-right text (ltr), as right-to-left text (rtl), according to the content of the cell (auto) or in the direction inherited from the table direction annotation of the table. The value of this property determines the text direction annotation for the column, and the text direction annotation for the cells within that column: if the value is inherit then the value of the text direction annotation is the value of the table direction annotation on the table, otherwise it is the value of this property. See Bidirectional Tables in [tabular-data-model] for details.”


Notes:
The PhysicalLayout contains a description of the physical representation of each InstanceVariable in a ValueMapping. This relationship fills the role of "Contains" from the Collection pattern. Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
The line number, where 1 is the first line, on which to begin counting characters. If missing this defaults to 1 (the first line).


Notes:
The last line on which to count characters. If missing this defaults to startLine.


Notes:
The character position of the first character of the segment, with the count beginning at character 1 of startLine.


Notes:
The character position of the last character of the segment.  If endLine is specified, the count begins at character 1 of endLine. If startLine and endLine are not specified, the count begins at character 1 of the first line of the resource and the count includes any line termination characters. The resulting segment may include text from multiple lines of the resource.


Notes:
The number of characters in the segment. The segment may include text from multiple lines of the resource. If it does, the length includes any line termination characters.


Notes:
The base datatype of the physical representation. An integer InstanceVariable might, for example, be stored as a floating point number. From https://www.w3.org/TR/tabular-metadata/ Inherited 5.7 datatype: “An atomic property that contains either a single string that is the main datatype of the values of the cell or a datatype description object. If the value of this property is a string, it MUST be the name of one of the built-in datatypes defined in section 5.11.1 Built-in Datatypes and this value is normalized to an object whose base property is the original string value. If it is an object then it describes a more specialized datatype. If a cell contains a sequence (i.e. the separator property is specified and not null) then this property specifies the datatype of each value within that sequence. See 5.11 Datatypes and Parsing Cells in [tabular-data-model] for more details.  The normalized value of this property becomes the datatype annotation for the described column. ”


Notes:
Default value is . (period). The string separating the integer part from the fractional part of a decimal or real number. In W3C part of the datatype format From https://www.w3.org/TR/tabular-metadata/ tabular 6.4.2 decimalChar: “A string whose value is used to represent a decimal point within the number. If the supplied value is not a string, implementations MUST issue a warning and proceed as if the property had not been specified.”


Notes:
Default value is null. A string separating groups of digits (for readability). In W3C part of the datatype format From https://www.w3.org/TR/tabular-metadata/ tabular 6.4.2 groupChar: “A string whose value is used to group digits within the number. If the supplied value is not a string, implementations MUST issue a warning and proceed as if the property had not been specified.”


Notes:
A pattern description of the format of a numeric value. In W3C part of the datatype format From https://www.w3.org/TR/tabular-metadata/ tabular 6.4.2 pattern: “A number format pattern as defined in [UAX35] http://www.unicode.org/reports/tr35/tr35-31/tr35-numbers.html#Number_Format_Patterns . Implementations MUST recognise number format patterns containing the symbols 0, #, the specified decimalChar (or "." if unspecified), the specified groupChar (or "," if unspecified), E, +, % and ‰. Implementations MAY additionally recognise number format patterns containing other special pattern characters defined in [UAX35]. If the supplied value is not a string, or if it contains an invalid number format pattern or uses special pattern characters that the implementation does not recognise, implementations MUST issue a warning and proceed as if the property had not been specified.   f the datatype format annotation is a single string, this is interpreted in the same way as if it were an object with a pattern property whose value is that string. If the groupChar is specified, but no pattern is supplied, when parsing the string value of a cell against this format specification, implementations MUST recognise and parse numbers that consist of:  an optional + or - sign, …  Implementations MAY also recognise numeric values that are in any of the standard-decimal, standard-percent or standard-scientific formats listed in the Unicode Common Locale Data Repository. …”


Notes:
A default string indicating the value to substitute for an empty string. From https://www.w3.org/TR/tabular-metadata/ Inherited 5.7  default “An atomic property holding a single string that is used to create a default value for the cell in cases where the original string value is an empty string. See Parsing Cells in [tabular-data-model] for more details. If not specified, the default for the default property is the empty string, "". The value of this property becomes the default annotation for the described column.”


Notes:
A string indicating a null value. From https://www.w3.org/TR/tabular-metadata/ 4.3 null — “the string or strings which cause the value of cells having string value matching any of these values to be null.” From Inherited 5.7 null: “An atomic property giving the string or strings used for null values within the data. If the string value of the cell is equal to any one of these values, the cell value is null. See Parsing Cells in [tabular-data-model] for more details. If not specified, the default for the null property is the empty string "". The value of this property becomes the null annotation for the described column.”


Notes:
This defines the format of the physical representation of the value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 format: “An atomic property that contains either a single string or an object that defines the format of a value of this type, used when parsing a string value as described in Parsing Cells in [tabular-data-model]. The value of this property becomes the format annotation for the described datatype.” See https://www.w3.org/TR/tabular-metadata/ Tabular 6.4.2 ‘Formats for numeric datatypes’  this may include decimalChar, groupChar, pattern  “By default, numeric values must be in the formats defined in [xmlschema11-2]. It is not uncommon for numbers within tabular data to be formatted for human consumption, which may involve using commas for decimal points, grouping digits in the number using commas, or adding percent signs to the number.” See https://www.w3.org/TR/tabular-metadata/ Tabular 6.4. Formats for Booleans   ” Boolean values may be represented in many ways aside from the standard 1 and 0 or true and false.” See https://www.w3.org/TR/tabular-metadata/ 6.4.4. Formats for dates and times “By default, dates and times are assumed to be in the format defined in [xmlschema11-2]. However dates and times are commonly represented in tabular data in other formats.” See https://www.w3.org/TR/tabular-metadata/ 6.4.5 Formats for durations “Durations MUST be formatted and interpreted as defined in [xmlschema11-2], using the [ISO8601] format -?PnYnMnDTnHnMnS. For example, the duration P1Y1D is used for a year and a day; the duration PT2H30M for 2 hours and 30 minutes.” See  https://www.w3.org/TR/tabular-metadata/ 6.4.6 Formats for other types “If the datatype base is not numeric, boolean, a date/time type, or a duration type, the datatype format annotation provides a regular expression for the string values, with syntax and processing defined by [ECMASCRIPT]. If the supplied value is not a valid regular expression, implementations MUST issue a warning and proceed as if no format had been provided.” From DDI3.2 ManagedNumericRepresentation@format “A format for number expressed as a string.” From DDI3.2 ManagedDateTimeRepresentation_DateFieldFormat “Describes the format of the date field, in formats such as YYYY/MM or MM-DD-YY, etc. If this element is omitted, then the format is assumed to be the XML Schema format corresponding to the type attribute value.”


Notes:
The length of the physical representation of the value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 length: “A numeric atomic property that contains a single integer that is the exact length of the value. The value of this property becomes the length annotation for the described datatype. See Length Constraints in [tabular-data-model] for details.” Corresponds to DDI2.5 var/location/width and DDI 3.2 PhysicalLocation/Width


Notes:
The smallest possible value for the length of the physical representation of the value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 minLength: “An atomic property that contains a single integer that is the minimum length of the value. The value of this property becomes the minimum length annotation for the described datatype. See Length Constraints in [tabular-data-model] for details.”


Notes:
The largest possible value of the length of the physical representation of the value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 maxLength: “A numeric atomic property that contains a single integer that is the maximum length of the value. The value of this property becomes the maximum length annotation for the described datatype. See Length Constraints in [tabular-data-model] for details.”


Notes:
The scale of the number expressed as an integer (for example a number expressed in 100's, 5 = 500 would have a scale of 100).   From DDI 3.2 ManagedNumericRepresentation@scale:


Notes:
The number of decimal positions expressed as an integer. Used when the decimal position is implied (no decimal separator is present) See DDI 3.2 ManagedNumericRepresentation@decimalPositions


Notes:
If True a value is required for this variable. NOTE: this might be better at the InstanceVariable or higher in the variable cascade. From https://www.w3.org/TR/tabular-metadata/ Inherited 5.7 required: “A boolean atomic property taking a single value which indicates whether the cell value can be null. See Parsing Cells in [tabular-data-model] for more details. The default is false, which means cells can have null values. The value of this property becomes the required annotation for the described column.”


Notes:
The maximum number of occurrences of an associated CustomValue


Notes:
The minimum number of occurrences of an associated CustomValue


Notes:
Intentional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.)


Notes:
A display label for the RelationStructure. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
Provides information on reflexivity, transitivity, and symmetry of relationship using a descriptive term from an ennumeration list.  Use if all relations within this relation structure are of the same specification. .


Notes:
Member relationships that comprise the relationship structure


Notes:
the value associated with a particular key expressed as a string. The ultimate value representation is defined by the corresponding CustomValue.


Notes:
An explanation (definition) of the value


Notes:
A display label for the OrderRelation. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
Explanation of the ways in which the sample frame is to be employed. Supports use of multiple languages and structured text.


Notes:
An explanation of the intent of the sample frame. Supports the use of multiple languages and structured text.


Notes:
An explanation of any limitations of the sample frame. Supports the use of multiple languages and structured text.


Notes:
A description of how the sample frame is updated and maintained. Supports the use of multiple languages and structured text.


Notes:
The reference period for the sample frame.


Notes:
The period for which the current version is valid


Notes:
The name or number of the specific strata if the sample frame has been stratified prior to sampling within the specified stage


Notes:
The date the sample was selected from the sample frame


Notes:
The algorithm expressed as algebraic or computer code.


Notes:
The goal for the overall size of the sample expressed as an integer.


Notes:
The goal for the overall size of the sample expressed as a decimal (i.e. 70% entered as .7).


Notes:
Repeat for primary and secondary target samples. Supports identification of size, percent, unit type, and universe


Notes:
Specification of a code which relates to an area of coverage of the standard. Supports the use of an external controlled vocabulary.


Notes:
Brief identification of the type of evaluation. Supports the use of an external controlled vocabulary.


Notes:
Describes the evaluation process. Supports multi-lingual content. Allows the optional use of structured content.


Notes:
Describes the outcomes of the evaluation process. Supports multi-lingual content. Allows the optional use of structured content.


Notes:
Identifies the date the evaluation was completed.


Notes:
Describes, with a string or a term from a controlled vocabulary, the kind of data documented in the logical product(s) of a study unit. Examples include survey data, census/enumeration data, administrative data, measurement data, assessment data, demographic data, voting data, etc.


Notes:
A general descriptive overview of the Study


Notes:
Complete bibliographic reference containing all of the standard elements of a citation that can be used to cite the work. The "format" attribute is provided to enable specification of the particular citation style used, e.g., APA, MLA, Chicago, etc.


Notes:
A general descriptive overview of the series.


Notes:
If a standard process model such as The Generic Statistical Business Process Model (GSBPN), the Generic Longitudinal Business Process Model (GLBPM), Open Archive Information System model (OAIS), etc. has been related to this business process, the model and step or sub-step is noted here using the Paired External Controlled Vocabulary Entry. Enter the name of the model in "term" and the step, sub-step, or specific portion of the model in "extent".


Notes:
A condition for beginning the Business Process which may include the specification of the data set required for beginning the Business Process.


Notes:
A condition for completing and exiting the Business Process which may include the specification of the data set resulting from the Business Process.


Notes:
Specifies BusinessProcess that participates in the DataPipeline


Notes:
Allows for the addition of a Purpose, Table of Contents, List of Variables, or other forms of information more specific than a general abstract. Provides both the content (using description) and a type identification using an External Controlled Vocabulary Entry.


Notes:
Default value is False. Indicates that the metadata instance will not be changed without versioning, and is a stable target for referencing.


Notes:
A whitespace-delimited list of the DDI URN identifiers of the objects contained in an XML instance or RDF graph which could be considered the primary objects or entry points. In a Codebook View, for example, the top-level Codebook object, fo example. In some views, such as the Agents View, there my be more than one primary object (Individuals, Organizations, and Machines in this case).


Notes:
Automatically brings in the version number for of DDI 4


Notes:
Designation of the type of material being described. Supports the use of a controlled vocabulary.


Notes:
A description of the referenced material. This field can map to a Dublin Core abstract. Note that Dublin Core does not support structure within the abstract element. Supports multiple languages and optional structured content.


Notes:
Describes the reason the external material is being related to the DDI metadata instance.


Notes:
Provides a standard Internet MIME type for use by processing applications.


Notes:
Can describe a segment within a larger object such as a text or video segment.


Notes:
Bibliographic citation for the external resource.


Notes:
Role of the funding organization or individual. Supports the use of a controlled vocabulary.


Notes:
The identification code of the grant or other monetary award which provided funding for the described object.


Notes:
The command code performed as a part of the transformation or computation


Notes:
Allows for the specification of a computation or transformation type supporting the use of an external controlled vocabulary


Notes:
Condition to be evaluated to determine whether or not to execute the Workflow Sequence in contains. It can be an expression and/or programmatic code. The specialized sub-classes determine whether the Sequence is executed when the condition is true or false


Notes:
The condition to check if the IfThenElse condition is false.


Notes:
The command used to set the initial value for the process. Could be a simple value.


Notes:
The command used to set the incremental or step value for the process. Could be a simple value.


Notes:
Allows for the specification of a transformation type supporting the use of an external controlled vocabulary


Notes:
A definition of the action in XHTML that conforms to the quasi-VTL schema. Each action has its own definition that a user optionally completes.


Notes:
If the content of the parameter is being used in a generic set of code as an alias for the value of an object in a formula (for example source code for a statistical program) enter that name here. This provides a link from the identified parameter to the alias in the code.


Notes:
Provides a default value for the parameter if there is no value provided by the object it is bound to or the process that was intended to produce a value.


Notes:
If set to "true" indicates that the content of the parameter is a delimited array rather than a single object and should be processed as such.limitArrayIndex


Notes:
When the Parameter represents an array of items, this attribute specifies the index identification of the items within the zero-based array which should be treated as that associated with the parameter. If not specified, the full array is treated as the parameter.


Notes:
This is the registered agency code with optional sub-agencies separated by dots. For example, diw.soep, ucl.qss, abs.essg.


Notes:
The ID of the object. This must conform to the allowed structure of the DDI Identifier and must be unique within the Agency.


Notes:
The version number of the object. The version number is incremented whenever the non-administrative metadata contained by the object changes.


Notes:
Explanation of the intent of the Agent Listing. Supports the use of multiple languages and structured text.


Notes:
Specify the type of temporal relationhship between identified WorkflowSteps using Allen's Interval definitions.


Notes:
Whether the collection is a bag or a set: a bag is a collection with duplicates allowed, a set is a collection without duplicates


Notes:
Explanation of the ways in which the pattern is employed. Supports  the use of multiple languages and  structured text.


Notes:
Specifies how to communicate with the service.


Notes:
The estimated time period associated with the operation of the Service. This may be expressed as a time, date-time, or duration.


Notes:
Mapping of specific information flow within the workflow


Notes:
Provides the ability to "type" a sequence for classification or processing purposes. Supports the use of an external controlled vocabulary.


Notes:
The Workflow Steps included in the Collection with an index for position within ordered array.


Notes:
Can bind data attached to parameters into, out of, and between processes.


Notes:
Explanation of the intent of some decision or object. Supports the use of multiple languages and structured text


Notes:
A statement regarding the confidentiality of the related data or metadata.


Notes:
A link to a form used to provide access to the data or metadata including a statement of the purpose of the form.


Notes:
A statement regarding restrictions to access. May be expressed in multiple languages and supports the use of structured content.


Notes:
A statement regarding the citation requirement. May be expressed in multiple languages and supports the use of structured content.


Notes:
A statement regarding depositor requirements. May be expressed in multiple languages and supports the use of structured content.


Notes:
A statement regarding conditions for access. May be expressed in multiple languages and supports the use of structured content.


Notes:
A disclaimer regarding the liability of the data producers or providers. May be expressed in multiple languages and supports the use of structured content.


Notes:
The agent to contact regarding access including the role of the agent.


Notes:
The date range or start date of the access description.


Notes:
The easternmost coordinate expressed as a decimal between the values of -180 and 180 degrees


Notes:
The westernmost coordinate expressed as a decimal between the values of -180 and 180 degrees


Notes:
The northernmost coordinate expressed as a decimal between the values of -90 and 90 degrees.


Notes:
The southermost latitude expressed as a decimal between the values of -90 and 90 degrees


Notes:
A generic description including temporal, topical, and spatial coverage that is the equivalent of dc:coverage (the refinement base of dcterms:spatial and dcterms:temporal. Use specific coverage content for detailed information. Short natural language account of the information obtained from the combination of properties and relationships associated with an object. Supports the use of multiple languages and structured text.


Notes:
A textual description of the spatial coverage to support general searches.


Notes:
Supports the use of a standardized code such as ISO 3166-1,  the Getty Thesaurus of Geographic Names, FIPS-5, etc.


Notes:
Indicates the most discrete spatial object type identified for a single case. Note that data can be collected at a geographic point (address) and reported as such in a protected file, and then aggregated to a polygon for a public file.


Notes:
A date referencing a specific aspect of temporal coverage. The date may be typed to reflect coverage date, collection date, referent date, etc. Subject and Keywords may be associated with the date to specify a specific set of topical information (i.e. Residence associated with a date 5 years prior to the collection date).


Notes:
A subject that describes the topical coverage of the content of the annotated object. Subjects are members of structured classification systems such as formal subject headings in libraries. Uses and InternationalCodeValue and may indicate the language of the code used.


Notes:
A keyword that describes the topical coverage of the content of the annotated object.  Keywords may be structured (e.g. TheSoz thesauri) or unstructured and reflect the terminology found in the document and other related (broader or similar) terms.  Uses and InternationalCodeValue and may indicate the language of the code used.


Notes:
A name for the measurement. A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.


Notes:
A description of the purpose or use of the Measurement. May be expressed in multiple languages and supports the use of structured content.


Notes:
The source of a capture structure defined briefly; typically using an external controlled vocabulary


Notes:
Identifies the unit being analyzed such as a Person, Housing Unit, Enterprise, etc.


Notes:
A description of the purpose or use of the Member. May be expressed in multiple languages and supports the use of structured content.


Notes:
Specification of the type of instrument according to the classification system of the documentor.


Notes:
A reference to an external representation of the the data collection instrument, such as an image of a questionnaire or programming script.


Notes:
The name of a question as used in an Instrument. Redefined to provide a more useful description. A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.


Notes:
The content of the Instruction text provided using DynamicText. Note that when using Dynamic Text, the full InstructionText must be repeated for multi-language versions of the content. The InstructionText may also be repeated to provide a dynamic and plain text version of the instruction. This allows for accurate rendering of the instruction in a non-dynamic environment like print.


Notes:
The purpose of the code (e.g., quality control, edit check, checksums, compute filler text, compute values for use in administering the instrument)


Notes:
Describes the code used to execute the command using the options of inline textual description, inline code, and/or an external file.


Notes:
Identification of the numeric type such as integer, decimal, etc. supports the use of an external controlled vocabulary.


Notes:
An optional unit of measurement.  Examples include units from the International System of Units (SI) such as meter, seconds, mole, kilograms. Other examples include miles, tons, pints.


Notes:
Defines the valid number range or number values for the representation.


Notes:
The text of the question which may be literal or dynamic (altered to personalize the question text) in terms of content.


Notes:
An estimation of the number of seconds required to respond to the question. Used for estimating overall questionnaire completion time.


Notes:
A display label for the domain. May be expressed in multiple languages.


Notes:
Structured human-readable text that allows for dynamic content. For example, the insertion of a name or gender specific pronoun. Repeat ONLY for capturing the same content in multiple languages.


Notes:
Describes the use of the statement within the instrument. For example, a section divider, welcome statement, or other text.


Notes:
The maximum number of characters allowed.


Notes:
The minimum number of characters allowed.


Notes:
A regular expression limiting the allowed characters or character order of the content. Use typeOfContent to specify the syntax of the regularExpression found in content.


Notes:
A map defining the match relationship and the members in the relationship


Notes:
Describes the relationship between the source and target members using both controlled vocabularies and descriptive text.


Notes:
Pointers to members of the collection that are unordered or in an indexed ordered array.


Notes:
Set to true if the members are in an ordered set. If unordered set to false.


Notes:
Provides annotation information on the object to support citation and crediting of the creator(s) of the object.


Notes:
Contributor who has the ownership and responsibility for the current version.


Notes:
The reason for making this version of the object.


Notes:
The date and time the object was changed. Supports standard ISO date and datetime formats.


Notes:
Default value is false. Usually the combination of agency and id (ignoring different versions) is unique. If isUniversallyUnique is set to true, it indicates that the id itself is universally unique (unique across systems and/or agencies) and therefore the agency part is not required to ensure uniqueness.


Notes:
Default value is false. Usually the content of the current version is allowed to change, for example as the contributor is working on the object contents. However, when isPersistent is true, it indicates the there will be no more changes to the current version.


Notes:
This is an identifier in a given local context that uniquely references an object, as opposed to the full ddi identifier which has an agency plus the id. For example, localId could be a variable name in a dataset.


Notes:
The object/version that this object version is based on.


Notes:
Default character set used in the Data Store.


Notes:
The type of DataStore. Could be delimited file, fixed record length file, relational database, etc. Points to an external definition which can be part of a controlled vocabulary maintained by the DDI Alliance.


Notes:
The number of records in the Data Store.


Notes:
General information about missing data, e.g., that missing data have been standardized across the collection, missing data are present because of merging, etc.-  corresponds to DDI2.5 dataMsng.


Notes:
Data in the form of Data Records contained in the Data Store. Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
The DataStores in the Catalog. Allows for the identification of the member and optionally provides an index for the member within an ordered array


Notes:
Specification of the type of Signification


Notes:
Controlled vocabulary for the order relation semantics. It should contain, at least, the following: Self_Or_Descendant_Of, Part_Of, Less_Than_Or_Equal_To, Subtype_Of, Subclass_Of.


Notes:
Member relations of InstanceVariables that comprise the relation structure


Notes:
Specifies contents of Unit Record as Instance Variable values.


Notes:
Logical Record relations that comprise the relation structure


Notes:
Correspondences between Instance Variables of different Logical Record Layout.


Notes:
An identifier within a specified system for specifying an agent


Notes:
References an image using the standard Image description. In addition to the standard attributes provides an effective date (period), the type of image, and a privacy ranking.


Notes:
The effective start and end date of the relationship


Notes:
Define the level of privacy regarding this relationship. Supports the use of a controlled vocabulary.


Notes:
Explanation of the intent of creating the relation. Supports the use of multiple languages and structured text.


Notes:
Provides semantic context for the relation structure


Notes:
Agent relations that comprise the relation structure


Notes:
The name of an individual broken out into its component parts of prefix, first/given name, middle name, last/family/surname, and suffix.


Notes:
The agency identifier of the individual according to the DDI Alliance agent registry.


Notes:
Contact information for the individual including location specification, address, URL, phone numbers, and other means of communication access. Sets of information can be repeated and date-stamped.


Notes:
The kind of machine used - software, web service, physical machine, from a controlled vocabulary


Notes:
The name of the machine. A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.


Notes:
The locations where the machine can be access


Notes:
Specified the machine interface. Supports the use of a controlled vocabulary.


Notes:
Contact information for the owner/operator including location specification, address, URL, phone numbers, and other means of communication access. Sets of information can be repeated and date-stamped.


Notes:
Names by which the organization is known.


Notes:
The agency identifier of the organization as registered at the DDI Alliance register.


Notes:
Contact information for the organization including location specification, address, URL, phone numbers, and other means of communication access. Sets of information can be repeated and date-stamped.


Notes:
Text of the authorization (law, mandate, approved business case).


Notes:
Provide a legal citation to a law authorizing the study/data collection. For example, a legal citation for a law authorizing a country's census.


Notes:
Allows for the identification of the member Classification Series and optionally provides an index for the member within an ordered array


Notes:
Date when the current version of the Classification Index was released.


Notes:
A Classification Index can exist in several languages. Indicates the languages available. If a Classification Index exists in several languages, the number of entries in each language may be different, as the number of terms describing the same phenomenon can change from one language to another. However, the same phenomena should be described in each language. Supports the indication of multiple languages within a single property. Supports use of codes defined by the RFC 1766.


Notes:
Verbal summary description of corrections, which have occurred within the Classification Index. Corrections include changing the item code associated with an Classification Index Entry.


Notes:
Additional information which drives the coding process for all entries in a Classification Index.


Notes:
Text describing the type of object/unit or object property.


Notes:
Date from which the Classification Index Entry became valid (startDate). The date must be defined if the Classification Index Entry belongs to a floating Classification Index. Date at which the Classification Index Entry became invalid (endDate). The date must be defined if the Classification Index Entry belongs to a floating Classification Index and is no longer valid.


Notes:
Additional information which drives the coding process. Required when coding is dependent upon one or many other factors.


Notes:
Indicates whether or not the item is currently valid. If updates are allowed in the Statistical Classification, an item may be restricted in its validity, i.e. it may become valid or invalid after the Statistical Classification has been released.


Notes:
Indicates whether or not the item has been generated to make the level to which it belongs complete


Notes:
A Classification Item may be associated with explanatory notes, which further describe and clarify the contents of the Category. Explanatory notes consist of: General note: Contains either additional information about the Category, or a general description of the Category, which is not structured according to the "includes", "includes also", "excludes" pattern. Includes: Specifies the contents of the Category. Includes also: A list of borderline cases, which belong to the described Category. Excludes: A list of borderline cases, which do not belong to the described Category. Excluded cases may contain a reference to the Classification Items to which the excluded cases belong.


Notes:
The future events describe a change (or a number of changes) related to an invalid item. These changes may e.g. have turned the now invalid item into one or several successor items. This allows the possibility to follow successors of the item in the future.


Notes:
Describes the changes, which the item has been subject to during the life time of the actual Statistical Classification.


Notes:
Describes the changes, which the item has been subject to from the previous version to the actual Statistical Classification


Notes:
Dates for which the classification is valid. Date from which the item became valid. The date must be defined if the item belongs to a floating Statistical classification. Date at which the item became invalid. The date must be defined if the item belongs to a floating Statistical classification and is no longer valid


Notes:
A Classification Item has a name as provided by the owner or maintenance unit. The name describes the content of the category. The name is unique within the Statistical Classification to which the item belongs, except for categories that are identical at more than one level in a hierarchical classification. Use the context attribute to identify Official Name or alternate names for the Classification Item.


Notes:
The value as expressed in the data file.


Notes:
ClassificationSeries can be designed in a specific context. Supports the use of and External Controlled Vocabulary.


Notes:
A ClassificationSeries is designed to classify a specific type of object/unit according to a specific attribute.


Notes:
Areas of statistics in which the ClassificationSeries is implemented.


Notes:
A ClassificationSeries can be associated with one or a number of keywords.


Notes:
CodeRelations making up the relation structure.


Notes:
Effective period of validity of the CorrespondenceTable. The correspondence table expresses the relationships between the two NodeSets as they existed on the period specified in the table.


Notes:
Set of mappings between nodes that participate in the correspondence.


Notes:
A perceivable object used to denote a signified, i.e. a concept in this case.


Notes:
A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided


Notes:
Index Entry Relations  that comprise the relationship structure


Notes:
Explanation of the ways in which some decision or object is employed. Supports the use of multiple languages and structured text. Use in locations where you need to relay information on the usage of the instantiated class.


Notes:
The association of a level number in an ordered array with the description of that level


Notes:
The dates for which the level structure is valid.  A structured DateRange with start and end Date (both with the structure of Date and supporting the use of ISO and non-ISO date structures); Use to relate a period with a start and end date.


Notes:
The type of platform under which sentinel codes will be used. Statistical software platforms use different sets of codes to indicate missing values. The external controlled vocabulary should list platform tpes and a description of the allowed missing value types. A sample list would be: • BlankString - A Blank string indicates missing. Comparison is based on lexical order.  • EmptyString - An empty string indicates missing. Use in comparisons returns missing.   • Rstyle - Codes drawn from  NA and the IEEE 754 values of  NaN  -Inf   +Inf.   Comparisons return NA.   • SASNumeric - codes drawn from . ._ .A .B .C .D .E .F .G .H .I .J .K .L .M .N .O .P .Q .R .S .T .U .V .W .X .Y .Z    Sentinel code treated as less than any substantive value   • SPSSstyle - System missing (a dot) a set of individual values drawn from the same datatype as the SubstantiveValueDomain, and a range of values  drawn from the same datatype as the SubstantiveValueDomain.  Comparisons return system missing.  Some functions substitute with valid values (e.g. SUM replaces missing values with 0)   • StataNumeric - codes drawn from . ._ .A .B .C .D .E .F .G .H .I .J .K .L .M .N .O .P .Q .R .S .T .U .V .W .X .Y .Z  Sentinel code treated as greater than any substantive value  • Unrestricted - No restrictions on codes for sentinel values. Use in comparisons is indeterminate.


Notes:
Date the Statistical Classification was released


Notes:
The date the statistical classification enters production use and the date on which the Statistical Classification was superseded by a successor version or otherwise ceased to be valid. (Source: GSIM Statistical Classification)


Notes:
Indicates if the Statistical Classification is a floating classification. In a floating statistical classification, a validity period should be defined for all Classification Items which will allow the display of the item structure and content at different points of time. (Source: GSIM StatisticalClassification/Floating


Notes:
Describes the relationship between the variant and its base Statistical Classification, including regroupings, aggregations added and extensions. (Source: GSIM StatisticalClassification/Changes from base Statistical Classification)


Notes:
If the Statistical Classification is a variant, notes the specific purpose for which it was developed. (Source: GSIM StatisticalClassification/Purpose of variant)


Notes:
Copyright of the statistical classification.


Notes:
Summary description of changes which have occurred since the most recent classification version or classification update came into force.


Notes:
A list of languages in which the Statistical Classification is available. Supports the indication of multiple languages within a single property. Supports use of codes defined by the RFC 1766.


Notes:
A formal description of the set of values.


Notes:
A logical expression where the values of "x" making the expression true are the members of the set of valid values.  Example: (all reals x such that  x >0) describes the real numbers greater than 0


Notes:
A regular expression where strings matching the expression belong to the set of valid values. Use typeOfContent to specify the syntax of the regularExpression found in content.


Notes:
A string denoting the minimum possible value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 minimum: “An atomic property that contains a single number or string that is the minimum valid value (inclusive); equivalent to minInclusive. The value of this property becomes the minimum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.”


Notes:
A string denoting the maximum possible value. From https://www.w3.org/TR/tabular-metadata/  5.11.2 maximum: “An atomic property that contains a single number or string that is the maximum valid value (inclusive); equivalent to maxInclusive. The value of this property becomes the maximum annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.”


Notes:
A string denoting the minimum possible value (excluding this value) From https://www.w3.org/TR/tabular-metadata/  5.11.2 minExclusive: “An atomic property that contains a single number or string that is the minimum valid value (exclusive). The value of this property becomes the minimum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.”   DDI3.2 handles this with a Boolean isInclusive attribute.


Notes:
A string denotFrom https://www.w3.org/TR/tabular-metadata/  5.11.2 maxExclusive: “An atomic property that contains a single number or string that is the maximum valid value (exclusive). The value of this property becomes the maximum exclusive annotation for the described datatype. See Value Constraints in [tabular-data-model] for details.”   DDI3.2 handles this with a Boolean isInclusive attribute. ing the maximumpossible value (excluding this value)


Notes:
Indicates the type of relationship, nominal, ordinal, interval, ratio, or continuous. Use where appropriate for the representation type.


Notes:
A pattern for a number as described in Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html) Part 3: Numbers  (http://www.unicode.org/reports/tr35/tr35-numbers.html#Number_Format_Patterns) and Part 4. Dates (http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns) . Examples would be    #,##0.### to describe the pattern for a decimal number, or yyyy.MM.dd G 'at' HH:mm:ss zzz for a datetime pattern.


Notes:
The data types that are recommended for use with this domain


# t_connector

Notes:
Any subtype of an enumeration domain enumerating the set of valid values.


Notes:
A formal description of the set of valid values - for described value domains.


Notes:
Corresponding conceptual definition given by an SubstantiveConceptualDomain.


Notes:
A complex structure, hierarchical, for a ClassificationItem. Restricted to single structure.


Notes:
Statistical Classification that supersedes the actual Statistical Classification (for those Statistical Classifications that are versions or updates),


Notes:
Statistical Classification superseded by the actual Statistical Classification (for those Statistical Classifications that are versions or updates).


Notes:
ClassificationIndex(es) related to the StatisticalClassification.


Notes:
Statistical Classification on which the current variant is based, and any subsequent versions of that Statistical Classification to which it is also applicable.


Notes:
Description and link to a publication, including print, PDF, HTML and other electronic formats, in which the Statistical Classification has been published. This is similar to dcat:Distribution.


Notes:
Organization, agency, or group within an agency responsible for the maintenance and upkeep of the statistical classification.


Notes:
Any subtype of an Enumeration Domain enumerating the set of valid values.


Notes:
Corresponding conceptual definition given by a SentinelConceptualDomain.


Notes:
Class of the Collection pattern realized by this class.


Notes:
The conceptual basis for the collection of members.


Notes:
Has meaningful level to which members belong.


Notes:
CategorySet associated with the enumeration


Notes:
Class in the Signification Pattern realized by Designation. A Designation is a type of Sign.


Notes:
The person(s) who may be contacted for additional information about the Correspondence Table. Can be an individual or organization.


Notes:
The unit or group of persons who are responsible for the Correspondence Table, i.e. for maintaining and updating it.


Notes:
The statistical office, other authority or section that created and maintains the Correspondence Table. A Correspondence Table may have several owners.


Notes:
A list of the publications in which the Correspondence Table has been published.


Notes:
Level to which the correspondence is made. Correspondences might be restricted to a certain Level in the NodeSet. In this case, target items are assigned only to source items on the given level. If no level is indicated, target items can be assigned to any level of the source NodeSet.


Notes:
Level from which the correspondence is made. Correspondences might be restricted to a certain Level in the NodeSet. In this case, target items are assigned only to source items on the given level. If no level is indicated, source items can be assigned to any level of the target NodeSet.


Notes:
The Statistical Classification(s) from which the correspondence is made.


Notes:
A complex structure, hierarchical, for a CodeList. Restricted to single structure.


Notes:
The Collection pattern class realized by this class


Notes:
A definition for the code. Specialization of denotes for Categories.


Notes:
The statistical office or other authority, which created and maintains the StatisticalClassification (s) related to the ClassificationSeries. A ClassificationSeries may have several owners.


Notes:
Description of a complex structure for the Collection. A collection may be structured in more than one way for different uses.


Notes:
Classification Items to which the excluded cases belong (as described in explanatoryNotes).


Notes:
Case law rulings related to the Classification Item.


Notes:
Person(s) who may be contacted for additional information about the Classification Index.


Notes:
The unit or group of persons within the organization responsible for the Classification Index, i.e. for adding, changing or deleting Classification Index Entries.


Notes:
A list of the publications in which the Classification Index has been published.


Notes:
ClassificationIndexes associated to the ClassificationFamily.


Notes:
References the authorizing agent generally described as an organization or individual


Notes:
Collection Pattern class realized by this class


Notes:
An Agent can perform the role of a Member in an Agent Registry


Notes:
Collection pattern class realized by the class


Notes:
The InstanceVaribles functioning as attributes


Notes:
The InstanceVaribles functioning as measures


Notes:
The InstanceVaribles functioning as identifiers


Notes:
A UnitDataRecord may have multiple ViewPoints, each of which assigns among roles identifier, measure, and attribute to the InstanceVariables associated with each Datapoint


Notes:
Describe the order of InstanceVariables in a record for those cases where the variables have a more complicated logical order than a simple sequence.


Notes:
Map related record types, which are Collections of Instance Variables. Realization of structures in Symmetric Relation.


Notes:
Specifies the subtype of collection realized by this class


Notes:
A Datum is bounded by an InstanceVariable. The Datum is drawn from a set of values, either substantive or sentinel described by the value domain of the InstanceVariable


Notes:
Whereas a DataStore is associated with a Study, a DataSoreLibrary is associated with a StudySeries. Each StudySeries has at most one DataStoreLibrary


Notes:
The Record Relation that defines the relationship and linking requirements between LogicalRecords in the DataStore


Notes:
A Study has at most one DataStore. Many studies can have the same set of record types.


Notes:
Allows the DataStore to function as a Collection, enabling, for example,  ordering of its components.


Notes:
Classes which realize the class Member fufill the role of Member e.g. they may have relations defined on them, for example one DataPoint follows another in a  Record.


Notes:
The InstanceVariable delimits the values which can populate a DataPoint.


Notes:
Used to reference external resources. Should include the citation to such material, an external reference to a URI, and a statement of the relationship of the material to the object it has been associated with.


Notes:
A relation structure that provides complex organization of the collection


Notes:
Second member in the relationship. Notes this could be realized as a collection supporting tuple relationship.


Notes:
The member(s) defined as the target of the mapping. If relationship is disjoint do not use target relationship.


Notes:
The member defined as the source in the relationship. Note that when a correspondence has been defined as disjoint only the source relationship should be used.


Notes:
The collection(s) contianing the mapped members.


Notes:
A parameter which can be used to bind the output of this response domain to another parameter to direct the flow of the captured datum.


Notes:
Associates the ResponseDomain with the RepresentedVariable that the question will populate into an InstanceVariable when fielded.


Notes:
An optional link to a represented variable which can be used by each instance variable created by a use of this question.


Notes:
An optional link to a represented variable which can be used by each instance variable created by a use of this measure.


Notes:
Any external object used to clarify, inform, or support the role of the instrument component


Notes:
An instrument compoment can have zero to many instructions


Notes:
An image or other external material associated with the Instruction, located at the provided URN or URL.


Notes:
The measurement being instantiated in the data collection process


Notes:
The ConceptualInstrument which informs the design of the ImplementedInstrument.


Notes:
Refers to the RepresentedMeasures and RepresentedQuestions used by the ConceptualInstrument.


Notes:
Optionally allows specifying the Code to which a secondary response domain is attached. For example, link to code which signifies "Other" within this CodeList.


Notes:
Optionally allows specifying the attached secondary response domain used by a specific item within this CodeListResponseDomain. For example, attach a TextResponseDomain to the code for "Other" using the TextDomain label (Please specify) as a label for the TextDomain. The attached secondary response domain must also be added to the Represented Question or Measure.


Notes:
The CodeList which includes the response options to list.


Notes:
The category to which a boolean response is requested.


Notes:
The lowest geographic unit type identified within this coverage. Repeat if multiple geographic hierarchies are used and there is no single lowest level that can be used to compile geographic areas into higher levels. For example a file that has one hierarchy using State-County-CensusTract/BNA and also data identified for Place which cannot be constructed directly from Census Tracts as they may cross Place boundaries.


Notes:
The unit type describing the highest or broadest geographic unit type that can be assembled within this coverage. In some cases with multiple hierarchies there may be multiple geographic unit types assembled.


Notes:
The geographic units used within this coverage.


Notes:
The geographic unit types used within this coverage.


Notes:
A classification which describes the geographic units (specific locations) and relationships used within this coverage.


Notes:
A classification which describes the geographic unit types and relationships used within this coverage.


Notes:
The north and south latitudes and east and west longitudes that define the spatial coverage area.


Notes:
Description of the spatial (geographic) coverage of the contents of the annotated object.


Notes:
The topics covered by the contents of the annotated object. These may be expressed by subject classification systems and structured or unstructured keywords.


Notes:
The dates and time periods described by the contents of the annotated object.


Notes:
Used by Binding to link the output of this class to the input of another class


Notes:
Used by Binding to link the output of another class to the input of this class


Notes:
Comparison of Result of the Process against the Goal to inform further activities.


Notes:
The result may have one or more specific usages which provides guidance for the use of the result with a specific unit type.


Notes:
The Precondition may be based on the Results of earlier Processes, indicated with this relationship.


Notes:
Identifies material discussing the precondition. The material may be in DDI or other format.


Notes:
Identifies material discussing the goal. The material may be in DDI or other format.


Notes:
Specifies the object for which the guide is appropriate


Notes:
The unit type or types for which the guide is appropriate


Notes:
The guide describing the appropriate usage of the result in the context of specified unit types and/or objects.


Notes:
An identification for a Parameter related to the WorkflowStep and referred to by a Binding indicating the Output from the WorkflowStep


Notes:
An identification for a Parameter related to the WorkflowStep and referred to by a Binding indicating the Input to the WorkflowStep


Notes:
Class in the ProcessPattern realized by WorkflowStep.


Notes:
Identifies the Service Implementation which performs the Workflow Step. Specialization of isPerformedBy in Process Step for Service Implementations.


Notes:
Class in the Process Pattern realized by Workflow Service.


Notes:
Actor that performs a role in the service,


Notes:
Points to the WorkflowControlStep subtype which defines the starting point for initiating the set of process steps contained in the process.


Notes:
ProcessPattern class realized by this class


Notes:
The algorithms implemented by the process. May be expressed by AlgorithmOverview or any subclass


Notes:
The WorkflowSteps executed by the control mechanism


Notes:
A realization of the specified Process Pattern class


Notes:
If the content of the parameter contains representational content, such as codes, provide the representation here. ValueDomain is the abstract with a number of subtype and may be replaced with any valid substitution for ValueDomain. Inclusion of the valueRepresentation is recommended if you will be sharing data with others as it provides information on the structure of what they can expect to receive when the parameter is processed.


Notes:
Optional sequence of Process Steps that are triggered for execution when the condition is false.


Notes:
The Workflow Sequence is executed depending on the result of the condition evaluation. The specialized sub-classes determine whether the Sequence is executed when the condition is true or false. Specialization of contains in Control Construct.


Notes:
The source of the funding expressed as an Organization or Individual.


Notes:
Allows for listing information on any material external to the DDI metadata instance that is related to it.


Notes:
Describes funding source by description, grant number, and link to funding agent


Notes:
Access control imposed by the local distributor. For example, distribution only to registered users of a system or members of an association. Provides information on access restrictions as well as the process to gain access.


Notes:
Access control that will persist over time, generally imposed by the producer (i.e. embargo limits, confidentiality constraints). Provides information on access restrictions as well as the process to gain access.


Notes:
Describes the coverage of the document as a whole.


Notes:
A study has at most one DataPipeline. The same DataPipeline can be used in many studies.


Notes:
Description of a complex structure for the Collection. A collection may be structured in more than one way for different uses


Notes:
A StudySeries can contain multiple Studies, or even StudySeries


Notes:
Study that is the target of the StudyControl


Notes:
Makes use of the Agent Listing to define relationships between agents.


Notes:
A Study may relate to a multiple collections of variables which may be defined by type, subject, use, source, etc.


Notes:
A Study may relate to multiple concepts. These may also be denoted by keywords in an Annotation.


Notes:
A relationship to a description of a simple overview, in which case the AlgorithmOverView class should be the target.


Notes:
A relationship to a description of a simple overview, in which case the MethodologyOverView class should be the target.


Notes:
The methodologies for sampling employed by the study.


Notes:
Evaluation for the purpose of reviewing the study, data collection, data processing, or management processes.


Notes:
A Study can be a member of a Collection (a StudySeries)


Notes:
A variable describing actual instances of data as recorded in the study. An example might be self reported gender, with categories of male encoded as "0"  and female encoded as "1", with missing values recorded as  "-9" for refused and "-8" as "not asked", recorded (physically) as an integer.


Notes:
A description of the budget for the Study


Notes:
A statement of quality which may be related to an external standard or contain a simple statement of internal quality goals or expectations.


Notes:
The authorizing agency and allows for the full text of the authorization (law, regulation, or other form of authorization).


Notes:
Information about the individual, agency and/or grant(s) which funded the described entity.


Notes:
Information relating to the availability of data from the study.


Notes:
Information about data that are not currently available because of policies established by the principal investigators and/or data producers.


Notes:
The implemented instruments used in capturing the data. The ImplentedInstrument designates the mode of delivery, a relation to an external representation of the instrument, and reference to the conceptual instrument that contains more detailed information on the content of the instrument.


Notes:
Overview of the Process employed in the Study


Notes:
The defined classes of Units related to the data,  Examples: 1. Canadian adults (not limited to those residing in Canada) 2. Computer companies 3. Universities


Notes:
The set of specific Units studied. Examples: 1. Canadian adult persons residing in Canada on 13 November 1956 2. US computer companies at the end of 2012 3. Universities in Denmark 1 January 2011.


Notes:
Unit(s) of analysis for the study, e.g. persons, households.


Notes:
Spatial, Temporal, and Topical coverage information for the Study


Notes:
A series in which this Study takes part.


Notes:
Provide the citation and location of the published standard using the OtherMaterialType.


Notes:
Allows for a quality statement based on frameworks to be described using itemized properties. A reference to a concept, a coded value, or both can be used to specify the property from the standard framework identified in StandardUsed. Usage can provide further details or a general description of compliance with a standard.


Notes:
Identifies the external standard used and describes the level of compliance with the standard in terms specific aspects of the standard's content.


Notes:
Agent responsible for enforcing the embargo


Notes:
Agent (Organiztion, Individual, etc.) that is responsible for the embargo


Notes:
A reference to a concept which relates to an area of coverage of the standard.


Notes:
References to one or more external budget documents.


Notes:
The sampling algorithm implanted by this sampling process. Constraint of the relationship implementsAlgorithm in Process pattern class by limiting the target to a SamplingAlgorithm


Notes:
Results of the Sampling Process. Restriction to SamplePopulation, a  type of Result


Notes:
The Process Sequence which initiate the process flow and describes the sequence of the process flow


Notes:
Description and link to external material discussing this Sampling Process


Notes:
A Sampling Procedure that is a component part of this Sampling Procedure


Notes:
Sampling Algorithm that defines the methodology in a generic way


Notes:
Sampling Process used to perform the Sampling Procedure


Notes:
Sampling Design used to perform the Sampling Procedure


Notes:
The design of the expressed algorithm is implemented by the Sampling Process. Constrains impliementedBy of the Design Pattern by limiting the target to a Sampling Process.


Notes:
Specification of the goal for the Sampling Design. Constrained to SamplingGoal.


Notes:
Is an expression of this Sampling Algorithm


Notes:
The population represented by the sample


Notes:
The Unit Type of the units within the sample.


Notes:
SampleFrame can be an output related to a sampling process.


Notes:
SampleFrame can serve as an input to a sampling process.


Notes:
A sample frame which served as a source for the sample frame being described


Notes:
A secondary unit type identifiable with the population


Notes:
The population included in the sample frame


Notes:
Accessibility of the sample frame including means of accessing


Notes:
The agent who is primarily responsible for the maintenance of the sample frame


Notes:
Class can play the role of a Member in a Collection


Notes:
This optional relationship indicates an InstanceVariable compatible with the value associated with this key. Custom metadata might be reused as data and data might be used as metadata. This mechanism could enable these transformations. The related InstanceVariable could also carry information about units of measurement, missing values etc.


Notes:
The CustomItem which defines the key for this key,value pair, It also defines a ValueRepresentation


Notes:
Collection pattern class realized by this class


Notes:
This optional relationship indicates a RepresentedVariable compatible with this key. Custom metadata might be reused as data and data might be used as metadata. This mechanism could enable these transformations.


Notes:
A Concept associated with the key of a CustomValue


Notes:
The type of value for the key.value pair


Notes:
The RelationStructure defining hierarchy or specific realtionships between vocabulary entries in the vocabulary


Notes:
ValueMappings are members of the PhysicalLayout.


Notes:
Uses a PhysicalSegmentLocation to describe where in the physical record a segment representing the InstanceVarible is. This could be, for example, described as a start position and end position value for characters in a text record via the SegmentByText extension of PhysicalSegmentLocation.


Notes:
Describes the physical representation of the InstanceVariable


Notes:
Logical Record physically represented by the Physical Layout.


Notes:
This relationship allows the PhysicalLayout to play the role of a collection that contains ValueMappings.


Notes:
There may be cases where there is a more complex structure to a sequence of DataPoints. A cell containing a list, for example, might be considered to have nested DataPoints that are the elements of the list.


Notes:
Collections class realized by this class


Notes:
Every DataRecord has at o..n PhysicalRecordSegments, It is possible to describe a PhysicalDataProduct and its RecordRecordSegment(s) without reference to a DataRecord


Notes:
A record segment may represent a specific population or sub-population within a larger set of segments. Allows for the identification of this filter for membership in the segment.


Notes:
A PhysicalRecordSegment is associated with a one or more reusable PhysicalLayouts


Notes:
Variable Statistics related to the Physical Data Set. May be summary or category level statistics.


Notes:
Data Store physically represented by the Structure Description.


Notes:
Geographic Unit Type Structure that supersedes the actual Classification (for those Classifications that are versions or updates),


Notes:
Geographic Unit Type Structure superseded by the actual Classification (for those Classifications that are versions or updates).


Notes:
Geographic Unit Type Structure on which the current variant is based, and any subsequent versions of that Classification to which it is also applicable.


Notes:
Organization, agency, or group within an agency responsible for the maintenance and upkeep of the classification.


Notes:
A relation structure used to describe complex relationships between the members


Notes:
May reference an existing concept system generally of Geographic Unit Types


Notes:
Geographic Unit Type Structure that supersedes the actual Statistical Classification (for those Statistical Classifications that are versions or updates).


Notes:
Geographic Unit Classification superseded by the actual Classification (for those Classifications that are versions or updates).


Notes:
Geographic Unit Classification on which the current variant is based, and any subsequent versions of that Classification to which it is also applicable.


Notes:
May reference an existing concept system generally of Geographic Unit


Notes:
Describes the geographic extent or coverage of the geographic unit during the specified period of time.


Notes:
A Bounding Box (North, South Latitude and East, West Longitude) for the geographic extent.


Notes:
An identification for a Parameter related to the ProcessStep and referred to by a Binding as Output from the ProcessStep.


Notes:
An identification for a Parameter related to the ProcessStep and referred to by a Binding as Input to the ProcessStep.


Notes:
The ProcessSteps whose execution order is defined by the control structure.


Notes:
The Process Step which describes the organization of the process flow. This could be realizes as a sequence, a temporal relationship, or conditional control step. When appropriate to a realization it could be realized as a single ProcessStep (such as an Act). It should provide a clear entry and exit point(s) for the process.


Notes:
An implementation and/or execution of an algorithm which is associated with the design of the process.


Notes:
Concept or object denoted by the signifier associated to the sign.


Notes:
A methodology which is a component part of this Methodology


Notes:
An algorithm that defines the Methodology in a generic way.


Notes:
Process used to implement the Methodology


Notes:
The design of the expressed algorithm is implemented by a Process


Notes:
A precondition that must exist prior to the applied use of this design.


Notes:
An algorithm that defines the process used by the design in a generic way.


Notes:
External materials that describe or discuss the design


Notes:
Identifies material discussing the algorithm. The material may be in DDI or other format.


Notes:
Realization of the pattern class Process


Notes:
The Process Control Step which describes the organization of the process flow. This could be realizes as a sequence, a temporal relationship, or conditional control step. It should provide a clear entry and exit point(s) for the process.


Notes:
A realization of the pattern class Methodology


Notes:
A methodology which is a component part of this methodology. The target may be any realized Methodology. This allows the DescribedMethodology to incorporate more explicit or detailed methodologies for different forms of use without replicating the descriptive content.


Notes:
The algorithm which expresses the methodology. A restriction of the Methdology class to constrain the target to DescribedAlgorithm.


Notes:
The design used by the methodology. A restriction of the Methdology class to constrain the target to DescribedDesign.


Notes:
An external document or other source that provides descriptive information on the object.


Notes:
The process used to implement the Design. WorkflowProcess is a generic realization of the ProcessPattern.


Notes:
The algorithm that is expressed by the design. Constraint of the pattern relationship expressesAlgorithm by limiting the target to a DescribedAlgorithm.


Notes:
A description of the goal of the design. The goal may be used to evaluate the design, or implementations of the design, in terms of its ability to meet the goal.


Notes:
The description of a Precondition that must exist prior to the use of this design


Notes:
A realization of the pattern class Algorithm


Notes:
Uses the pattern of the abstract class Member


Notes:
A variable that may be used to filter the summary and/or category statistics (for example by country or by gender)


Notes:
Reference to a variable to use for weight in calculating the statistic.


Notes:
Reference to the StandardWeight value provided in Weighting.


Notes:
Reference to the variable to which the statistics apply.


Notes:
This supplies information for linking disparate records in a dataset. RecordRelations describe corresponding InstanceVariables between record types.


Notes:
Reference to the Concept that is being used


Notes:
Reference to the Unit Type that the Universe definition narrows.


Notes:
A RepresentedVariable may have more than one sets of SentinelValueDomains, one for each type of software platform on which related InstanceVariables might be instantiated. All of the SentinelValueDomains must have SentinelConceptualDomains that correspond exactly. This allows codes for missing values to be explicitly matched across platforms.


Notes:
The ConceptualVariable that can be shared by a set of multiple RepresentedVariables. Indicates comparability in  ConceptualDomain and UnitType.


Notes:
The defined class of people, entities, events, or objects to be measured.


Notes:
The substantive representation (SubstantiveValueDomain) of the variable. This is equivalent to the relationship "Measures" in GSIM although GSIM makes no distinction between substantive and sentinel values


Notes:
The geographic location related to this population. May be repeated for inclusion of multiple locations.


Notes:
Reference to a Universe that the Population narrows


Notes:
If generated directly through fielding an instrument use the instrument component containing the capture for the values that populate this InstanceVariable. A Capture is reusable and therefore it is important to know the specific use of the Capture within an Instrument. This may be any class using InstrumentComponent as an extension base, currently InstanceQuestion and InstanceMeasurement. If the content of the InstanceVariable was generated by a computation or other form of transformation with data processing, use the ComputationAction or similarly appropriate subclass of Act. If a sequence of Acts resulted in the InstanceVariable content indicate the final Act.


Notes:
The source of capture for the values that populate this InstanceVariable. This may be any class using Capture as an extension base, currently RepresentedQuestion and RepresentedMeasurement. This is the direct source of capture for the content of the data. If a transformation is required the source is not multiple captures but the transformation.


Notes:
The association to the possible sentinel (missing) values.These will be specific to one software platform.


Notes:
The ConceptualVariable that can be shared by multiple InstanceVariables. Indicates comparability ConceptualDomain and UnitType. If a relationship to a RepresentedVariable is defined there should be no relationship to a ConceptualVariable.


Notes:
The RepresentedVariable that can be shared by multiple InstanceVariables. Indicates comparability in substantive representation, Universe, and indirectly ConceptualDomain. If a relationship to a RepresentedVariable is defined there should be no relationship to a ConceptualVariable.


Notes:
Set of specific units (people, entities, objects, events), usually in a given time and geography, being measured. Can be a specialization of the Universe measured by a related RepresentedVariable.


Notes:
Identifies the ConceptualDomain containing the set of sentinel concepts used to describe the  ConceptualVariable.


Notes:
Identifies the UnitType associated with the ConceptualVariable


Notes:
Identifies the ConceptualDomain containing the set of substantive concepts used to describe the  ConceptualVariable.


Notes:
Reference to a Concept that is being used


Notes:
The set of categories containing the concepts in the domain.


Notes:
A description of the concepts in the domain. A numeric domain might use a logical expression to be machine actionable a text domain might use a regular expression to describe strings that describe the concepts.


Notes:
Class in the Collections Pattern realized by this class.


Notes:
Realization of structures in Symmetric Relation. When Concepts of a single ConceptSystem are mapped, the Concept has to appear twice as target.


Notes:
A structure containing specific relationships between members of the collection.


Notes:
A concept can play the role of a signified when there is a designation that denotes it.


Notes:
The subtype of a WorkflowStep occuring at the indexed position within the array.


Notes:
Restricts target to VocabularyEntry and cardinality.


Notes:
Restricts member target class to VocabularyEntry


Notes:
Second member in a relationship. Note that this can be realized as a collection to support tuples.


Notes:
Restricts member target class to ConceptualVariable, RepresentedVariable, and InstanceVariable


Notes:
Specialization of target to VariableMapping. Restricts cardinality. The following VariableMapping in the pair.


Notes:
Specialization of source to VariableMapping. The First Variableapping in the pair.


Notes:
Restricts member target class to ValueMapping


Notes:
The universe of the sample. Note that when the Design is implemented the Population should be a Population within this Universe.


Notes:
Restricts member target class to StatisticalClassification


Notes:
The geographic unit related to by the parent geographic unit


Notes:
first member in the relationship. Constrained to a single source


Notes:
Restricts member target class to PhysicalRecordSegment


Notes:
Restricts member target class to LogicalRecord


Notes:
A concept or concept sub-type which describes the level.


Notes:
Collections pattern class realized by this class


Notes:
Target Instance Variables if a directional relation is used


Notes:
The source Intance Variable for the relationship.


Notes:
Second member in a relationship. Note that this can be realized as a collection to support tuple


Notes:
The WorkflowStepSequence to execute if the condition is true


Notes:
Second DataStore in a relationship. Note that this can be realized as a collection to support tuples.


Notes:
Restricts member target class to DataStore


Notes:
Restricts member target class to DataPoint


Notes:
Restricts member target class to CustomValue


Notes:
Restricts member target class to CustomItem


Notes:
Restricts target object to Concept for relationshp


Notes:
Restricts source object to Concept for relationshp


Notes:
Restricts member target class to Concept or subtype of Concept


Notes:
The Collection class realized by this class


Notes:
The member containing the designation of the CodeItem


Notes:
Restricts member target class to ClassificationSeries


Notes:
The member containing the designation of the Classification Item


Notes:
Restricts member target class to ClassificationIndexEntry


Notes:
For categorical representations the CodeItem describing the value (signifier) and category (signified) may be identified.


Notes:
A Logical Record used by the BusinessProcessCondition in defining the condition.


Notes:
Parameter accepting the data as input to the process step


Notes:
The identification for the object upon which the current object is based.


Notes:
The Child agent in the hierarchical relationship


Notes:
The Parent agent in the hierarchical relationship


Notes:
Reference to an agent as described by any object that is a member of the abstract type Agent.


# t_efforttypes

Notes:
The construction phase is concerned with designing and building the components necessary to implement the system as specified.


Notes:
The elaboration phase is concerned with refining the system specification, setting up project infrastructure and agreeing on the body of work to be completed.


Notes:
The Transition phase revolves around the implementation of the project and the acceptance testing carried out by the end user


# t_genopt

Option:
_AFX_NO_DEBUG_CRT;_AFX_NO_OCC_SUPPORT;_AFX_OLD_EXCEPTIONS;_AFX_PACKING;_AFXDLL;_DEBUG;_MSC_VER;_UNICODE;AFX_CDECL;AFX_COMDAT;AFX_DATA;AFX_DATADEF;AFX_NOVTABLE;AFXAPI;APICALL;BEGIN_INTERFACE_PART ^ END_INTERFACE_PART;BEGIN_PARAM_MAP ^ END_PARAM_MAP;CONTROLLER_API;DECLARE_DYNAMIC();DECLARE_DYNCREATE();DECLARE_INTERFACE_MAP();DECLARE_MESSAGE_MAP();defined();PASCAL;SWLAPI;WINAPI;


# t_metrictypes

Notes:
Measures such as function points, SLOC, scenarios, test cases.


# t_object

Note:
Purpose:
This view is intended to provide a structure for the information needed to understand and make intelligent use of a set of data without other communication from the person or organization producing the data. It can be used to move the data into and among multiple software platforms. This information is useful for discovery of the data.

The view includes basic information about how the data were collected, but does not provide machine actionable details.

The view provides information about:
Variables and the representation of the data for each, 
Basic statistics for individual variables
Universe and population, 
Spatial, temporal, and topical coverage
The study under which the data were created
Overviews of Methodology, Design, and Process
Physical storage


Use Cases:
Basic search to find data (general search, known item search) by users looking to use data. 
--Searches by variable, coverage, creators, time frame, population, methodology and more
Machine actionable ingest to statistical software allowing users to analyze the data
--An open standard for representing the metadata needed to read the data 
Informational content to support intelligent use and understanding of the data
--The essential information for interpreting and using the data (e.g. units of measurement, relevant population)


Target Audiences:
Individual researchers, research groups, National Statistical Organizations focusing on stand-alone codebooks, students, instructors, archives, and libraries. Software tool makers.

Restricted Classes:
DesignOverview references Precondition, Goal, and WorkflowProcess
InstanceVariable references RepresentedVariable, and ConceptualVariable, and the abstract class Act(InstrumentComponent, ComputationAction, StudyControl, and MetadataDrivenAction)
Methodology references Methodology
ProcessOverview references ProcessSequence
RepresentedMeasurement references ExternalAid
RepresentedQuestion references ExternalAid
SamplingProcedure references SamplingDesign, SamplingAlgorithm, and SamplingProcess
SentinelConceptualDomain references ConceptualSystem
SpatialCoverage references GeographicUnitClassification, and GeographicUnitTypeClassification
Study references AuthorizationSource
SubstantativeConceptualDomain references ConceptualSystem


Note:
Purpose:
The Sampling View covers the methodology and process for drawing a sample from a designated sample frame. It provides the ability to describe sample designs from simple single stage samples to those with multiple stages and ones with more than one frame (necessitating drawing subsets of the sample from each frame). Probability sampling, including model-based, and non-probability sampling can each be described. The descriptive information of the methodologies used, design of the sample, algorithms to support the drawing of the sample, goals, sample frames used, and guidance on the use of the resulting sample (for defining weights, limitations, etc.) are supported. This includes the use of the Workflows which can define the process of creating simple or complex samples on a step-by-step basis. Can be used as metadata to drive sample selection.

Use Cases:
Defining Sample Frames for prospective use
Describing the process of simple or complex sampling procedures to inform the automated creation of a sample from a sample frame
Describe a sample to provide the information necessary to create sampling weights and estimation formulae.
Describe the processing of sampling for the purpose of informing the user of limitations or strengths of a particular sampling procedure and to provide guidance on the use of the procedure or the result of the procedure.

Target Audiences:
Organizations defining sample frames and sampling procedures for execution.
Users requiring information on the sampling process and its limitations.

Restricted Classes:
Parameter: valueRepresentation: ValueDomain: some subtypes not supported: SentinelValueDomain.

Precondition: basedOnPriorResult: Result: some subtypes not supported: SegmentDefintionResult, QualitativeCodingResult.

SamplingDesign: expressesAlgorithm: AlgorithmOverview: some subtypes not supported: SegmentDefinitionAlgorithm, QualitativeCodingAlgorithm, BusinessAlgorithm.

SamplingDesign: implementedBy: WorkflowProcess: all subtypes not supported.

SamplingProcedure: hasDesign: DesignOverview: some subtypes not supported: SegmentDefinitionDesign, QualitativeCodingDesign.

SamplingProcedure: isExpressedBy: AlgorithmOverview: some subtypes not supported: SegmentDefinitionAlgorithm, QualitativeCodingAlgorithm, BusinessAlgorithm.

SamplingProcedure: componentMethodology: MethodologyOverview: some subtypes not supported: SegmentDefinitionMethod, QualitativeCodingMethod.

Split: executeConcurrently: WorkflowStep: some subtypes not supported: Act, ConcurrentControlConstruct, SplitJoin.

SplitJoin: executeConcurrently: WorkflowStep: some subtypes not supported: Act, ConcurrentControlConstruct, Split.

Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.
Concept is extended by ConceptualVariable, RepresentedVariable and InstanceVariable.
ExternalMaterial is extended by ExternalAid.
WorkflowStepSequence is extended by StructuredWorkflowSteps.

General documentation:
In socio-economic statistics, samples are used to conduct surveys within time, accuracy, and expense constraints. When it comes time to conduct a survey, the sample is selected from a larger set, called the frame or sampling frame. Frames are an enumeration of the population the survey is designed to estimate, but they don’t contain the variables a survey or experiment might collect. The sample is a subset of the frame, and it is designed (in theory) to be representative of the population as a whole. In practice, for any selected sample, this might not be the case.

Samples can be based on probability or not. For a probability based sample, each element in the frame is assigned a probability it is selected for a sample. Non-probability samples do not have this feature, and the elements are selected in some other manner. The representativeness of a probability based sample is measured as sampling error, a statistical measure. Every probability sample has a sampling error associated with it. It is an indicator of how accurate estimates are to the theoretical population values.

Several methods can be used to select a sample. In the simple case, elements are selected from the frame in one step. In the probability based case, typical techniques are simple random sampling (with or without replacement), systematic random sampling, sampling proportional to size, and simple stratified random sampling. For non-probability samples, techniques include convenience, purposive, quota, self-selected, and snowball sampling.

Sampling in scientific experiments is different than for statistical surveys usually. Non-probability sampling is often used. Self-selected samples (for instance people who volunteer for a drug trial) are often seen. 

To help reduce sampling errors, improve estimates, reduce costs, and reduce the time to complete a survey, sampling is sometimes broken into parts. The first main way this is done is through the use of strata. Strata are subsets of a population with independent estimates. For example, the mean height of women is different than the mean height of men. Sampling based on stratification reduces sampling error.

The other main way samples are partitioned is through clusters. Clusters are subsets based on some convenience criteria. For example, to make sure interviews can be conducted in a short amount of time for a country-wide survey, selected sample units might need to be geographically close, or clustered. This will greatly reduce the time and cost for collecting data, but it has the reverse effect of increasing the sampling error. Representativeness is affected if only some geographical areas are used to select the sample.

Sometimes, so many clusters are identified that they are sampled themselves. Then within those selected, the units for collection are selected. This is a 2-stage sample, and it should not be hard to imagine more than 2 steps to reduce clusters to a manageable size before the ultimate sampling units are selected. Some statistical surveys in the US have 4 stages or more.

It is possible that for some survey, more than one frame is needed. For instance, in random dialing telephone surveys, a bank of valid telephone numbers is the frame, and some are selected for contact. However, the bank of valid telephone numbers might come from the telephone company, and they are all land-lines. To get full coverage of the population, one must also select from a bank of cellphone numbers. Thus, 2 frames are needed, 2 samples are selected for full coverage (representativeness) to be achieved.


Note:
Purpose:
The Statistical Classification View brings together the structures need to record, organize, manage, and index Statistical Classifications. These classifications are often developed cooperatively and managed over time. They may be organized into series and families of classifications and use specified vocabularies. Mapping may be provided to express relationships between two or more Statistical Classifications in order to clarify change over time or the similarities and differences between Statistical Classifications in the same family (i.e. Industry, Occupation, Education).

Use Cases:
Industry: US-SIC, NAICS, GICS, ISIC; Occupational: ISCO, US-SOC; Geographic: US-FIPS, NUTS

Target Audience:
Organizations maintaining and managing shared Statistical Classifications.

Included Classes: 
AuthorizationSource, Category, ClassificationFamily, ClassificationIndex, ClassificationIndexEntry, ClassificationItem, ClassificationSeries, Code, Concept, ConceptParentChild, ConceptParentChildPair, ConceptPartWhole, ConceptPartWholePair, ConceptSystem, CorrespondenceTable, ExternalMaterial, Individual, Level, Map, Organization, StatisticalClassification, Vocabulary.

General Documentation:
The abstract class Designation serves as a relationship target for the following classes: ClassificationItem and Vocabulary. The only included class belonging to this abstract group is Code.
The abstract class Node serves as a relationship target for the following classes: Map and Level. The only included class belonging to this abstract group is ClassificationItem.
The abstract class NodeSet serves as a relationship target for the following class: CorrespondenceTable. The only included class belonging to this abstract group is StatisticalClassification.
The abstract class Agent serves as a relationship target for the following classes: CorrespondenceTable and AuthorizationSource. The only included classes belonging to this abstract group are Organization and Individual.
The abstract pattern class OrderedPair serves as a relationship target for the following class: Map. The only included class realizing this pattern is ConceptParentChildPair


Note:
Purpose:
The purpose of Geographic Classification in DDI is to express relationships over time and space that are currently only available in geographic shape files or by exploring the data file itself. A great deal of legacy data does not have related geographic files. A large group of areas covered by DDI do not have clearly defined geography in terms of spatial extent, but have considerable relational information. Many geographic structures define geographic unit types with descriptive sub-sets (e.g. “Places of over 10,000 population” where the user must know whether a specific location meets that definition prior to determining if it is included in the data set).

Use Cases:
Describing geographic structures and their hierarchies
Describing geographic units and their corresponding locations (polygons, bounding boxes, points etc.)
Documenting changes to geographic units over time

Target Audiences:
Digital archivists
Search engines intent on exposing data by their geographical coverage
Researchers who need to describe complex geographical structures
Researchers who need to describe geographical structures and locations with changes over time

Restricted Classes:
ConceptSystem is extended by CategorySet
Concept is extended by Category, ConceptualVariable, RepresentedVariable, InstanceVariable, Population and Universe.
ExternalMaterial is extended by ExternalAid.

General Documentation:
Geographic classification uses unit, unit type, and collections to provide the basis for describing the geographic structure (unit types) and their individual locations (units) in a manner that supports complex layered hierarchies, changes in name, role, and geographic extent over time, and coding for direct use in value domains and responses. It supports the content of DDI Lifecycle Geographic Structure and Geographic Location.
The revision of the DDI 3.2 structure into the DDI4 structure addresses the following constraints in DDI 3.2:
·        Codes and names can be used directly wherever a code list can be used (both Geographic Unit Type Classification and Geographic Unit Classification are sub-types of Code List
·        A Geographic Unit (location) can belong to multiple Geographic Unit Type (geographic levels) with replicating its content
·        A Geographic Unit can version and/or define new units whenever there is a change in name or spatial extent as determined by the user. For example a Metropolitan Area may change only its spatial extent over time and be managed as versions of the same conceptual location; a city may annex additional land, or be renamed. Normally a new version of a Geographic Unit should have some common spatial extent with the old version. This can be described in the Geographic Unit precedes or supersedes using the Spatial Relationship using Spatial Relation Specification (Equals  Disjoint  Intersects  Contains  Touches).
·        Geographic Units can be used to describe points, lines, and/or polygons as well as include centroid information.


Equivalent Content between DDI 3.2 and DDI 4
DDI 3.2 - DDI 4 - Comment

Geographic Structure - Geographic Unit Type Classification - no comment

Geographic Level - Unit Type - Because no specialized information was being gathered a generic Unit Type is used. This allows users to declare any Unit Type as part of geography without requiring that it be of a specific type.

Parent Structure / Geographic Layer Base - Geographic Unit Type Relation Structure - Described as separate hierarchies; can have levels; Spatial relationships can be described

Geographic Level Code - Geographic Unit Type Instance - Codes are assigned when the Unit Type is used by a Geographic Unit Type Classification (see information on contains in Geographic Location)
Primary Component - Geographic Unit Type Relation Structure - Spatial relationships can be described

Geographic Location - Geographic Unit Classification - Inclusion of a Geographic Unit using “contains” allows for the assignment of a code in the same manner as in a code list. Different code sets should be expressed as different geographic unit classifications. Inclusion is by reference so that the described Geographic Unit can be assigned multiple codes without altering the Geographic Unit description

Location Value - Geographic Unit - Rather than grouping with other units of the same unit type, each unit can relate itself to one or more unit types. This allows for a location like Washington, D.C. to act as a State equivalent, County equivalent, and Place in the United States. Provides supersedes and precedes.


Note:
Purpose:
DDI4 data management description aims to account for the ingestion and production of new data types (registry data, health data, big data, spell data, event data, etc.) and both legacy and new data management services that give shape to these data types in the course of the data lifecycle.  The Data Management View describes the prospective and retrospective use of multiple data management platforms and architectures including (1) ESB (Enterprise Service Bus) and SOA (Service Oriented Architecture); (2) the use of PROCs/Commands in statistical packages like SAS, Stata and R; and now (3) the use of iPaaS (integration Platform as a Service) in public clouds, private clouds and apparatuses as practiced by various ETL (Extract, Transform and Load) platforms.

Use Cases:
Create repeatable processes across a data network. More specifically, document and share the specifications for a demographic and epidemiological surveillance DataPipeline across surveillance sites
Produce a Data Management Plan (DMP) in the form of a DataPipeline so other researchers are able to replicate a study’s results
Document the actual data management in a study as a DataPipeline. This could underpin workflow tools for researchers
Use a DataPipeline description as the input to tools that trace the lineage of data during the data lifecycle of a Study 
Use a DataPipeline description and the GraphML it spawns to create workflow diagrams
Specialize the GLBPM to support the production of a dataset of geotagged tweets from the US where a wave corresponds to a day. Create a DataPipeline that describes in detail how this dataset is produced.
Programmatically create a Data Management View for an Extract, Transform and Load (ETL) platform using the ETL’s authoring environment and the instructions that authors create as input

Target Audiences:
Researchers who are preparing a Data Management Plan (DMP)
Data networks migrating from an Enterprise Service Bus (ESB) / Service Oriented Architecture (SOA) platform to a virtual (cloud-based) or actual integrated Platform as a Service (iPaaS) appliance (e.g. ETLs)
Industry-specific or generic standard groups who wish to integrate fully developed information models with domain-specific business process models
Search engines intent on exposing data lineage within a study

General Documentation:
At one level the Data Management View consists of a data pipeline that traverses a series of business activities from business process models like the GSBPM (Generic Statistical Business Process Model) for the production of statistics and the GLBPM (Generic Longitudinal Business Process Model) for the description of longitudinal studies. At another level the Data Management View decomposes these business processes into a series of workflow steps. At both levels components exchange data.

DataPipeline-
With the Data Management View, the user is able to construct a DataPipeline of BusinessProcesses where each BusinessProcess contains either a simple collection or a structured collection of WorkflowSteps. 
The DataPipeline itself is a simple collection of BusinessProcesses with the next one beginning after the preceding one ends.  
Use the Data Management View and its DataPipeline to traverse a business process model once to describe the data lifecycle of a Study and many times to describe the data lifecycle of a StudySeries.

BusinessProcess-
A BusinessProcess has an AlgorithmOverview, zero or more Preconditions, zero or more Postconditions and one or more StandardModelUsed. 
Note that Preconditions and Postconditions are LogicalRecords. One BusinessProcess creates/updates LogicalRecords as Postconditions. These Postconditions may become the Preconditions of the next BusinessProcess.

Figure 1: The DataPipeline

Note that support for business process models here is not limited to either the GSBPM or the GLBPM that the GSBPM has spawned.

The Generic Statistical Business Process Model (GSBPM) circumscribes a set of business processes that together describe a data lifecycle for building a single wave of national statistics. The Generic Longitudinal Business Process Model (GLBPM) specializes the GSBPM for longitudinal studies. Here each traversal of the GLBPM corresponds to the data lifecycle of a Study in a StudySeries.
Other business process models are more or less based on the GLBPM and the GSBPM. For example, a widely used demographic and epidemiological surveillance business process model specializes the GLBPM data lifecycle to create events, event histories and spells.

Figure 2: Support for Specialization of the GSBPM/GLBPM in DDI4 BusinessProcesses

WorkflowSteps-
The BusinessProcess decomposes into a WorkflowStepSequence.  Alternatively, the BusinessProcess AlgorithmOverview can be used to outline a WorkflowStepSequence. This would be appropriate in situations where only a higher-level description was needed.

Figure 3: Example AlgorithmOverview

The WorkflowStepSequence may be either a Simple Collection or a Structured Collection of WorkflowSteps. In a simple collection of WorkflowSteps, successive pairs in the sequence participate in a before/after relationship. In a structured collection, however, relationships among the WorkflowSteps can be complicated: a sequence may have multiple starting points and multiple end points. Here before and after relationships can be indeterminate, depending on a platform and its technology stack.
The structured collection of WorkflowSteps is called a WorkflowStepRelationStructure. Like other structured collections in DDI4, a WorkflowStepRelationStructure is specified in a graph form as an unordered list of adjacency lists where for each vertex we specify an array of adjacent vertices:

Figure 4: The DDI4 RelationStructure

Here each vertex and the array of its adjacencies are WorkflowSteps.

Figure 5: An Example WorkflowRelationStructure (fragment)

The Structured Collection in DDI4 is the successor to GSIM’s Node Set. Using graph representation, DDI4 RelationStructures, like the WorkflowStepRelationStructure, are easy to visualize and annotate using open source tools:

Figure 6: Graph Rendering of Example DDI4 WorkflowRelationStructure


Note:
Purpose
Use the DataDescriptionView to describe a collection of LogicalRecords by themselves or along with their PhysicalRecordSegments in a Study and/or a StudySeries.

Recall that a LogicalRecord is a record definition and a PhysicalRecordSegment describes the physical storage arrangement of a LogicalRecord.

Think of the collection of LogicalRecords and their PhysicalRecordSegment counterparts in a Study as a succession of states that are the products of one or more data transforming processes. In the DataDescriptionView we just describe products in this succession, not the processes through which these products are created.

In this succession operational data may be transformed into analysis-ready data and then analytical data in a series of steps. The DataDescriptionView captures the products from one, some or all of these interim steps. 

Products can include “skinny” and “fat” data structures; relational datastores; star schemas (data warehouses); structured collections of instance variables that take the form of objects, not tables; data cubes (not supported in the prototype) and so forth.

Instead of using the DataDescriptionView, use the DataManagementView for creating data descriptions that are both process-centered and product-centered. 


Use Cases
Construct a catalog of data records produced across the life of a study. Order the records by category: initial or submission records, interim or archival records, analysis or dissemination records
Expose variables in LogicalRecords and their PhysicalRecordSegments so they are searchable by: 
study, 
structural role(s) (identifier, measure and attribute) in one or more viewpoints and 
their functional role(s) as specified in one or more external controlled vocabularies
Specify the information needed for a Submission Information Package (SIP), an Archival Information Package (AIP) or a Dissemination Information Package (DIP) when the data is a CSV file
Support the description of a CSV file that uses a list datatype to, for example, report health measures that consist of compound elements like blood pressure
Support the description of medical information as specified both by Fast Healthcare Interoperability Resources (FHIR) and the Clinical Information Modeling openEHR Initiative (CIMI). With respect to FHIR, support, for example, the Observation and DiagnosticReport resources. With respect to CIMI, support, for example, the various observation archetypes including the newborn Apgar score, blood pressure, body mass index, physical examination findings, etc.
Support the description of a NoSQL key/value store where the key is either a simple collection of one or more identifiers or a structured (hierarchical) collection and the value can be text, video, sound or a JSON document

Target Audiences
Digital archivists
Search engines intent on exposing data lineage within a study
Researchers who are preparing a Data Management Plan (DMP)
Governments intent on exposing in a single datastore registries that include demographic data and health information in order to promote various types of research

Restricted Classes
Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.
Concept is extended by ConceptualVariable, RepresentedVariable, UnitType and Universe.
ExternalMaterial is extended by ExternalAid.


Note:
Purpose:
To review the conceptual concept structures and to manage concept systems (other than statistical classifications). The coverage go down to a RepresentedVariable. InstanceVariable has been included in the collection for use as a member of a VariableCollection. However it does not go into the detailed content of an InstanceVariable.

Restriction: 
InstanceVariable has been included for the sole purpose of membership in a VariableCollection. The classes required to completely describe an InstanceVariable have not been included.


Note:
Purpose:
The ControlledVocabulary view is intended to allow for the structured description of a vocabulary in DDI4. A vocabulary can be described as a simple set of terms and definitions, or a set of terms and definitions with a structure such as a hierarchy.

Use Cases:
A DDI4 ExternalControlledVocabularyEntry could reference a vocabulary entry described in DDI4. This would allow processing by software able to interpret DDI4. 
DDI4 has a set of controlled vocabularies https://www.ddialliance.org/controlled-vocabularies, currently described in Genericode. These could be published in DDI4 as well.
Vocabularies having a structure more complex than a simple table.

Target Audiences:
DDI4 user communities.

Restricted Classes:
Concept is extended by Category, ConceptualVariable, RepresentedVariable, InstanceVariable, Population, UnitType and Universe
ExternalMaterial is extended by ExternalAid

General Documentation:
The representation of a controlled vocabulary in DDI4 consists of four classes:
ControlledVocabulary – The structured collection of vocabulary entries
VocabularyEntry – Assigns a definition to a term
VocabularyRelationStructure – Allows for the description of a complex structure among the terms, such as a hierarchy
ExternalMaterial – Points to material outside of a current DDI4 instance.

The ControlledVocabulary uses a set of  VocabularyEntryIndicators to delineate the entries in the vocabulary. These may be ordered with an index.
The VocabularyRelationStructure uses a set of VocabularyEntryRelations to describe relationships among the vocabulary entries. A "source" entry might have a relationship to several "target" entries, for example one entry (e.g. Vehicle) might be a more general term for several other terms (e.g. car, bike, skateboard). This relationship may be described with a semantic, a relationSpecification (e.g. GeneralSpecific), and whether the relation is total or not. 
The diagram below shows all inherited properties for the vocabulary classes.
[image to be inserted here]


Note:
Purpose:
The DDI4 CustomMetadataView allows for the definition of a set of keys and their interrelationships. This structure can be shared and reused by a community. These keys can be used in key-value pairs to enter metadata that is more actionable than would be if an uncontrolled set of keys were employed. They could also be used in a NoSQL key/value store.

Use Cases:
User defined structures for notes. This corresponds to the UserAttributePair in DDI3.2, but allows for additional specification of a structure for the keys and a datatype and cardinalities for the values.
User defined structures for specifying the location of parts of qualitative objects. The example below shows the location of words or sentences from material arranged into volume, chapter, sentence and word
User defined structures for specifying the location of  parts of cited materials

Target Audiences:
Users of DDI4 needing structured extensions to be shared by their community. A user community, for example, could share the structure for locating material by volume, chapter, sentence and word.

Restricted Classes:
The list below displays each class in the View that is extended by classes not in the view.
Concept is extended by ConceptualVariable and Population.
ExternalMaterial is extended by ExternalAid.
Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.

General Documentation:
The keys and their interrelationships are defined in a CustomStructure which is a collection of CustomItems. Each CustomItem defines a key, giving it a cardinality and associating it with a RepresentedVariable and a ValueDomain. The set of CustomItems can be arranged into a structure, for example a hierarchy, by a CustomItemRelationStructure.
[image to be inserted]
Once the structure is defined, it can be used in a CustomInstance. This is a collection of CustomValues. A CustomValue contains a key-value pair where the key corresponds to a previously defined CustomItem. A CustomValue also may be associated with an InstanceVariable.  The CustomValues may also be structured by a CustomValueRelationStructure.
[image to be inserted]


Note:
Purpose:
The purpose of the DDI4 Data Capture Instrument View is to describe the processes of developing- and collect data from a questionnaire instrument, as well as to describe the capture or acquiring of measurements from various sources, like databases, registries, administrative data, bio-medical devices, environmental sensors, or any other source or instrument. The focus on measurement is new in DDI4 compared to earlier versions of the standard.

Use Cases:
Document  the development process for a conceptual questionnaire of an international survey
Design an implemented questionnaire in a specific mode and for a specific population
View how a measurement has been captured or how a survey question has been asked
Reuse of instrument components developed for a different study
Export instrument related metadata between applications
Design a measurement
Describe a measurement  instrument 

Target Audiences:
Developers of conceptual instruments, for example for an international survey
Designers of implemented instruments for surveys and measurements
Designers and developers of data capture tools
Researchers wishing to understand how a measurement has been captured or how a survey question was asked or how it was developed
DDI4 users in general

Restricted Classes:
WorkflowStepSequence is extended by StructuredWorkflowSteps.
RepresentedVariable is extended by InstanceVariable.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.
ConceptualVariable is extended by InstanceVariable
Concept is extended by InstanceVariable, Population and UnitType;
ExternalMaterial is extended by ExternalAid.
Code is extended by ClassificationItem.

General Documentation:
Questionnaire development – a brief overview

The goal of questionnaire design is to develop an ImplementedInstrument from which data can be captured when put in field. 

The first step in a questionnaire design process is often to select or define the topics and the Concepts to be measured by the questions in the instrument. 
The concepts are then operationalized into RepresentedQuestions that contains the more reusable components of a question that can be reused among different surveys, studies and modes of collection.
InstanceQuestions realize the represented questions in an instrument. It connects to other InstrumentComponents like for example a showcard or other ExternalAid and Instructions, and links the question to the flow logic of the questionnaire. 
The ConceptualInstrument represents the instrument independent of mode. It organizes the instrument by connecting the instrument components to WorkflowStepSequence that realizes the flow of a questionnaire sequence, including conditions IfThenElse, Loop etc.. 
The ImplementedInstrument has a specific mode and is designed or adapted for a specific sample or population. Two different implemented instruments may use the same conceptual instrument. 

Measurement 

Measurements are non-question based data captures like for example blood pressure measurements, MRI images, thermometer, web-service, and experimental observations.
Measurements often involve the use of specific machines or protocols to ensure consistency and comparability of the measure. The RepresentedMeasurement is a description of the components of a measurement, that can be reused by multiple or repeated studies.
The ImplementedMeasurement initiates the represented measurement so that it can be used in the data capture process. Other InstrumentComponents like Instructions and ExternalAids associated with the measurement can be linked to the implemented instrument.
The ConceptualInstrument represents the reusable components of the instrument that can have different concrete implementations. It connects to the WorkflowStepSequence that realizes the instrument flow. A WorkflowStep can be linked to a WorkflowService that involves agents and services involved in the process step.
The ImplementedInstrument is a specific implementation of a conceptual instrument.


Note:
Purpose:
The Agent Registry View supports the creation of a listing of Agents (Organization, Individual, Machine) for the purpose of maintenance and reuse. The listing of Agents can be organized as simple lists or in more complicated structures through the use of an AgentRelationStructure. These may be typed and provided with effective date ranges either for the whole AgentRelationStructure or for individual AgentRelations. 
Complex relationships may be described among Individuals or among Organizations or among Machines. Relationships between members of these classes may also be described.


Use Cases:
Maintaining a listing of all Organizations and Individuals related to a project or statistical activities, i.e. Individuals and Organizations related to the IPUMS projects at the Minnesota Population Center or the Departments and Individuals involved in the production of the Australian Census within the Australian Bureau of Statistics.
Organizational affiliations of Individuals. 
Collaboration networks or other social networks.


Target Audience:
Organizations working with a number of Individuals and Organizations whose descriptive information and interrelationships change over time.

Included Classes: Agent Listing, Agent Relation Structure, Organization, Individual, Machine, and External Material. 

Restricted Classes:
Concept is extended by Category, ConceptualVariable, RepresentedVariable, InstanceVariable, Population, UnitType and Universe
ExternalMaterial is extended by ExternalAid


General Documentation:
The primary class is the Agent List which can be structured by AgentRelationStructure. Agents may be of any type supported by DDI at the time of this release. Agent relationships can be defined using the adjacency list Agent Relation within AgentRelationStructure. specifying the RelationshipSpecification (Equality, Parent/Child, Whole/Part, etc.), a relevant semantic such as a specific role or relationship type, and effective time span for the relationship.


Note:
Definition
============
A set of access information for a Machine including URI, mime type, and physical location

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Location address identifying each part of the address as separate elements, identifying the type of address, the level of privacy associated with the release of the address, and a flag to identify the preferred address for contact.

Examples
==========
For example:
1.  OFFICE, ABS HOUSE, 45 Benjamin Way, Belconnen, Canberra, ACT, 2617, AU
2.  OFFICE, Institute of Education, 20 Bedford Way, London, WC1H 0AL, UK

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:AddressType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A basic structure for declaring the name of an Agent inline, reference to an Agent, and role specification. This object is used primarily within Annotation.


Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ContributorType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Persistent identifier for a researcher using a system like ORCID

Examples
==========
ORCID

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type Agent

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Used to define the relation agents in a hierarchical structure

Examples
==========
An Organization (source/parent) employing and Individual (target/child); An Individual (source/parent) supervisory to an Individual (target/child); An Organization (source/parent) overseeing a project (Organization) (target/child). Select appropriate relationship using the controlled vocabulary available through hasRelationshipSpecification. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides annotation information on the object to support citation and crediting of the creator(s) of the object.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CitationType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A generic date type for use in Annotation which provides the standard date structure plus a property to define the date type (Publication date,  Accepted date, Copyrighted date, Submitted date, etc.). 

Examples
==========


Explanatory notes
===================


Synonyms
==========
Equivalent of http://purl.org/dc/elements/1.1/date where the type of date may identify the Dublin Core refinement term.

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Use to specify the area of land, water, total or other area coverage in terms of square miles/kilometers or other measure as part of a Geographic Extent.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:AreaCoverageType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the type and length of the audio segment.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:AudioType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Use when creating an object that is based on an existing object or objects that are managed by a different agency or when the new object is NOT simply a version change but you wish to maintain a reference to the object that served as a basis for the new object. BasedOnObject may contain references to any number of objects which serve as a basis for this object, a BasedOnRationaleDescription of how the content of the referenced object was incorporated or altered, and a BasedOnRationaleCode to allow for specific typing of the BasedOnReference according to an external controlled vocabulary.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:BasedOnObjectType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Personal names should be listed surname or family name first, followed by forename or given name. When in doubt, give the name as it appears, and do not invert. In the case of organizations where there is clearly a hierarchy present, list the parts of the hierarchy from largest to smallest, separated by full stops and a space. If it is not clear whether there is a hierarchy present, or unclear which is the larger or smaller portion of the body, give the name as it appears in the item. The name may be provided in one or more languages.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:BibliographicNameType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Binds two parameters together to direct flow of data through a process

Examples
==========
From the output of an InstanceQuestion to the input of a ComputationAction

Explanatory notes
===================
Binding is used to define the flow of data into, out of, and within a process. It is separate from the flow of a process. When used in the workflow of a data capture process most data may go from a capture to an instance variable, but when needed as a check sum in a loop, a recoding process, or conditional content for DynamicText, Binding provides the means for explicitly directing the movement of data from one point to another in the process.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A BusinessProcess precondition or post condition which describes the condition which must be met to begin (pre) or exit (post) a process. It may use a specified LogicalRecord. The Logical Record has SQL that describes it, rejectionCriteria against which its adequacy may be tested and an optional annotation that describes its provenance.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for the identification of the BusinessProcess specifically as a member and optionally provides an index for the member within an ordered array. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use when the member type is restricted to Category.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Source target relationship between categories in a classification relation structure


Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Statistics related to a specific category of an InstanceVariable within a data set.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
pi:CategoryStatisticType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specification of the character offset for the beginning and end of the segment, or beginning and length.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CharacterParameterType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type ClassificationIndexEntry

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A ClassificationItemIndicator realizes and extends a MemberIndicator which provides a Classification Item with an index indicating order and a level reference providing the level location of the Classification Item within a hierarchical structure.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Source target relationship between classification items in a classification item relation structure

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type ClassificationSeries

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the Classification Series in a complex relation and specifies the relationshi

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A CodeIndicator realizes and extends a MemberIndicator which provides a Code with an index indicating order and a level reference providing the level location of the Code within a hierarchical structure.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Source target relationship between codes in a code relation structure

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides the following information on the command. The content of the command and the programming language used.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CommandType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Contains information on the command used for processing data. Contains a description of the command which should clarify for the user the purpose and process of the command, an in-line provision of the command itself, and a reference to an external version of the command such as a coding script. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CommandCodeType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Identifies and provides a link to an external copy of the command, for example, a SAS Command Code script. Designates the programming language of the command file, a description of the location of the file , and a URN or URL for the command file.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CommandFileType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type Concept and all subtypes of Concept: Category, Universe, Population, Unit Type

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specifies the relationship between concepts in a collection of concepts. Use controlled vocabulary provided in hasRelationSpecification to identify the type of relationship (e.g. ParentChild, WholePart, etc.)

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Text which has a changeable value depending on a stated condition, response to earlier questions, or as input from a set of metrics (pre-supplied data). The command code indicates the condition and/or calculation used to determine the content of the text.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:ConditionalTextType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Contact information for the individual or organization including location specification, address, web site, phone numbers, and other means of communication access. Address, location, telephone, and other means of communication can be repeated to express multiple means of a single type or change over time. Each major piece of contact information contains the element EffectiveDates in order to date stamp the period for which the information is valid.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:ContactInformationType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Identifies the difference between the date applied to the data as a whole and this specific item such as previous year's income or residence 5 years ago. A value of true for the attribute isNegativeOffset indicates that the offset is the specified number of declared units prior to the date of the data as a whole and false indicates information regarding a future state.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ContentDateOffsetType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the commonalities and differences between two members using a textual description of both commonalities and differences plus an optional coding of the type of commonality.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
cm:CorrespondenceType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type CustomItem

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines a relationship between CustomItems .

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type CustomValue

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type DataPoint

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Data Point relations used by the Data Point Relation Structure of a Logical Record to describe specific source target Data Points and their relationship

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type DataStore

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the complex relationship between 2 or more DataStores in a DataLibrary

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.

Examples
==========


Explanatory notes
===================
Date allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999.

Synonyms
==========


DDI 3.2 mapping
=================
r:DateType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Expresses a date/time range using a start date and end date (both with the structure of Date and supporting the use of ISO and non-ISO date structures). Use in all locations where a range of dates is required, i.e. validFor, embargoPeriod, collectionPeriod, etc.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:DateType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes a bounding value for a number range expressed as an xs:double.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:DoubleNumberRangeValueType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Structure supporting the use of dynamic text, where portions of the textual content change depending on external information (pre-loaded data, response to an earlier query, environmental situations, etc.). 

Examples
==========
Purpose: Provide customized number of hours within a question text
Input is the OutputParameter from Question "What time did you take this medication?"
Literal Text: "During the past " [0]
Conditional Text / Command: PastTime=Input; Round PastTime to nearest hour; Round CurrentTime to nearest hour; CurrentTime - PastTime = HOURS; content=HOURS [1]
Literal Text: " hours which of the following symptoms have you experienced?" [2]

Result in question text for a PastTime= 06:10; CurrentTime=14:54
"During the past 9 hours which of the following symptoms have you experienced?"

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:DynamicTextType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Abstract type existing as the head of a substitution group. May be replaced by any valid member of the substitution group TextContent. Provides the common property of purpose to all members using TextContent as an extension base. Provides a Purpose for the content and ordering information within the Dynamic Text. May be a LiteralText or ConditionalText.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:TextContentType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Any non-email means of relaying a message electronically. This would include text messaging, Skype, Twitter, ICQ, or other emerging means of electronic message conveyance. 

Examples
==========
Skype account, etc.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:InstantMessagingType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An additional condition and resulting step to take if the condition in the parent IfThenElse is false. It cannot exist without a parent IfThenElse.



Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An e-mail address which conforms to the internet format (RFC 822) including its type and time period for which it is valid.

Examples
==========
info@ddialliance.org; ex.ample@somewhere.org

Explanatory notes
===================


Synonyms
==========
e-mail address; internet email address

DDI 3.2 mapping
=================
r:EmailType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for unstructured content which may be an entry from an externally maintained controlled vocabulary.If the content is from a controlled vocabulary provide the code value of the entry, as well as a reference to the controlled vocabulary from which the value is taken. Provide as many of the identifying attributes as needed to adequately identify the controlled vocabulary. Note that DDI has published a number of controlled vocabularies applicable to several locations using the ExternalControlledVocabularyEntry structure. If the code portion of the controlled vocabulary entry is language specific (i.e. a list of keywords or subject headings) use language to specify that language. In most cases the code portion of an entry is not language specific although the description and usage may be managed in one or more languages. Use of shared controlled vocabularies helps support interoperability and machine actionability.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:CodeValueType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The static portion of the text expressed as a StructuredString with the ability to preserve whitespace if critical to the understanding of the content.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:TextType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A link to a form used by the metadata containing the form number, a statement regarding the contents of the form, a statement as to the mandatory nature of the form and a privacy level designation.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:FormType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides ability to declare an optional sequence or index order to a Geographic Unit

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes structured relationship between Geographic Units.

Examples
==========


Explanatory notes
===================
A member might have a ParentChild relation to several other members which is Anti-Reflexive, Anti-Symmetric, and Anti-Transitive. For a process this might have a semantic of "immediately follows". 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides ability to declare an optional sequence or index order to a Unit Type describing a Geographic Unit Type. Extended to support membership in a specific level.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes structured relationship between Unit Types used to define Geographic Unit Types. Extended to include the ability to define a Spatial Relationship using a controlled vocabulary.

Examples
==========


Explanatory notes
===================
A member might have a ParentChild relation to several other members which is Anti-Reflexive, Anti-Symmetric, and Anti-Transitive. For a process this might have a semantic of "immediately follows". 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A reference to an image, with a description of its properties and type.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ImageType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the shape and area of an image used as part of a location representation. The shape is defined as a Rectangle, Circle, or Polygon and content provides the information required to define it in the form of a comma-delimited list of x,y coordinates, listed as a set of adjacent points for rectangles and polygons, and as a center-point and a radius for circles (x,y,r).

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ImageAreaType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Relationship between Index Entries defined by RelationSpecification.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The name of an individual broken out into its component parts of prefix, first/given name, middle name, last/family/surname, and suffix. The preferred compilation of the name parts may also be provided. The legal or formal name of the individual should have the isFormal attribute set to true. The preferred name should be noted with the isPreferred attribute. The attribute sex provides information to assist in the appropriate use of pronouns.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:IndividualNameType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for the identification of the InstanceVariable specifically as a member and optionally provides an index for the member within an ordered array. 

Examples
==========


Explanatory notes
===================
Note if multiple types of Variables may be included in a collection use VariableIndicator.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the relationship between 2 or more InstanceVariables.

Examples
==========


Explanatory notes
===================
Use when relationships are limited to InstanceVariables only. Use VariableRelation when mixing relationships between various levels in the Variable Cascade. Use ConceptRelation when any subtype of Concept may be part of the relationship.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A key value relationship for two or more logical records where the key is one or more equivalent instance variables and the value is a defined relationship or a relationship to a set value. Correspondence type refers to the variables themselves rather than the value of the variables concerned. In this context Correspondence type will normally be set to ExactMatch.

Examples
==========


Explanatory notes
===================
Logical Records: Household and Person, Key: Household ID (HHID in Household Record, HHIDP in Person Record), ValueRelaitonship: Equal, Set Value: n.a.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An identifier whose scope of uniqueness is broader than the local archive. Common forms of an international identifier are ISBN, ISSN, DOI or similar designator. Provides both the value of the identifier and the agency who manages it.

Examples
==========


Explanatory notes
===================
For use in Annotation or other citation format. 

Synonyms
==========


DDI 3.2 mapping
=================
r:InternationalIdentifierType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Packaging structure for multiple language versions of the same string content. Where an element of this type is repeatable, the expectation is that each repetition contains different content, each of which can be expressed in multiple languages. The language designation goes on the individual String.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:InternationalStringType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Packaging structure for multiple language versions of the same string content, for objects that allow for internal formatting using XHTML tags. Where an element of this type is repeatable, the expectation is that each repetition contains different content, each of which can be expressed in multiple languages.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:StructuredStringType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A structured display label. Label provides display content of a fully human readable display for the identification of the object. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:LabelType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for non-formatted language specific strings that may be translations from other languages, or that may be translatable into other languages. Only one string per language/scope type is allowed. LanguageSpecificString contains the following attributes, xmlang to designate the language, isTranslated with a default value of false to designate if an object is a translation of another language, isTranslatable with a default value of true to designate if the content can be translated, translationSourceLanguage to indicate the source languages used in creating this translation,  translationDate, and scope which can be used to define intended audience or use such as internal, external, etc.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:StringType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition ============ Supports the optional use of formatting tags expressed with escape characters within the string structure. Language of the string is defined by the attribute language. Scope of the string is defined by scope. Language and Scope are used to filter selection and use of content based on unique combinations of these two properties. The content can be identified as translated (isTranslated), subject to translation (isTranslatable), the result of translation from one or more languages (translationSourceLanguages), carry an indication whether or not it should be treated as plain text (isPlain), identification of the structure used (structureUsed) which is an internal enumeration, and the ability to identify a structure not available in the enumeration by declaring structureUsed="Other" and specifying the other structure (otherDefined). Examples ========== The content: 
a bit of text
with some specialties highlighted 
Would be entered as: 
with some specialties highlighted 
Explanatory notes =================== Synonyms ========== DDI 3.2 mapping ================= r:ContentType RDF mapping ============= GSIM mapping ==============


Note:
Definition
============
Provides Level information for the members of the LevelStructure. levelNumber provides the level number which may or may not be associated with a category which defines level.

Examples
==========


Explanatory notes
===================
ISCO-08: index='1' label of associated category 'Major',  index='2' label of associated category 'Sub-Major',  index='3' label of associated category 'Minor', 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specification of the line and offset for the beginning and end of the segment.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:LineParameterType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Literal (static) text to be used in an instrument.  The value is a LanguageSpecificStruccturedString with the addition of an attribute allowing for the specification that white space is to be preserved.

Examples
==========
The text string "     Comment vous appelez-vous?" with the leading spaces included, described as being in French.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:LiteralTextType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
This is an identifier in a given local context that uniquely references an object, as opposed to the full ddi identifier which has an agency plus the id.

Examples
==========
The name of a variable within a dataset is a localId. Software systems might use their own identifier systems for performance reasons (e.g. incrementing integers).

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Name of the location using the DDI Name structure and the ability to add an effective date.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:LocationNameType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type LogicalRecord

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines complex relationship between LogicalRecords. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the correspondence between concepts in a correspondence table related to one or more Statistical Classifications.

Examples
==========


Explanatory notes
===================
A Map is the pairing of similar Concepts. Each Concept in the Map belongs to a different Collection. The collection of maps for all the Concepts in corresponding Collections is a Correspondence Table.

A simple example might map the following 2 martial status category sets:
MS1 -
single
married
widowed
divorced

MS2 -
single
married

So, a correspondence table between these 2 category sets might look like this:
MS1                                               MS2
single                                             single
widowed                                          "
divorced                                          "
married                                            married

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Map


Note:
Definition
============
Used to preserve an historical date, formatted in a non-ISO fashion.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:HistoricalDateType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Structures a numeric range. Low and High values are designated. The structure identifies Low values that should be treated as bottom coded (Stated value and bellow, High values that should be treated as top coded (stated value and higher), and provides a regular expression to further define the valid content of the range.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:NumberRangeType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes a bounding value for a number range expressed as an xs:demical.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:NumberRangeValueType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A standard means of expressing a Name for a class object.  A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles.

Examples
==========


Explanatory notes
===================
USE in Model: In general the property name should be "name" as it is the name of the class object which contains it. Use a specific name (i.e. xxxName) only when naming something other than the class object which contains it.

Synonyms
==========


DDI 3.2 mapping
=================
r:NameType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Names by which the organization is known. Use the attribute isFormal="true" to designate the legal or formal name of the Organization. The preferred name should be noted with the isPreferred attribute. Names may be typed with TypeOfOrganizationName to indicate their appropriate usage.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:OrganizationNameType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A tightly bound pair of items from an external controlled vocabulary. The extent property describes the extent to which the parent term applies for the specific case. 

Examples
==========
When used to assign a role to an actor within a specific activity this term would express the degree of contribution. Contributor with Role=Editor and extent=Lead.

Alternatively. the term might be a controlled vocabulary from a list of controlled vocabularies, e.g. the Generic Longitudinal Business Process Model (GLBPM) in a list that could include other business process model frameworks. In this context the extent becomes the name of a business process model task, e.g. "integrate data" from the GLBPM.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type PhysicalRecordSegment

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines structured relationship between PhysicalRecordSegments.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A closed plane figure bounded by three or more line segments, representing a geographic area. Contains either the URI of the file containing the polygon, a specific link code for the shape within the file, and a file format, or a minimum of 4 points to describe the polygon in-line. Note that the first and last point must be identical in order to close the polygon. A triangle has 4 points.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:PolygonType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
References an image using the standard Image description. In addition to the standard attributes provides an effective date (period), the type of image, and a privacy ranking.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:PrivateImageType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes a bounding value of a string.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:RangeValueType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Textual description of the rationale/purpose for the version change and a coded value to provide an internal processing flag within and organization or system. Note that versioning can only take place on objects owned by the specified DDI Agency. If you are creating a local instance of an object from another agency for current or future modification use BasedOnObject. If the changes being made result in what you determine to be new object rather than a version of a previous object, i.e. the change is too extensive to consider it a version of the existing object, create a new object and use BasedOnObject to provide a link to the object or objects that were a basis for the new object.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:VersionRationaleType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The date covered by the annotated object. In addition to specifying a type of date (e.g. collection period, census year, etc.) the date or time span may be associated with a particular subject or keyword. This allows for the expression of a referent date associated with specific subjects or keywords. 

Examples
==========
A set of date items on income and labor force status may have a referent date for the year prior to the collection date. To express a duration the preference is for Start and End dates expressing two time points separated by a "/". 

Explanatory notes
===================
Note that if needed you may use Start and Duration or Duration and End. These options may not be recognizable by all systems.

Synonyms
==========


DDI 3.2 mapping
=================
r:ReferenceDateType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides a means of identifying a related resource and provides the typeOfRelationship.  



Examples
==========
Standard usage may include: describesDate, isDescribedBy,  isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires, etc.

Explanatory notes
===================
Makes use of a controlled vocabulary for typing the relationship.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A structure used to express explicit segments or regions within different types of external materials (Textual, Audio, Video, XML, and Image). Provides the appropriate start, stop, or region definitions for each type.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:SegmentType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Lists the value and format type for the coordinate value. Note that this is a single value (X coordinate or Y coordinate) rather than a coordinate pair.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:SpatialCoordinateType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines a geographic line (minimum of 2 points)

Examples
==========
Street, River

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A geographic point consisting of an X and Y coordinate. Each coordinate value is expressed separately providing its value and format.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:PointType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Used to specify a relationship between one spatial object and another. Includes definition of the spatial object types being related, the spatial relation specification, and the event date.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The value of the statistic expressed as an xs:decimal and/or xs:double. Indicates whether it is weighted value and the computation base.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
pi:StatisticType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type StatisticalClassification

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specifies the Statistical Classifications for the source and target of the complex relationship and defines the relationship.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type Study

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Relation specification between source and target studies in a relation structure

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes summary statistics for a variable.

Examples
==========
Mean, standard deviation

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
pi:SummaryStatisticType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specifies details of target sample size, percentage, type, and universe

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Details of a telephone number including the number, type of number, a privacy setting and an indication of whether this is the preferred contact number.

Examples
==========
+12 345 67890123

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:TelephoneType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the segment of textual content used by the parent object. Can identify a set of lines and or characters used to define the segment.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:TextualType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
This Complex Data Type bundles a descriptiveText with an External Controlled Vocabulary Entry allowing structured content and a means of typing that content. For example specifying that the description provides a Table of Contents for a document.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
TypedString combines a typeOfContent with a content defined as a simple string. May be used wherever a simple string needs to support a type definition to clarify its content

Examples
==========
content is a regular expression and typeOfContent is used to define the syntax used.

Explanatory notes
===================
This is a generic type + string where property name and documentation should be used to define any specification for the content. If international structured string content is required use TypedStructuredString 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type ValueMapping

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Variable relationships in PhysicalLayout as defined using ValueMappingRelation

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The Value expressed as an xs:string with the ability to preserve whitespace if critical to the understanding of the content. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ValueType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type ConceptualVariable, RepresentedVariable, and InstanceVariable

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Ordered relations between any Variables in the Variable Cascade (Conceptual, Represented, Instance)

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the type and length of the video segment.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:VideoType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Member Indicator for use with member type VocabularyEntry

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Relation of Vocabulary Entries as defined using RelationSpecification 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A web site (normally a URL) with information on type of site, privacy flag, and effective dates.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:URLType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Associates an sequence ordering number with any WorflowStep or sub-type,

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Concept whose role is to define and measure a characteristic.

Examples
==========
Self-identified as "Male".  "Extremely Satisfied" as a response category.

Explanatory notes
===================
The Category is a Concept. It can have multiple name and display label properties as well as a definition and some descriptive text. As a "Signified" class there can be one or more "Sign" classes (e.g. a Code) that denotes it with some representation. The relationship is from the Code to the Category.

Synonyms
==========


DDI 3.2 mapping
=================
l:CategoryType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Relation structure of categories within a collection. Allows for the specification of complex relationships among categories.

Examples
==========
The category of student might be described as having sub-types of primary school student and high school student.

Explanatory notes
===================
The CategoryRelationStructure employs a set of CategoryRelations to describe the relationship among concepts. Each CategoryRelation is a one to many description of connections between categories. Together they might commonly describe relationships as complex as a hierarchy. 
This is a kind of a ConceptRelationStructure restricted to categories (which are concepts).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Specialization of a Concept System focusing on sets of categories used as specifications for a generalized concept. Can be used directly by questions to express a set of categories for a response domain or as the related source for a CodeList or StatisticalClassification

Examples
==========
"Male" and "Female" categories in a CategorySet named "Gender"

A CategorySet for an occupational classification system like ISCO-08 could use a ClassificationRelationStructure to describe a hierarchy (Chief Executives and Administrative and Commercial Managers as subtypes of Managers) without an associated Code List.


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Unit of thought differentiated by characteristics [GSIM 1.1]

Examples
==========
Poverty, Income, Household relationship, Family, Gender, Business Establishment, Satisfaction, etc.

Explanatory notes
===================
Many DDI4 classes are subtypes of the Concept class including Category, Universe, UnitType, ConceptualVariable. This class realizes the pattern class Signified and as such a Concept can be denoted by a Sign.

Synonyms
==========


DDI 3.2 mapping
=================
c:ConceptType

RDF mapping
=============


GSIM mapping
==============
Concept


Note:
Definition
============
Relation structure of concepts within a collection. Allows for the specification of complex relationships among concepts.

Examples
==========
A concept of vacation might be described as having sub-types of beach vacation and mountain vacation.

Explanatory notes
===================
The ConceptRelationStructure employs a set of ConceptRelations to describe the relationship among concepts. Each ConceptRelation is a one to many description of connections between concepts. Together they can describe relationships as complex as a hierarchy or even a complete cyclical network as in a concept map.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A set of Concepts structured by the relations among them. [GSIM 1.1] 

Examples
==========
1) Concept of Sex: Male, Female, Other 2) Concept of Household Relationship: Household Head, Spouse of Household Head, Child of Household Head, Unrelated Household Member, etc.  

Explanatory notes
===================
Note that this structure can be used to structure Concept, Classification, Universe, Population, Unit Type and any other class that extends from Concept.

Synonyms
==========


DDI 3.2 mapping
=================
c:ConceptSchemeType

RDF mapping
=============


GSIM mapping
==============
Concept System


Note:
Definition
============
Relationship between 2 or more ConceptSystems described through mapping similarity relationships between their member Concepts.

Examples
==========
Correspondence between the concepts used to define the populations in the censuses of two countries with similarity mapping of Concepts "Resident Population", "Labor Force", "Housing Unit", etc. 

Explanatory notes
===================
Describes correspondence with one or more Maps which identify a source and target concept and defines their commonality and difference using descriptive text and controlled vocabularies.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Set of Concepts, both sentinel and substantive, that can be described by either enumeration or by an expression.

Examples
==========
Substantive: Housing Unit Tenure - Owned, Rented, Vacant; Sentinel: Non-response - Refused, Don't Know, Not Applicable 

Explanatory notes
===================
Intent of a Conceptual Domain is defining a set of concepts used to measure a broader concept. For effective use they should be discrete (non-overlapping) and provide exhaustive coverage of the broader concept.  

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The use of a Concept as a characteristic of a UnitType intended to be measured

Examples
==========
1. Sex of person
2. Number of employees 
3. Value of endowment

Explanatory notes
===================
Note that DDI varies from GSIM in the use of a UnitType rather than a Universe. "The use of a Concept as a characteristic of a Universe intended to be measured" [GSIM 1.1]

Synonyms
==========


DDI 3.2 mapping
=================
c:ConceptualVariableType

RDF mapping
=============


GSIM mapping
==============
Variable


Note:
Definition
============
The use of a Represented Variable within a Data Set.  The InstanceVariable describes actual instances of data that have been collected. 

Examples
==========
1) Gender: Dan Gillman has gender <m, male>, Arofan Gregory has gender<m, male>, etc. 
2) Number of employees: Microsoft has 90,000 employees; IBM has 433,000 employees, etc. 
3) Endowment: Johns Hopkins has endowment of <3, $1,000,000 and above>, 
Yale has endowment of <3, $1,000,000 and above>, etc.

Two InstanceVariables of a person's height reference the same RepresentedVariable. This indicates that they are intended to: be measured with the same unit of measurement, have the same intended data type, have the same SubstantativeValueDomain, use a SentinelValueDomain drawn from the same set of SentinelValueDomains, have the same sentinel (missing value) concepts, and draw their Population from the same Universe. In other words, the two InstanceVariables should be comparable.

Explanatory notes
===================
The InstanceVariable class inherits all of the properties and relationships of the RepresentedVariable (RV) class and, in turn, the ConceptualVariable (CV) class. This means that an InstanceVariable can be completely populated without the need to create an associated RepresentedVariable or ConceptualVariable. If, however, a user wishes to indicate that a particular InstanceVariable is patterned after a particular RepresentedVariable or a particular ConceptualVariable that may be indicated by including a relationship to the RV and or CV. Including these references is an important method of indicating that multiple InstanceVariables have the same representation, measure the same concept, and are drawn from the same Universe. If two InstanceVariables of a person's height reference the same RepresentedVariable. This indicates that they are intended to: be measured with the same unit of measurement, have the same intended data type, have the same SubstantativeValueDomain, use a SentinelValueDomain drawn from the same set of SentinelValueDomains, have the same sentinel (missing value) concepts, and draw their Population from the same Universe. In other words, the two InstanceVariables should be comparable. 


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Instance Variable


Note:
Definition
============
Set of specific units (people, entities, objects, events) with specification of time and geography.

Examples
==========
1. Canadian adult persons residing in Canada on 13 November 1956
2. US computer companies at the end of 2012  
3. Universities in Denmark 1 January 2011.

Explanatory notes
===================
Population is the most specific in the conceptually narrowing hierarchy of UnitType, Universe and Population. Several Populations having differing time and or geography may specialize the same Universe.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Population


Note:
Definition
============
A combination of a characteristic of a universe to be measured and how that measure will be represented.


Examples
==========
The pair (Number of Employees, Integer), where "Number of Employees" is the characteristic of the population (Variable) and "Integer" is how that measure will be represented (Value Domain).

Explanatory notes
===================
Extends from ConceptualVariable and can contain all descriptive fields without creating a ConceptualVariable. By referencing a ConceptualVariable it can indicate a common relationship with RepresentedVariables expressing the same characteristic of a universe measured in another way, such as Age of Persons in hours rather than years. RepresentedVariable constrains the coverage of the UnitType to a specific Universe. In the above case the Universe with the measurement of Age in hours may be constrained to Persons under 5 days (120 hours old). RepresentedVariable can define sentinel values for multiple storage systems which have the same conceptual domain but specialized value domains.

Synonyms
==========


DDI 3.2 mapping
=================
l:RepresentedVariableType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Description or list of possible sentinel concepts , e.g. missing values.

Examples
==========
Refused, 
Don't know, 
Lost in processing

Explanatory notes
===================


Synonyms
==========
missing categories

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Set of valid Concepts. The Concepts can be described by either enumeration or by an expression.

Examples
==========
An enumeration of concepts for a categorical variable like "male" and "female" for gender.

Explanatory notes
===================
A ConceptualVariable links a UnitType to a SubstantiveConceptualDomain. The latter can be an enumeration or description of the values (Signified) that the variable may take on. In the enumerated case these are the categories in a CategorySet that can be values, not the codes that represent the values. 
An example might be the conceptual domain for a variable representing self-identified gender. An enumeration might include the concept of “male” and the concept of “female”. These, in turn, would be represented in a SubstantiveValueDomain by codes in a CodeList like “m” and “f”, or “0” and “1”. 
A conceptual domain might be described through a ValueAndConceptDescription’s description property of “a real number greater than 0” or through a more formal logicalExpression of “(all reals x such that x >0) “. Even in the described case, what is being described are conceptual, not the symbols used to represent the values. This may be a subtle distinction, but allows specifying that the same numeric value might be represented by 32 bits or by 64 bits or by an Arabic numeral or a Roman numeral.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Conceptual Domain


Note:
Definition
============
The object of interest in a process step related to the collection or use of observational data.

Examples
==========
Here are 3 examples - 1. Individual US person (i.e., Arofan Gregory, Dan Gillman, Barack Obama, etc.) 2. Individual US computer companies (i.e., Microsoft, Apple, IBM, etc.) 3. Individual US universities (i.e., Johns Hopkins, University of Maryland, Yale, etc.) [GSIM 1.1]

Explanatory notes
===================
In a traditional data table each column might represent some variable (measurement). Each row would represent the entity (Unit)  to which those variables relate. Height measurements might be made on persons (UnitType) of primary school age (Universe) at Pinckney Elementary School on September 1, 2005 (Population). The height for Mary Roe (Unit)  might be 139 cm.
The Unit is not invariably tied to some value. A median income might be calculated for a block in the U.S. but then used as an attribute of a person residing on that block. For the initial measurement the Unit was the block. In the reuse the unit would be that specific person to which the value was applied.
In a big data table each row represents a unit/variable double. Together a unit identifier and a variable identifier define the key. And for each key there is just one value – the measure of the unit  on the variable. 
A big data table is sometimes referred to as a column-oriented data store whereas a traditional database is sometimes referred to as a row-oriented data store. The unit plays an identifier role in both types of data stores.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Unit


Note:
Definition
============
A Unit Type is a type or class of objects of interest.

Examples
==========
Person, Establishment, Household, State, Country, Dog, Automobile

Explanatory notes
===================
UnitType is the most general in the hierarchy of UnitType, Universe, and Population. It is a description of the basic characteristic for a general set of Units.  A Universe is a set of entities defined by a more narrow specification than that of an underlying UnitType. A Population further narrows the specification to a specific time and geography.
A Unit Type is used to describe a class or group of Units based on a single characteristic with no specification of time and geography.  For example, the Unit Type of “Person” groups together a set of Units based on the characteristic that they are ‘Persons’.
It concerns not only Unit Types used in dissemination, but anywhere in the statistical process. E.g. using administrative data might involve the use of a fiscal unit. [GSIM 1.1]

Synonyms
==========
Object Class [ISO11179]

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Unit Type


Note:
Definition
============
A defined set or class of people, entities, events, or objects, with no specification of time and geography, contextualizing a Unit Type

Examples
==========
1. Canadian adults (not limited to those residing in Canada)
2. Computer companies 
3. Universities

Explanatory notes
===================
Universe sits in a hierarchy between UnitType and Population, with UnitType being most general and Population most specific. A Universe is a set of entities defined by a more narrow specification than that of an underlying UnitType. A Population further narrows the specification to a specific time and geography.

If the Universe consists of people, a number of factors may be used in defining membership in the Universe, such as age, sex, race, residence, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. A universe may be described as "inclusive" or "exclusive". 

Not to be confused with Population, which includes the specification of time and geography.

Synonyms
==========


DDI 3.2 mapping
=================
c:UniverseType

RDF mapping
=============


GSIM mapping
==============
Population


Note:
Definition
============
A collection (group) of any type of Variable within the Variable Cascade (Conceptual, Represented, Instance) for purposes of management, conceptualization or anything other than organizing a logical record or physical layout.

Examples
==========
Variables within a specific section of a study, Variables related to a specific subject or keyword. Variables at a specified level of development or review.

Explanatory notes
===================
A simple ordered or unordered list of variables can be described via a set of VariableIndicator parameters. An optional VariableRelationStructure can describe a more complex structure for the collection. We might, for example, use the VariableRelationStructure to group variables by content within a Study or across a StudySeries.

Synonyms
==========


DDI 3.2 mapping
=================
l:VariableGroupType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
RelationStructure for use with any mixture of Variables in the Variable Cascade (Conceptual, Represented, Instance).

Examples
==========


Explanatory notes
===================
A VariableCollection can be described as a simple list, or as having a more complex structure. All of the "administrative" variables for a study might be described as just a simple list without a VariableRelationStructure. If, however, the administrative variables needed to be described in subgroups, a VariableRelationStructure could be employed.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides an identified value for a standard weight expressed as an xs:float. This object may be referenced by a variable or statistic and used as a weight for analysis.

Examples
==========
A simple sample survey without an individual weight variable will have a StandardWeight to be used on all cases: 1% sample has a sample weight of 100

Explanatory notes
===================
A simple random sample survey without an individual weight variable will have a StandardWeight to be used on all cases. This is common when the sample is a simple random sample of a population with no oversampling to provide larger case counts for small populations.

Synonyms
==========


DDI 3.2 mapping
=================
d:StandardWeightType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Contains summary and category level statistics for the referenced variable.

Examples
==========
A mean of values for a variable "Height". Counts for each level of variable "Gender" (male and female)

Explanatory notes
===================
 Includes information on the total number of responses, the weights in calculating the statistics, variable level summary statistics, and category statistics. The category statistics may be provided as unfiltered values or filtered through a single variable. For example the category statistics for Sex filtered by the variable Country for a multi-national data file. Note that if no weighting factor is identified, all of the statistics provided are unweighted.

Synonyms
==========


DDI 3.2 mapping
=================
pi:VariableStatisticsType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
High level, descriptive, human informative, algorithm statement used to describe the overall methodology. 

Examples
==========


Explanatory notes
===================
This would most commonly be used in a Codebook along with a MethodologyOverview and a DesignOverview.The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
High level, descriptive, human informative, design statement The design may be used to specify how a process will be performed in general. This would most commonly be used in a Codebook along with an AlgorithmOverview and a MethodologyOverview. The design informs a specific or implemented process as to its general parameters. Supports specification of any realization of Goal. 


Examples
==========


Explanatory notes
===================
Allows for the use of any realized Process. The methodology, design, and algorithm of a specific realized process should be used if available. The use of a generic Process such as a WorkflowProcess containing an Act would be appropriate here. Restriction would be done by inclusion of the appropriate realized process class(es) in a Functional View.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
High level, descriptive, human informative methodology statement used to describe the overall methodology, identify related design, algorithm, and process information. A methodology is normally informed by earlier research and clarifies how earlier research methods were incorporated into the current work. 



Examples
==========
The target of the relationship from Study: "hasMethodology"


Explanatory notes
===================
This would most commonly be used in a Codebook along with an AlgorithmOverview and a DesignOverview. Note that Process may be described in more detail than a high level overview.
Note that the algorithm may be implemented by multiple processes which are not limited to any specific type of Process. This can be constrained by the inclusion of only specific realizations of Process within a Functional View. Note that this MethodologyOverview can be used as a collective description of specific methodologies used by a Study or other broad set of metadata.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Process is an implementation of an algorithm. It is the series of steps taken as a whole. It is decomposable into ProcessSteps, but this decomposition is not necessary. 

Examples
==========
In descriptive document regarding ingest of a study into a repository: "Validation processes were run comparing all data against the provided documentation to check for out-of-range and invalid content."

Explanatory notes
===================
In a descriptive document, Process Overview provides a means of presenting the reader with a clear view of an overall process without going into the details of the process steps. Process Overview should be used when a description of the process in general is all that is desired.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An algorithm is an effective method that can be expressed within a finite amount of space and time and in a well-defined formal language for calculating a function. Starting from an initial state and initial input (perhaps empty), the instructions describe a computation that, when executed, proceeds through a finite number of well-defined successive states, eventually producing "output" and terminating at a final ending state. The transition from one state to the next is not necessarily deterministic; some algorithms, known as randomized algorithms, incorporate random input. [from www.wikipedia.org 15 April 2016]

The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The design pattern class may be used to specify or, again, defines how a process will be performed in general. The design informs a specific or implemented process as to its general parameters.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Process Design


Note:
Definition
============
Methodology brings together the design, algorithm, and process as a logically structured approach to an activity such as sampling, weighting, harmonization, imputation, collection management, etc. A methodology in normally informed by earlier research and clarifies how earlier research methods were incorporated into the current work.



Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Something that suggests the presence or existence of a fact, condition, or quality.

Examples
==========
The terms “Unemployment” and “Arbeitslosigkeit”

Explanatory notes
===================
It is a perceivable object used to denote a concept or an object.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Concept or object denoted by the signifier associated to a sign.

Examples
==========


Explanatory notes
===================
Concept or object represented by the sign.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Concept whose extension includes perceivable objects. 

Examples
==========
A perceivable object in the extension of a signifier is a token. For instance, the object 5 is a token of “the numeral five”, a signifier.

Explanatory notes
===================
A signifier has the potential to refer to an object.  In this case, the referring signifier is a label.  If that object is a concept, then the referring signifier is a designation.  A label is a representation of an object by a signifier which denotes it.  For instance, the token http://www.bls.gov is a label for the web site maintained for the US Bureau of Labor Statistics. The label is also an identifier, since it is intended to dereference the BLS web site. It is a locator, since the HTTP service is associated with it. Finally, ‘Dan Gillman’ is a name for a co-author of this paper, since the token is linguistic.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Process is an implementation of an algorithm. It is the set of process steps taken as a whole. It is decomposable into a single ProcessStep or multiple ProcessSteps organized by a Process Control Step.

Examples
==========
The Generic Longitudinal Business Process Model (GLBPM) identifies a series of processes like data integration, anonymization, analysis variable construction and so forth in the data lifecycle.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Process Design


Note:
Definition
============
A Process Step that controls the ordering of execution for one or more Process Steps. May be realized to provide needed controls such as sequencing, temporal relationships, or conditions as the means of ordering or triggering a Process Step. The abstract class does not dictate the means of designating the trigger for initiating a Process Step or ordering of those Process Steps. This provides the flexibility to define these in a way most appropriate to the realization and use.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
One of the constituents of a Process. It can be a composition or atomic and might be performed by a Service.

Examples
==========
Each step and substep in the Generic Longitudinal Business Process Model is a ProcessStep. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A means of performing a Process Step as part of a Business Function (an ability that an organization possesses, typically expressed in general and high level terms and requiring a combination of organization, people, processes and technology to achieve). 



Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Business Service


Note:
Definition
============
Defines the extent of a geographic unit for a specified period of time using Bounding Box, Inclusive and Exclusive Polygons, and an area coverage that notes a type of coverage (land, water, etc.) and measurement for the coverage. The same geographic extent may be used by multiple versions of a single geographic version or by different geographic units occupying the same spatial area.

Examples
==========
Bounding box for Burkino Faso: (N) 15.082773; (S) 9.395691; (E) 2.397927; (W) -5.520837.  Minnesota Land area: 206207.099 sq K, Water area: 18974.589 sq K 

Explanatory notes
===================
Clarifies the source of a change in terms of footprint of an area as opposed to a name or coding change. 

Synonyms
==========


DDI 3.2 mapping
=================
r:GeographicBoundaryType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A specific geographic unit of a defined Unit Type. A geographic unit may change its name, composition, or geographic extent over time. This may be tracked by versioning the content of the geographic unit. Normally a new version of a geographic unit would have a geographic (spatial) overlap with its previous version (a city annexing new area). A geographic unit ends when it is no longer a unit of the same unit type.

Examples
==========
The State of Minnesota from 1858 to date where the Unit Type is a State as defined by the United States Census Bureau. It has a geographic extent and supersedes a portion of the Territory of Minnesota and a portion of the Territory of Wisconsin. Minnesota territory had both a broader geographic extent, different Unit Type, and earlier time period (1849-1858) as did the Territory of Wisconsin. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:GeographicLocationType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the classification of specific geographic units into a classification system. As a subtype of Code List it can be used directly for the description of a value domain.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A description of each physical storage segment required to completely cover the logical record. A logical record may be stored in one or more segments housed hierarchically in a single file or in separate data files. All logical records have at least one segment.

Examples
==========
The file below has four InstanceVariables: PersonId, SegmentId, AgeYr, HeightCm. The data for each person (identified by PersonId) is recorded in two segments (identified by SegmentId), "a" and "b". AgeYr is on physical segment a, and HeightCm is on segment b. These are the same data as described in the UnitSegmentLayout documentation.
1 a  22
1 b 183
2 a 45
2 b 175


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
p:PhysicalRecordSegmentType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The PhysicalSegmentLayout is an abstract class used as an extension point in the description of the different layout styles of data structure description.

Examples
==========
Examples include UnitSegmentLayouts, event data layouts, and cube layouts (e.g. summary data).

Explanatory notes
===================
A PhysicalLayout is a physical description (e.g. UnitSegmentLayout) of the associated Logical Record Layout consisting of a Collection of Value Mappings describing the physical interrelationship of each related ValueMapping and associated Instance Variable.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Among other things defines the location of a DataPoint in a PhysicalSegment (e.g. the location of the representation of a variable in a text file). This is abstract since there are many different ways to describe the location of a segment - character counts, start and end times, etc.

Examples
==========
A segment of text in a plain text file beginning at character 3 and ending at character 123.

Explanatory notes
===================
While this has no properties or relationships of its own, it is useful as a target of relationships where its extensions may serve.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the location of a segment of text through character, and optionally line, counts. An adequate description will always include a startCharacterPosition and then may include an endCharacterPosition or a characterLength.
If StartLine is specified, the character counts begin within that line.
An endCharacterPosition of 0 indicates that whole lines are specified


Examples
==========
The segment beginning at line 3, character 4 and ending at line 27 character 13.
Alternatively the segment beginning at character 257 and ending at character 1350 of the whole body of text.
StartLine of 10, endLine of 12, startCharacterPosition of 1, endCharacterPosition of 0 means all of lines 10,11, and 12. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
UnitSegmentLayout supports the description of unit-record ("wide") data sets, where each row in the data set provides the same group of values for variables all relating to a single unit. Each logical column will contain data relating to the values for a single variable. 

Examples
==========
A simple spreadsheet. Commonly the first row of the table will contain variable names or descriptions.

The following csv file has a rectangular layout and would import into a simple table in a spreadsheet:
PersonId,AgeYr,HeightCm
1,22,183
2,45,175


Explanatory notes
===================
This is the classic rectangular data table used by most statistical packages, with rows/cases/observations and columns/variables/measurements. Each cell (DataPoint) in the table is the intersection of a Unit (row) and an InstanceVariable. 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides physical characteristics for an InstanceVariable as part of a PhysicalSegmentLayout

Examples
==========
A variable "age" might be represented in a file as a string with a maximum length of 5 characters and a number pattern of ##0.0

Explanatory notes
===================
An InstanceVariable has details of value domain and datatype, but will not have the final details of how a value is physically represented in a data file. A variable for height, for example, may be represented as a real number, but may be represented as a string in multiple ways. The decimal separator might be, for example a period or a comma. The string representing the value of a payment might be preceded by a currency symbol. The same numeric value might be written as “1,234,567” or “1.234567 E6”. A missing value might be written as “.”, “NA”, “.R” or as “R”. 
The ValueMapping describes how the value of an InstanceVariable is physically expressed. The properties of the ValueMapping as intended to be compatible with the W3C Metadata Vocabulary for Tabular Data (https://www.w3.org/TR/tabular-metadata/ ) as well as common programming languages and statistical packages. The “format” property, for example can draw from an external controlled vocabulary such as the set of formats for Stata, SPSS, or SAS.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The specification of a controlled vocabulary defines a set of values and their definitions together with the order relationships among those entries.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A set of CustomValues to be attached to some object.

Examples
==========
A set of OMB required information about a question.

The set of openEHR protocol information to be attached to a blood pressure Capture

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the relationships between Geographic Unit Types in a collection. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A structured collection of Unit Types defining a geographic structure. As a subtype of CodeList it may be used directly to describe a value domain.

Examples
==========
Country--State--County

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the relationships between Geographic Unit Types in a collection.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A means for describing the complex relational structure of Data Points in a Logical Record 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The information needed for understanding the physical structure of data coming from a file or other source. A StructureDescription also points to the Data Store it physically represents.

Examples
==========
The PhysicalDataProduct is the entry point for information about a file or other source. It includes information about the name of a file, the structure of segments in a file and the layout of segments.

Explanatory notes
===================
Multiple styles of structural description are supported: including describing files as unit-record (UnitSegmentLayout) files; describing cubes; and describing event-history (spell) data.

Synonyms
==========


DDI 3.2 mapping
=================
p:PhysicalDataProductType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A realization of RelationStructure that is used to describe the sequence of Value Mappings in a Physical Layout. This can be more complex than a simple sequence. 

Examples
==========
The W3C Tabular Data on the Web specification allows for a list datatype. In the example below there are three top level InstanceVariables
PersonID – the person identifier
AgeYr – age in year
BpSys_Dia – blood pressure (a list containing Systolic and Diastolic values)

There are two variables at a secondary level of the hierarchy
Systolic – the systolic pressure
Diastolic – the diastolic pressure

The delimited file below uses the comma to separate "columns" and forward slash to separate elements of a blood pressure list.

PersonID, AgeYr, BpSys_Dia
1,22,119/67
2,68,122/70

The PhysicalRelationStructure in this case would describe a BpSys_Dia  list variable as containing an ordered sequence of the Systolic and Diastolic InstanceVariables.


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
PhysicalStructureOrder orders thePhysicalRecordSegments  which map to a LogicalRecord.

Examples
==========


Explanatory notes
===================
The same LogicalRecordLayout may be the sourceMember in several adjacency lists. This can happen when PhysicalRecordSegments are also population specific. In this instance each adjacency list associated with a LogicalRecordLayout is associated with a different population.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A custom item description. This allows the definition of an item which is a member of a CustomStructure.
It defines the minimum and maximum number of occurrences and representation of a CustomValue.

Examples
==========
DegreeOfBurden for a question as required by the U.S. OMB.

BloodPressureCuffSize - the size of a blood pressure cuff specified for a particular protocol.

Explanatory notes
===================
This definition will be referenced by a CustomValue when recording a key,value instance

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Contains a set of CustomItemRelations which together define the relationships of Custom Structure.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Collection containing a set of item descriptions defining a structure for a set of key,value pairs

Examples
==========
The set of CustomItems which are to be used to document the OMB required information for a question.

The set of CustomItems used to describe an openEHR blood pressure protocol.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An instance of a  key, value pair for a  particular  key.

Examples
==========
OMBBurden,"High"

openEHRBPposition, "upper arm"

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
One entry term and its definition in an ordered list comprising a controlled vocabulary.

Examples
==========
aunt - The female sibling of a parent

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Contains the Vocabulary Relations used to structure the ControlledVocabulary

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A set of information used to identify a sample population within a larger population. The sample frame will contain identifying information for individual units within the frame as well as characteristics which will support analysis and the division of the frame population into sub-groups.

Examples
==========
A listing of all business enterprises by their primary office address with information on their industry classification, work staff size, and production costs. A telephone directory. An address list of housing units.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The Sample Population is the result of a sampling process. It is the subset of the population selected from the Sample Frame or Frames that will be used as respondents to represent the target population. Sample Populations may occur at a number of stages in the sampling process and serve as input to a subsequent sampling stage. The Sample Population should be validated against the intended sample population as described in the goal of the design and/or process.

Examples
==========
A list of phone numbers representing a random sample from a telephone book. The Counties selected from within a State from which Households will be selected using another sampling method.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Generic description of a sampling algorithm expressed by a Sampling Design and implemented by a Sampling Process. May include common algebraic formula or statistical package instructions (use of specific selection models).

Examples
==========
Random Sample; Stratified Random Sample

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Sampling plan defines the how the sample is to be obtained through the description of methodology or a model based approach, defining the intended target population, stratification or split procedures and recommended sample frames. The content of a sampling plan is intended to be reusable. The application of the sample plan is captured in Sampling Process.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides general description and specific targets for sample sizes including sub-populations.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The Sampling Procedure describes the population being sampled, the sampling frame and the sampling plan including steps and sub steps by referencing the universe, sample frames and sampling plans described in schemes. Target sample sizes for each stage can be noted as well as the process for determining sample size, the date of the sample and the person or organization responsible for drawing the sample.

Examples
==========
Census of Population and Housing, 1980 Summary Tape File 4, chapter on Technical Information. Overview is the Introduction generally describing the sample; there is a sample design section which provides a more detailed overview of the design. Additional external documentation provides detailed processes for sample adjustments needed for small area estimations, sample frames etc.

Explanatory notes
===================
This is a summary of the methodology of sampling providing both an overview of purpose and use of a particular sampling approach and optionally providing specific details regarding the algorithm, design, and process of selecting a sample.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides the details of the process used to apply the sampling design and obtain the sample. Sampling Process contains a Workflow Step which provides the constituents of a Workflow. It can be a composition (a set of Control Constructs) or atomic (an Act) and may be performed by a service. This allows the use of existing Workflow models to express various sampling process actions. Sampling Frames and Sample Population can be used as designated Inputs or Outputs using Parameters.

Examples
==========
A Split which takes a sampling stage and divides the sample frame into different subsets. A different sampling technique is applied to each subset. Once a split occurs each subset can have stages underneath, and the number of states under each split subset may differ.
A Stage is the application of a single sampling algorithm applied to a sampling frame. For instance, the US Current Population Survey samples geographic areas first before identifying household to contact within each of those areas.
A Stratification of a stage into multiple subsets. Each stratified group will be sampled using the same sampling approach. For example stratifying a state by ZIP Code areas in each of 5 mean income quintiles and then doing a random sample of the households in a set of Zip Codes. Allows for oversampling of identified subpopulations.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A description of the budget for any of the main publication types that can contain a reference to an external budget document.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:BudgetType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for a quality statement based on frameworks to be described using itemized properties. A reference to a concept, a coded value, or both can be used to specify the property from the standard framework identified in StandardUsed. Usage can provide further details or a general description of compliance with a standard.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ComplianceType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides information about data that are not currently available because of policies established by the principal investigators and/or data producers. Embargo provides a name and label of the embargo, the dates covered by the embargo, the rationale or reason for the embargo, a reference to the agency establishing the embargo, and a reference to the agency enforcing the embargo.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:EmbargoType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Evaluation for the purpose of reviewing the study, data collection, data processing, or management processes. Results may feed into a revision process for future data collection or management. Identifies the type of evaluation undertaken, who did the evaluation, the evaluation process, outcomes and completion date.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:ExPostEvaluationType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A statement of quality which may be related to an external standard or contain a simple overview, rationale, and usage statement. When relating to an external standard information on compliance may be added via the ComplianceStatement referenced by the Standard class.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:QualityStatementType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Identifies the external standard used and describes the level of compliance with the standard in terms specific aspects of the standard's content.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:StandardType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Study is the conceptual anchor for an individual collection activity resulting in a data set or data file. It can be both a part of a StudySeries as a wave etc. or an unrelated activity like a single survey project.

Examples
==========
ICPSR study 35575 Americans and the Arts [1973 - 1992] (ICPSR 35575). https://www.icpsr.umich.edu/icpsrweb/ICPSR/studies/35575?dataFormat%5B0%5D=SAS&keyword%5B0%5D=public+opinion&geography%5B0%5D=United+States&searchSource=revise  

Explanatory notes
===================
The Study class brings together many properties and relationships describing a set of data – coverage, kind of data, methodology, citation information, access information and more.

Synonyms
==========


DDI 3.2 mapping
=================
s:StudyUnitType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
StudyControl references a Study. StudyControl enables the representation of a research protocol at the Study level. [If the only purpose of the object is to carry a Study, it should be seriously considered for melting with another object. Modeling rules state that any object needs to have a reality of its own. Carrying another object is not a reality. If I misunderstood, please clarify the description instead]

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Allows for a complex nested structure for a Study Series

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A collection of studies which can be structured as a simple sequence, or with a more complex structure.

Examples
==========
An annual series of surveys.

Explanatory notes
===================
A set of studies may be defined in many ways. A study may be repeated over time. One or more studies may attempt to replicate an earlier study. The StudySeries allows for the description of the relationships among a set of studies.

A simple ordered or unordered sequence of studies can be described via the "contains StudyIndicator" property. More complex relationships among studies may also be described using the optional "isStructuredBy StudyRelationsStructure".

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Business Algorithm is used to express the generalized function of the Business Process.
The underlying properties of the algorithm or method rather than the specifics of any particular implementation. In short a description of the method in its simplest and most general representation.

Examples
==========
There are several well-established algorithms for performing data anonymization including "local suppression", "global attribute generalization" and "k-Anonymization with suppression" which is a specific combination of the two. An anonymizing business process might implement one of these algorithms.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
BusinessProcesses could be Generic Longitudinal Business Process Model (GLBPM) and/or Generic Statistical Business Process Model (GSBPM) steps and/or sub-steps. BusinessProcesses participate in a DataPipeline by virtue of their preconditions and postconditions. 

A BusinessProcess differs from a WorkflowStep by virtue of its granularity. Higher level operations are the subject of BusinessProcesses. A BusinessProcess has a WorkflowStepSequence through which these higher levels operations may optionally be decomposed into WorkflowSteps.

BusinessProcess preconditions and postconditions differ from input and output parameters because they don't take variables and values. Instead the subject of preconditions and postconditions are typically whole datasets.

Given this level of granularity it is possible to view a BusinessProcess through the Open Archival Information System (OAIS) Reference Model. So a BusinessProcess may optionally be described as a component of a Submission Information Package (SIP), an Archival Information Package (AIP) or a Dissemination Information Package (DIP).

Examples
==========
In a single BusinessProcess we might receive data from a data source or merge data from different data sources or create new variables and recodes or format data for data dissemination

Explanatory notes
===================
One or more PairedExternalControlledVocabularyEntry objects may be used to identify and characterize controlled vocabularies like the GLBPM, GSBPM and OAIS. The PairedExternalControlledVocabularyEntry both identifies both the model (term) and the step/sub-step of the model (extent). If a BusinessProcess combines two steps from the same model (GLBPM, GSBPM, OAIS, etc.) or from different models, multiple PairedExternalControlledVocabularyEntry objects can be specified.

Synonyms
==========
Task

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A DataPipeline is a single traversal of the Generic Longitudinal Business Model (GLBPM) and/or the Generic Statistical Business process Model (GSBPM) in the course of a study where a study is either one off or a wave in a StudySeries.

Examples
==========
In a study where the study is a wave in a StudySeries, we do a single traversal of the Generic Longitudinal Business Process Model. From one wave to the next the traversal may be different. Each traversal is described in a DataPipeline.

Extract Transform and Load (ETL) platforms support data pipelines to move data between systems. Using an ETL platform, data engineers create data pipelines to orchestrate the movement, transformation, validation, and loading of data, from source to final destination. The DataPipeline describes this "orchestration".

A prospective DataPipeline gives guidance to data engineers. It is a design pattern. A retrospective DataPipeline documents an ETL data pipeline after the fact.


Explanatory notes
===================


Synonyms
==========
Traversal, Data Lifecycle

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides a consistent path to identifying information regarding the DDI Document and is automatically available for all Functional Views (/DocumentInformation/Annotation etc.). It covers annotation information, coverage (general, plus specific spatial, temporal, and topical coverage), access information from the producer (persistent access control), access information from the local distributor (Local Access Control), information on related series (i.e. a study done as a series of data capture events over time, qualitative material that is part of a larger set, one of a series of funded data capture activities, etc.), funding information, and other document level information used to identify and discover information about a DDI document regardless of its Functional View type. Use the Annotation at this level to provide the full annotation of the DDI Document. Note that related materials can be entered within the Annotation fields.

Examples
==========


Explanatory notes
===================
Annotation associated with a specific class is the annotation of the metadata class itself, such as the Study, InstanceVariable, Concept, etc. The annotation associated with Document Information is to refer to the Document itself. Note that not all DDI instances are intended to be persistent documents. For those that are DocumentInformation provides a consistent set of discovery level information on the content of the whole rather than specific parts of the instance. 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
ExternalMaterial describes the location, structure, and relationship to the DDI metadata instance for any material held external to that instance. This includes citations to such material, an external reference to a URL (or other URI), and a statement about the relationship between the cited ExternalMaterial the contents of the DDI instance. It should be used as follows:as a target object from a relationship which clarifies its role within a class; or as the target of a relatedResource within an annotation.


Examples
==========
ExternalMaterial is used to identify material and optionally specific sections of the material that have a relationship to a class. There is a generic relatedMaterial on AnnotatedIdentifiable. This should be used to attach any additional material that the user identifies as important to the class. The properties typeOfMaterial, descriptiveText, and relationshipDescription should be used to clarify the purpose and coverage of the related material.

Explanatory notes
===================
Within the DDI model, ExternalMaterial is used as an extension base for specific external materials found such as an External Aid. It is used as a base for specifically related material (e.g. ExternalAid) by creating a relationship whose name clarifies the purpose of the related material.

Synonyms
==========


DDI 3.2 mapping
=================
r:OtherMaterialType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides information about the individual, agency and/or grant(s) which funded the described entity. Lists a reference to the agency or individual as described by a DDI Agent, the role of the funder, the grant number(s) and a description of the funding activity.

Examples
==========
A "millionaire grant" (funding description) from John Beresford Tipton, Jr. (individual). Exploration of the effect of sudden wealth and basis for a television episode (funder role).

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:FundingInformationType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An Act is an indivisible, atomic step, i.e. not composed of other steps. An Act can also be viewed as a terminal node in a hierarchy of Workflow Steps. 

Examples
==========
QuestionConstructType from DDI 3.x is an example of an Act.
GenerationInstructionType from DDI 3..x is an example of an Act extended to include a CommandCode used to create a derivation or recode for an InstanceVariable or other similar use 

Explanatory notes
===================
Act is named after the act in the HL7 RIM. This act can take many forms including an observation, a procedure, a referral, a prescription, a consent and so forth.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides an extensible framework for specific computation or transformation objects.

Examples
==========
In data processing, a ComputationAction might be a code statement in a code sequence.

In data capture, a ComputationAction might takes the form of a question, a measurement or instrument code.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:ComputationItemType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Type of WorkflowControlStep in which the execution flow is determined by one or more conditions.


Examples
==========
If-then-else and iterative structures.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
IfThenElse describes an if-then-else decision type of control construct. If the stated condition is met, then the associated Workflow Sequence in containsSubSeqence is triggered, otherwise the Workflow Sequence that is triggered is the one associated via elseContains.


Examples
==========
An IfThenElse object describes the conditional logic in the flow of a questionnaire or other data collection instrument, where if a stated condition is met, one path is followed through the flow, and if the stated condition is met, another path is taken.

Explanatory notes
===================
Contains a condition and two associations:
- one to the Workflow Sequence that is triggered when the condition is true (containsSubSequence), and 
- another to the Workflow Sequence that is triggered when the condition is false (elseContains). 


Synonyms
==========


DDI 3.2 mapping
=================
d:IfThenElseType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Iterative control structure to be repeated a specified number of times based on one or more conditions. Inside the loop, one or more Workflow Steps are evaluated and processed in the order they appear.

Examples
==========
A loop is set to repeat a fixed number of times (initialValue). A stepValue is initially specified. At the end of the loop the current value is decremented by the stepValue. The current value might be the initialValue or it might be the current value after the initialValue has been decremented one or more times.

Explanatory notes
===================
The Workflow Sequence contained in the Loop is executed until the condition is met, and then control is handed back to the containing control construct.

Synonyms
==========
ForLoop

DDI 3.2 mapping
=================
d:LoopType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
MetadataDrivenActions are Acts in which their logic is defined by validation and transformation rules expressed in some standard rule language.

Examples
==========
Some data management systems present users with a menu of actions they can use in a sequence to perform a specific task. The system engages the user in a dialog driven by an action template. The dialog completes the template which the system then uses to perform the action. The user doesn't write any code.

Explanatory notes
===================
Whereas ComputationActions are used in statistical packages like SPSS, Stata, SAS and R to perform data management and data transformations, MetadataDrivenActions are used by data pipelines, e.g. ETL (Extract Transform Load) platforms, along with ComputationActions.

In a data pipeline the user is presented with a menu of MetadataDrivenActions that are captured here in an external controlled vocabulary. Users enter into a dialog with the platform through which they customize the MetadataDrivenAction. The user writes no code. The dialog is saved.

In the course of this dialog the user might specify a data source, specify which variables to keep or drop, rename variables, specify join specifics, create a value map between two variables and so forth.

MetadataDrivenActions represent this dialog in some standard rule language, e.g. Structured Data Transformation Language (SDTL) , Validation and Transformation Language (VTL), etc.. In fact,  MetaDataDrivenAction can use VTL with certain "extensions". Together they form quasi-VTL. quasi-VTL in turn conforms to a known schema. Using this schema users can render the quasi-VTL as XHTML and record it in the MetadataDrivenAction quasiVTL property. quasiVTL supports structured text.

Note that we would like NOT to create specific subtypes of MetadataDrivenAction -- one for each transformation. In fact there are a dozen or more such actions that will be captured in the MetadataDrivenAction types external controlled vocabulary. As an alternative, users can optionally write structured text based on a known schema. In this approach we are able to "evolve" SDTL as needed without changing our model. Instead, as our language "evolves", we one have to update its schema.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An Input or Output to a Process Step defined by as a unique identifier. It may be a single value or an array. 

Examples
==========
A question might have dynamic text or, again, "fills". Depending on the gender of the subject, a question might say "he" or "she" and/or "him" or "her". A gender variable is passed into the question, and question code resolves the dynamic text.
A computation action may be expecting a numeric array of values [result of looping an "Age in years" question through every member of a household]. isArray = "true"; valueRepresentation would link to a SubstantiveValueDomain defining a numeric value with a possible valid range; and because the parameter occurs in the context of a computation action it is necessary to specify an alias (e.g. AGE). The alias links the parameter to the code in the computation.

Explanatory notes
===================
When used as an hasInputParameter it defines a value being used by Process Step as a direct input or as an alias value within an equation. When used as an hasOutputParameter it defines itself as the value of the variable, capture, or explicit value of the parent class or as a specific value in a computation output by assigning the related Alias and/or defining the item within an array. Providing a defaultValue ensures that when bound to another Parameter that some value will be passed or received. A Value Domain expressed as a SubstantiveValueDomain or a SentinalValueDomain may be designated to define the datatype and range( of the expected value.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Iterative control structure to be repeated until a specified condition is met. After each iteration the condition is tested. If the condition is not met, the associated Workflow Sequence in contains (inherited from Conditional Control Construct) is triggered. When the condition is met, control passes back to the containing Workflow Step.

Examples
==========
A RepeatUntil loop is similar to a RepeatWhile loop, except that it tests the Boolean expression after the loop rather than before. Thus, a RepeatUntil loop always executes the loop once, whereas if the Boolean expression is initially False, a RepeatWhile loop does not execute the loop at all. For example, in a household there is at last one person and a loop might contain a block of person questions. After the first person the last question in the block might be "Anyone else in the household"? The RepeatUntil would continue iterating until there was no-one else in the household.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:RepeatUntilType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Iterative control structure to be repeated while a specified condition is met. Before each iteration the condition is tested. If the condition is met, the associated Workflow Sequence in contains (inherited from Conditional Control Construct) is triggered. When the condition is not met, control passes back to the containing Workflow Step.

Examples
==========
A RepeatWhile loop is similar to a RepeatUntil loop, except that it tests the Boolean expression before the loop rather than after. Thus, a RepeatUntil loop always executes the loop once, whereas if the Boolean expression is initially False, a RepeatWhile loop does not execute the loop at all. For example, RepeatWhile may be used to pre-test a certain condition like if "the number of new people in a household is greater than 0" in which case a block of questions might be asked for each new person.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:RepeatWhileType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The components of a Split consists of a number of process steps to be executed concurrently with partial synchronization. Split completes as soon as all of its component process steps have been scheduled for execution.

Examples
==========


Explanatory notes
===================
Supports parallel processing that does not require completion to exit. 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
SplitJoin consists of process steps that are executed concurrently (execution with barrier synchronization). That is, SplitJoin completes when all of its components processes have completed. 

Examples
==========
A GANTT chart where a number of processes running parallel to each other are all prerequisites of a subsequent step.

Explanatory notes
===================
Supports parallel processing that requires completion of all included process steps to exit.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines complex synchronous or asynchronous temporal ordering control. Defines temporal relationships using Allen's Intervals.

Examples
==========


Explanatory notes
===================
When creating a specific subtype identify the workflow steps included in a structure that is appropriate to the subtype. For example, Split contains a relationship "executeConcurrently".

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A subtype of WorkflowStep which controls the ordering of Workflow Steps within a Process. Abstract base for specialized ordering conditions that have specific requirements to relay ordering information.

Examples
==========
A WorkflowStepSequence is a subtype of WorkflowControlStep which defines a sequential order for included steps.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Workflow Process is a realization of Process which identifies the Workflow Step Sequence which contains the WorkflowSteps and their order. It may identify the algorithm that it implements.

Examples
==========
Overall description of steps taken when ingesting a dataset into an archive; A Sampling Process; A step or sub-step of the Generic Longitudinal Business Process Model (GLBPM).

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A means of performing a Workflow Step as part of a concrete implementation of a Business Function  (an ability that an organization possesses, typically expressed in general and high level terms and requiring a combination of organization, people, processes and technology to achieve).

Examples
==========
A specification for an air flow monitor used to capture a measure for an ImplementedMeasure (a subtype of Act).

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
One of the constituents of a Workflow. It can be a composition or atomic and might be performed by a Service.

Examples
==========
A ControlConstruct that orchestrates steps and substeps in a Workflow is a WorkflowStep. An Act is a WorkflowStep.

Explanatory notes
===================
An atomic Workflow Step has no Control Constructs -- it's an Act. A composition consists of a tree of Control Constructs. In this tree Acts are associated with the leaf nodes.

Furthermore, a composition might be a glass box or a black box from the perspective of a service. If a service performs a WorkflowStep, it might invoke just the topmost ControlConstruct -- for example a WorkflowSequence. It may know nothing about the internal workings of the sequence. In this case the WorkflowStep is a black box.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Process Step


Note:
Definition
============
A WorkflowStepSequence controls the order of WorkflowSteps by defining a simple sequence.

WorkflowSteps that may be used in a WorkflowStepSequence may be of many subtypes, covering simple or computational acts, conditional steps such as an IfThenElse, temporally defined ordering controls such as Split and SplitJoin, or others designed for various specializations of the WorkflowProcess. .

WorkflowSteps in a WorkflowStepSequence exchange variables and values by way of output parameters, input parameters and their bindings.


Examples
==========
A WorkflowStepSequence can be used to describe the flow of questions in a questionnaire. 

A WorkflowStepSequence can be used to decompose a BusinessProcess like data integration or anonymization into a series of steps.



Explanatory notes
===================
If more complex temporal or graph ordering is required use the subtype StructuredWorkflowSteps.
The relationship "executes" in this instance of a WorkflowControlStep is an optional means of noting the set of WorkflowSteps managed by the sequence. Sequencing is done using orderedStep. This is currently an anomoly that should be resolved in future discussion application of transformation rules from UML model. 


Synonyms
==========


DDI 3.2 mapping
=================
d:SequenceType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Links the guidance instructions to specific unit types.

Examples
==========
Links one or more guides for the use of a sample (result) obtained in the first stage of complex sample with the unit type. A sample of Counties from which households will be selected in the next sample stage.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Something an enterprise does, or needs to do, in order to achieve its objectives.

A Business Function delivers added value from a business point of view. It is delivered by bringing together people, processes and technology (resources), for a specific business purpose. 

Business Functions answer in a generic sense "What business purpose does this Business Service or Process Step serve?" Through identifying the Business Function associated with each Business Service or Process Step it increases the documentation of the use of the associated Business Services and Process Steps, to enable future reuse.

Examples
==========
A Business Function may be defined directly with descriptive text and/or through reference to an existing catalogue of Business Functions. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Business Function


Note:
Definition
============
Goals are the "things" a method aims to achieve. A goal may be a business function (GSIM) corresponding to a function in a catalog of functions such as GSBPM or GLBMN. However, goals may be specified more broadly. For example, conducting a clinical trial might be the goal of a method. Machine learning might be the goal of a method. 



Examples
==========
To further distinguish a "goal" from an "output", consider the construction of a statistic. A goal may be the construction of the statistic. The output is the statistic. The output is data. The statistic by itself -- the output -- is arguably meaningless even if we capture the process of its construction. 

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Business Function


Note:
Definition
============
Provides a guide for the usage of a result within a specified application

Examples
==========
The applied use of a weight determined by a weighting process in analyzing a data set

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A precondition is a state. The state includes one or more goals that were previously achieved. This state is the necessary condition before a process can begin.

Examples
==========
Using goals and preconditions processes can be chained to form work flows. Note that these work flows do not include data flows. Instead data flows consisting ouf outputs, inputs and bindings are a separate swim lane. 

Explanatory notes
===================
A precondition related to a design defines the state that must exist in order for a design being applied. For example in applying a Sampling Design there may be a precondition for the existance of a sampling frame meeting certain specifications.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the results of a process for the purpose of linking these results to guidance for future usage in specified situations. Result is abstract and serves as a substitution base for the specified result of a specific instantiation of a methodology process.

Examples
==========
The use of a weight resulting from a sampling process by an analyst within the context of a specific set of variables. The class containing the weight would use the extension base Result, adding any additional required properties and relationships to describe it.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes access to the annotated object. This item includes a confidentiality statement, descriptions of the access permissions required, restrictions to access, citation requirements, depositor requirements, conditions for access, a disclaimer, any time limits for access restrictions, and contact information regarding access.

Examples
==========
A proprietary InstanceQuestion might have specific access restrictions.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
a:AccessType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A type of Spatial coverage describing a rectangular area within which the actual range of location fits. A BoundingBox is described by 4 numbers - the maxima of the north, south, east, and west coordinates found in the area.

Examples
==========
Burkino Faso: (N) 15.082773; (S) 9.395691; (E) 2.397927; (W) -5.520837

Explanatory notes
===================
A BoundingBox is often described by two x,y coordinates where the x coordinates are used for the North and South Latitudes and y coordinates for the West and East Longitudes

Synonyms
==========
r:BoundingBox

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Coverage information for an annotated object. Includes coverage information for temporal, topical, and spatial coverage. 

Examples
==========
A survey might have ask people about motels they stayed in (topical coverage) in the year 2015 (temporal coverage), while they were travelling in Kansas (spatial coverage). This is different than the temporal, and spatial attributes of the population studied – (international travelers to the US surveyed in 2017).

Explanatory notes
===================
Coverage is a container for the more specific temporal, spatial, and topical coverages to which it refers.

Synonyms
==========


DDI 3.2 mapping
=================
r:CoverageType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A description of spatial coverage (geographic coverage) of the annotated object. Spatial coverage is described using a number of objects that support searching by a wide range of systems (geospatial coordinates, geographic classification systems, and general systems using dcterms:spatial).

Examples
==========
A country, a neighborhood, the inside of a polygon on the surface of the earth, along a street, at a particular intersection, or perhaps even in a certain orbit around the planet Mars. For a data set within a study this may be used to define the geographic restriction of the data set within the geographic coverage of the study (eg. The study may cover all of Sweden but the spatial coverage of the data set is Stockholm). 

Explanatory notes
===================
Different systems support different approaches to descriptions of geographic or spatial coverage. Dublin Core has a descriptive text field that is the equivalent of SpatialCoverage/description. Geographers need to understand the spatial objects available (spatialObject, highest and lowest level geography, geographic units and unit types) so they know the building blocks they have to create a map. Spatial search engines do a first pass search by a simple bounding box (the north and south latitudes and east and west longitudes that define the spatial coverage area). Spatial Coverage provides basic support for all of these uses.

Synonyms
==========
r:SpatialCoverage, place

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the temporal coverage of the annotated object by specifying dates and optionally associating them with Subject and Keyword. The date itself may be expressed as either and ISO and/or NonISO date. Dates may be catagorized by use of optional typeOfDate using and external controlled vocabulary entry.

Examples
==========


Explanatory notes
===================
The association of subjects or keywords with the date periods allows for describing the meaning of the temporal period. A survey, for example might be administered in one time period, but ask questions about the preceding decade. Temporal coverage might then include the data collection coverage as well as the referenced time period.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Describes the topical coverage of the module using Subject and Keyword. Subjects are members of structured classification systems such as formal subject headings in libraries. Keywords may be structured (e.g. TheSoz thesauri) or unstructured and reflect the terminology found in the document and other related (broader or similar) terms.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:TopicalCoverageType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a binary response, such as selected/unselected or checked/unchecked or true/false.

Examples
==========


Explanatory notes
===================
Exactly what is captured may be dependent upon the Implemented Instrument, however the response being captured is either there or not there (ON/OFF, True/False)

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A measurement that describes a means of capturing data. This class can be extended to account for different specific means. Use a specific instantiation of a Capture to describe a means of capturing a measurement.




Examples
==========
A survey question, blood pressure reading; MRI images; thermometer; web service; experimental observation. Classes could include InstanceQuestion, InstanceMeasurement or other class extending Capture.

Explanatory notes
===================
Provides an abstract base so that current and future forms of data capture can use this as an extension base and be freely mixed and matched within conceptual instruments as needed such as capturing a GPS point (using a RepresentedMeasurement) when administering a questionnaire (using RepresentedQuestions).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a coded response (where both codes and their related category value are displayed) for a question. This response domain allows the single selection of one coded response.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:CodeDomainType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Design plan for creating a data capture tool. 

Examples
==========
Design of a questionnaire regardless of mode; Design of an experiment

Explanatory notes
===================
A single ConceptualInstrument would contain workflow sequences of the intended flow logic of the instrument, which could be implemented as a web survey or paper survey, utilizing the same sequence and questions.
Similarly a single ConceptualInstrument would contain workflow sequences of the intended flow logic of the instrument, which could be implemented as a protocol delivered by a nurse or by self-administration.

Synonyms
==========
Idea; Intention; Theory; Design; LogicalInstrument

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Any external material used in an instrument that aids or facilitates data capture, or that is presented to a respondent and about which measurements are made. 

Examples
==========
Image, link, external aid, stimulus, physical object.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:OtherMaterialType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A specific data capture tool.  ImplementedInstruments are mode and/or unit specific.

Examples
==========
Two versions of a conceptual instrument, computer assisted personal interviewing (CAPI) and mail, would be separate ImplementedInstruments. These might both reference the same ConceptualInstrument. 
A piece of equipment used to measure blood pressure.


Explanatory notes
===================


Synonyms
==========
aka PhysicalInstrument

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An instance measurement instantiates a represented measurement, so that it can be used as an Act in the Process Steps that define a data capture process.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An instance question is an instantiation of a represented question,to be used as an Act in the process steps that define a survey questionnaire.

Examples
==========
“How old are you?”

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides the content and description of data capture instructions. Contains the "how to" information for administering an instrument.

Examples
==========
Completion instructions in self-administered mail questionnaire, information for administering a blood pressure measurement, interviewer instructions for a CATI questionnaire, guidance for communicating between an interviewer and a respondent (note MIDUS cognitive assessment example).

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:InstructionType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An InstrumentComponent that specifies the performance of a specific computation within the context of an instrument flow.

Examples
==========
quality control, edit check, checksums, compute filler text, compute values for use in administering the instrument

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:ComputationItemType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
InstrumentComponent is an abstract object which extends an Act (a type of Process Step). The purpose of InstrumentComponent is to provide a common parent for Capture (e.g., Question, Measure), Statement, and Instructions.



Examples
==========


Explanatory notes
===================
InstrumentComponent acts as a substitution head (abstract) for semantically meaningful for objects that extend it and exist in an instrument.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a numeric response (the intent is to analyze the response as a number) for a question.

Examples
==========
Systolic blood pressure level, as an integer from 0 to 200

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
d:NumericDomainType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a ranking response which supports a "ranking" or "Ordering" of provided categories. 
Note: This item still must be modeled and is incomplete at this time.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The description of a reusable non-question measurement that can be used as a template that describes the components of a measurement. A type code can be used to describe the type of measure that was used.

Examples
==========
A measure providing a geographic point; A blood pressure protocol; A protocol for measuring an ocean current

Explanatory notes
===================
Non-question measurements often involve the use of specific machines or protocols to ensure consistency and comparability of the measure. The RepresentedMeasurement allows the reusable format and protocol to be housed in a repository for use by multiple studies or repeated studies.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The description of a reusable question, that can be used as a template that describes the components of a question

Examples
==========
A question in a question bank such as the content and format for a question on Race for all survey/censuses fielded by U.S. agencies as prescribed by the U.S. Office of Management and Budget (OMB)

Explanatory notes
===================
A question that is repeated across waves of a panel study can be reused and also allow reference to a RepresentedVariable. A question that has been tested for consistency of response and is used by multiple studies.

Synonyms
==========


DDI 3.2 mapping
=================
d:QuestionItemType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The possible list of values that are allowed by a Capture.

Examples
==========
Yes/No, Male/Female, Age in years, Open-ended text, Temperature, BP reading

Explanatory notes
===================
Identifies both the sentinel and substantive value domains used for capturing the response to a question

Synonyms
==========
GSIM & DDI: ResponseDomain

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a scaled response, such as a Likert scale. 
Note: This item still must be modeled and is incomplete at this time.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Statement is a type of Instrument Component containing  human readable text or referred material. 

Examples
==========
Introductory text; Explanations; Labels, Headers, Help screens, etc.  "Thank you for agreeing to take this survey. We will start with a brief set of demographic questions." "The following set of questions are related to your household income. Please consider all members of the household and all sources of income when answering these questions."

Explanatory notes
===================
It is not directly related to another specific Instrument Component such as an InstanceQueston or InstanceMeasurement. It may be placed anywhere in a WorkflowStepSequence. 

Synonyms
==========
DDI:StatementItem

DDI 3.2 mapping
=================
d:StatementItemType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A response domain capturing a textual response including the length of the text and restriction of content using a regular expression.

Examples
==========
Collecting the first name on an individual in an open ended text field

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
r:TextDomainType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Generic class representing members of a collection. 


Examples
==========
Classification Item, Process Step.

Explanatory notes
===================
Members have to belong to some Collection, except in the case of nested Collections where the top level Collection is a Member that doesn't belong to any Collection.

Member is not extended, it is realized (see Collection Pattern documentation).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Node


Note:
Definition
============
The minimal pattern for a comparison including a mapping between members.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides a basic pattern for a comparison map which identifies source and target members and details about their match. Source and target were retained as in describing differences and commonalities the direction of the comparison may be important.

Examples
==========
Comparing the Classification Items between Statistical Classifications; describing the comparative relationship between InstanceVariables in two LogicalRecords for use in linking records

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Provides ability to declare an optional sequence or index order to a CollectionMember. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines one kind of relationship between one member (source) and possibly several members (target).  The type of the relationship, a semantic, and totality definition may also be specified. 

Examples
==========
A member might have a ParentChild relation to several other members which is Anti-Reflexive, Anti-Symmetric, and Anti-Transitive. For a process this might have a semantic of "immediately follows". 

Explanatory notes
===================
A MemberRelation functions like an adjacency list (https://en.wikipedia.org/wiki/Adjacency_list) in graph theory, describing the relationships of one Member to multiple other members. All of these relationships must have the same RelationSpecification, Totality, and semantic. 
These might not be the only relations from the source Member if there are other relations with different properties.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The set of MemberRelations used to structure a Collection

Examples
==========


Explanatory notes
===================
The optional RelationStructure is used to describe relations among Members of the Collection that are more complex than a simple list. There can be multiple types of relation structures for a Collection and these in turn may each have a different semantic. These differences can be described by the properties of the Relation Structure, or in the case of hybrid structures described by the individual MemberRelations.
Each MemberRelations functions like an adjacency list (https://en.wikipedia.org/wiki/Adjacency_list) in graph theory, describing the relationships of one Member to multiple other members.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Simple Collection container (set or bag) that may be unordered or ordered using Member Indicator. This collection type is limited to expressing only unordered sets or bags, and simple sequences. Use when there is a need to limit the organization of the collection to one of these forms of organization 

Examples
==========
The sequencing of questions within a questionnaire where ordering and routing is done through conditional constructs such as IfThenElse, etc.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Structured Collection container extends a Simple Collection allowing it to optionally have an RelationshpStructure to model hierarchies and nesting or more complex network structures. Like Simple Collection it is also a subtype of Member to allow for nested collections. A Collection can be described directly as having unordered members or an indexed array of members through a set of MemberIndicators. 

Examples
==========
Node Sets, Schemes, Groups, Concept Systems are all types of Collections.

Explanatory notes
===================
Members have to belong to some Collection, except in the case of nested Collections where the top level Collection is a Member that doesn't belong to any Collection.
If a Collection is ordered as a simple list that ordering can be indicated by an index property of each MemberIndicator. If the Collection is unordered, the index is not necessary.
Collection is not extended, it is realized (see Collection Pattern documentation).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Node Set


Note:
Definition
============
A Datum is a designation (a representation of a concept by a sign) with a notion of equality defined. The sign itself is a perceivable object.

Examples
==========
A systolic blood pressure of 122 is measured. The Signifier for that measurement in this paragraph is the character string "122". The Datum in this case is a kind of Designation (Sign), which is the association of the underlying measured concept (a blood pressure at that level) with that Signifier.  The Datum has an association with an InstanceVariable which allows the attachment of a unit of measurement (mm Hg), a datatype, a Population, and the Act which produced the measurement.  These InstanceVariable attributes are critical for interpreting the Signifier.

Explanatory notes
===================
From GSIM 1.1 "A Datum is the actual instance of data that was collected or derived. It is the value which populates one or more Data Points. A Datum is the value found in a cell of a table." (https://statswiki.unece.org/display/GSIMclick/Datum )  A Datum could be copied to one or more datasets.
DDI4 takes a little more formal (semiotic) description of a Datum using the Signification Pattern. See the attached example.


NOTE: This is NOT datum from DDI3.2 (which is quite specific).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Datum


Note:
Definition
============
An IdentifierRole identifies one or more InstanceVariables as being identifiers within a ViewPoint. An IdentifierRole is a SimpleCollection of InstanceVariables acting in the IdentifierRole.


Examples
==========
A data record with four variables: "PersonId", "Systolic", "Diastolic", "Seated" might have a Viewpoint with 
PersonId defined as having the IdentifierRole
Systolic defined as having the MeasureRole
Diastolic defined as having the MeasureRole
Seated defined as having the AttributeRole

PersonId, Systolic, Diastolic, Seated
123,122,20,yes
145,130,90,no


Explanatory notes
===================
See the Viewpoint documentation for an in depth discussion of the uses of ViewpointRoles: http://lion.ddialliance.org/ddiobjects/viewpoint

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A realization of RelationStructure that is used to describe the order of InstanceVariables in a record for those cases where the variables have a more complicated logical order than a simple sequence.


Examples
==========


Explanatory notes
===================
For a simple sequence the order can be defined by the index values of the LogicalRecord's InstanceVariableIndicators that a UnitDataRecord inherits. Alternatively, the InstanceVariableRelationStructure can be used by a UnitDataRecord to describe a StructuredCollection as needed. 


Synonyms
==========
An information model, a struct in C, a nested object in JSON

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The LogicalRecord is a record definition. It is abstract.

The actual realization of record definitions are provided by the UnitDataRecord and the DataCube. UnitDataRecords support two types of record definitions. The first is based on the SimpleCollection it inherits from LogicalRecord. The second type is a StructuredCollection that specializes the LogicalRecord. As a SimpleCollection a UnitDataRecord can, for example, provide table definitions. As a StructuredCollection, UnitDataRecord can define structures comparable to a "struct" in C or a JSON nested object. A UnitDataRecord, then, inherits SimpleCollection from LogicalRecord but adds its own StructuredCollection into the mix. The DataCube brings into play its own StructuredCollection which is distinct from the UnitDataRecord StructuredCollection.The DataCube StructuredCollection is not currently in scope.

The various record definitions -- simple and structured -- when they are actually instantiated with data is described by the PhysicalLayout of a LogicalRecord in the FormatDescription package. The PhysicalLayout places data into DataPoints formed at the direction of a LogicalRecord and its instance variables. At this point a LogicalRecord turn into a "dataset" that hosts unit records, A record definition is not a record. So we conflate metadata and data when we refer to a LogicalRecord as an empty table.

Examples
==========
SQL Data Definition Language (DDL) traffics in record definitions. SQL queries on "system tables" discover record definitions.

Explanatory notes
===================
In GSIM a DataPoint is a member of a "DataSet" and a UnitDataRecord. Since a DataPoint contains "Datum", this can lead to the conflation of a DataSet and a record definition. In the presence of a DataPoint it is difficult to be clear that a record definition does not have any rows. 

In DDI4 we defer the introduction of DataPoints until PhysicalLayouts are described. In this approach the instance variables that make up a LogicalRecord work downstream where they help to give each DataPoint in a PhysicalRecord its format.

Synonyms
==========
Record Type, Data Structure

DDI 3.2 mapping
=================
l:LogicalRecordType

RDF mapping
=============


GSIM mapping
==============
Data Structure


Note:
Definition
============
Allows for the complex structuring of relationships between LogicalRecords in a DataStore

Examples
==========
A DataStore with a Household, Family, and Person LogicalRecord type. Allows for describing parent/child, whole/part, or other relationships as appropriate

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A MeasureRole identifies one or more InstanceVariables as being measures within a ViewPoint. A MeasureRole is a SimpleCollection of InstanceVariables acting in the MeasureRole.



Examples
==========
A data record with four variables: "PersonId", "Systolic", "Diastolic", "Seated" might have a Viewpoint with 
PersonId defined as having the IdentifierRole
Systolic defined as having the MeasureRole
Diastolic defined as having the MeasureRole
Seated defined as having the AttributeRole

PersonId, Systolic, Diastolic, Seated
123,122,20,yes
145,130,90,no


Explanatory notes
===================
See the Viewpoint documentation for an in depth discussion of the uses of ViewpointRoles: http://lion.ddialliance.org/ddiobjects/viewpoint

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The RecordRelation object is used to indicate relationships among record types within and between LogicalRecords. For InstanceVariables existing in a LogicalRecord with multiple record layouts, pairs of InstanceVariables may function as paired keys to permit the expression of hierarchical links between records of different types. These links between keys in different record types could also be used to link records in a relational structure.

Examples
==========
One LogicalRecord containing a PersonIdentifier and a PersonName and another LogicalRecord containing a MeasurementID, a PersonID, a SystolicPressure, and a DiastolicPressure could be linked by a RecordRelation. The RecordRelation could employ an InstanceVariableValueMap to describe the linkage between  PersonIdentifier and PersonID.

Explanatory notes
===================
A household-level LogicalRecord might contain an InstanceVariable called HouseholdID and a person-level LogicalRecord might contain an InstanceVariable called HID. Describing a link between HouseholdID and HID would allow the linking of a person-level LogicalRecord to their corresponding household-level LogicalRecord.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition ============ Gives a UnitDataRecord structure to a Logical Record. UnitDataRecord structures a LogicalRecord as either a SimpleCollection or a StructuredCollection (InstanceVariableRelationStructure) of instance variables. The UnitDataRecord also organizes instance variables in a UnitDataViewpoint. The UnitDataViewpoint assigns roles to Instance Variables. In any one UnitDataViewpoint UnitDataRecord instance variables play one of three roles: identifier, measure or attribute. The same UnitDataRecord may have many UnitDataViewpoints. The UnitDataViewPoint can work in conjunction with the InstanceVariableRelationStructure. Together they can break out instance variables into complex (hierarchical) identifier, measure and attribute groups. Examples ========== The UnitDataRecord can be used to specify the structure of a table in a relational database. It can be used to specify the structure of both the fact and dimension tables in a data warehouse. It can be used to specify the structure of a big data table. Likewise it can be used to specify the structures of "column-based" and "row-based" tables. The UnitDataRecord may also form an information model if it is a StructuredCollection. Blood Pressure as described by an openEHR archetype is an information model. So is a collection of FHIR (HL7) resources that form an Electronic Health Record (EHR). Explanatory notes =================== The openEHR archetype is a use case that motivates the use of the InstanceVariableRelationStructure together with a UnitDataViewPoint. In the Blood Pressure archetype as well as most other archetypes attributes are not a SimpleCollection. Instead they are part of a StructuredCollection that breaks out attributes into "Protocol", "State" and "Events". In other archetypes the measure may be structured. For example body composition data includes a "base model" (fat mass, fat percentage, fat free mass), an "atomic level" (chemical elements, hydrogen, carbon, oxygen), a "molecular level" (minerals, protein, fat, water) and so forth. It is, however, possible to break out attributes into not one but many SimpleCollections in the event attributes and/or data do not form StructuredCollections. That is because the UnitDataViewpoint supports not just one but many attribute roles within the same viewpoint. Synonyms ========== Table Definition if the UnitDataRecord is a SimpleCollection, Information Model if the UnitDataRecord is a StructuredCollection DDI 3.2 mapping ================= RDF mapping ============= GSIM mapping ==============


Note:
Definition
============
The assignment of measure, identifier and attribute roles to InstanceVariables

Each of three roles within a UnitDataViewpoint is a SimpleCollection of instance variables. 

Examples
==========
Assigning 
PatientID the role of identifier
systolic the role of measure
diastolic the role of measure
device the role of attribute
time the role of attribute
position (sitting, standing) the role of attribute

Explanatory notes
===================
Viewpoint is a UnitDataViewpoint to underline that the composition of a UnitDataRecord viewpoint is different from the composition of DataCube viewpoint. The DataCube viewpoint is out of scope currently. 
It is sometimes useful to describe a set of variables and their roles within the set. In the blood pressure example above, values for a set of variables are captured in one setting - the taking of a blood pressure. Some of the variables may be the measures of interest, for example the systolic and diastolic pressure. Other variables may take on the role of identifiers, such as the hospital’s patient ID and a government ID such as the U.S. Social Security Number. A third subgroup of variables may serve as attributes. The age of the patient, whether she is sitting or standing, the time of day. The assignment of these three roles, identifier, measure, and attribute, is the function of the Viewpoint.
Viewpoints are not fixed attributes of variables. This is why there is a separate Viewpoint class which maps to InstanceVariables.   In the example above, the Viewpoint is within the context of the original measurement. In a reanalysis of the data the roles might change. Time of day might be the measure of interest in a study of hospital practices.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Used to identify objects for purposes of internal and/or external referencing. Elements of this type are versioned. Provides identification and administrative metadata about the object. Adds optional annotation. Use this as the extension base for First Order Classes that contain intellectual content that needs to be discoverable in its own right.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Used to identify objects for purposes of internal and/or external referencing. Elements of this type are versioned and provide administrative metadata properties. Use for First Order Classes whose content does not need to be discoverable in its own right but needs to be related to multiple classes. 

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
An AttributeRole identifies one or more InstanceVariables as being attributes within a ViewPoint. An AttributeRole is a SimpleCollection of InstanceVariables acting in the AttributeRole.


Examples
==========
A data record with four variables: "PersonId", "Systolic", "Diastolic", "Seated" might have a Viewpoint with 
PersonId defined as having the IdentifierRole
Systolic defined as having the MeasureRole
Diastolic defined as having the MeasureRole
Seated defined as having the AttributeRole

PersonId, Systolic, Diastolic, Seated
123,122,20,yes
145,130,90,no



Explanatory notes
===================
See the Viewpoint documentation for an in depth discussion of the uses of ViewpointRoles: http://lion.ddialliance.org/ddiobjects/viewpoint.
An InstanceVariable with an AttributeRole assigned might contain data about the conditions under which the MeausreRole InstanceVariables were collected or other paradata.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A DataPoint is a container for a Datum.

Examples
==========
A cell in a spreadsheet table. Note that this could be empty. It exists independently of the value to be stored in it.

Explanatory notes
===================
The DataPoint is structural and distinct from the value (the Datum) that it holds. [GSIM 1.1]

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Data Point


Note:
Definition
============
A DataStore is either a SimpleCollection or a StructuredCollection of LogicalRecords, keeping in mind that a LogicalRecords is a definition, not a "datasets".

LogicalRecords organized in a StructuredCollection is called a LogicalRecordRelationStructure.

Instances of LogicalRecords instantiated as organizations of DataPoints hosting data are described in FormatDescription.

A DataStore is reusable across studies. Each Study has at most one DataStore.


Examples
==========
The data lineage of an individual BusinessProcess or an entire DataPipeline are both examples of  a LogicalRecordRelationStructures. In a data lineage we can observe how LogicalRecords are connected within a BusinessProcess or across BusinessProcesses.

Explanatory notes
===================


Synonyms
==========
Schema repository, data network

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Data Set


Note:
Definition ============ A DataStoreLibrary is a collection or, again, a "library" of DataStores. An individual DataStore is associated with a Study. A collection of DataStores is associated with a StudySeries. The relationships among the DataStores in the DataStoreLibrary is described by the DataStoreRelationStructure. Relations may be more or less complicated depending on the StudySeries type. A StudySeries may be ad hoc. A StudySeries may form a time series. The variety of these collections has been described using the  in DDI 3.1. Like any RelationStructure, the DataStoreRelationStructure is able to describe both part/whole relations and generalization/specialization relations. See the controlled vocabulary at RelationSpecification to review all the types of relations a RelationStructure is able to describe. Examples ========== A StudySeries is a time series and a DataStoreRelationStructure is dedicated to tracking "supplements". There is a study at T0. Perhaps it is never executed. It is the "core" study. At T1 there is a study that includes the core and Supplement A. At T2 there is a study that includes the core, Supplement A and Supplement B. At T3 there is a study that includes the core and a one off supplement that is never asked again. T4 though T6 repeats T1 through T3. Explanatory notes =================== If we broke a study down into sub-studies where the core is a sub-study and each supplement is a sub-study, we could also use the DataStoreRelationStructure to track the generalization/specialization relationship or, again, "going deep" over time. Sometimes across a StudySeries we add panels. If panels were also sub-studies, we could use the DataStoreRelationStructure to track both the core and supplements by panel over time. Synonyms ========== Structured metadata archive DDI 3.2 mapping ================= RDF mapping ============= GSIM mapping ==============


Note:
Definition
============
A structure for describing a complex relation of DataStores within a DataStoreLibrary

Examples
==========
If the succession of DataStores are created by a StudySeries that is a time series, from one DataStore to the next part/whole relations can obtain as supplements are added and subtracted.

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A ViewpointRole designates the function an InstanceVariable performs in the context of the Viewpoint. (IdentifierRole, AttributeRole, or MeasureRole of interest).

Each of three roles within a Viewpoint may be a collection. This happens when a role is mapped to multiple instance variables. In this event a role forms a SimpleCollection. There are SimpleCollections of instance variables in each role.

Examples
==========


Explanatory notes
===================
See the Viewpoint documentation for an in depth discussion of the uses of ViewpointRoles: http://lion.ddialliance.org/ddiobjects/viewpoint

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
This package comprehends XML Schema datatypes which are used in the DDI model.


Note:
anyURI is like the primitive datatype "anyURI" of the XML Schema datatypes.

Definition from XML Schema Part 2: Datatypes Second Edition:
"anyURI" represents a Uniform Resource Identifier Reference (URI). An "anyURI" value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be a URI Reference). This type should be used to specify the intention that the value fulfills the role of a URI as defined by [RFC 2396], as amended by [RFC 2732].

For details see at https://www.w3.org/TR/xmlschema-2/#anyURI


Note:
language is like the derived datatype "language" of the XML Schema datatypes.

Definition from XML Schema Part 2: Datatypes Second Edition:
"language" represents natural language identifiers as defined by by [RFC 3066]. The value space of "language" is the set of all strings that are valid language identifiers as defined [RFC 3066] . The lexical space of language is the set of all strings that conform to the pattern [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*. The base type of "language" is token.

For details see at https://www.w3.org/TR/xmlschema-2/#language.


Note:
Definition
============
An actor that performs a role in relation to a process or product.

Examples
==========
Analyst performing edits on data, interviewer conducting an interview, a relational database management system managing data, organization publishing data on a regular basis, creator or contributor of a publication.

Explanatory notes
===================
foaf:Agent is: An agent (eg. person, group, software or physical artifact)
prov:Agent is An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.

Synonyms
==========
Agent

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A listing of Agents of any type. The AgentList may be organized to describe relationships between members using AgentRelationStructure.

Examples
==========
Organizations contributing to a project. Individuals within an agency. All organizations, indivduals, and machines identified within the collections of an archive.

Explanatory notes
===================
Relationships between agents are fluid and reflect effective dates of the relationship. An agent may have multiple relationships which may be sequencial or concurrent. Relationships may or may not be hierarchical in nature. All Agents are serialized individually and brought into relationships as appropriate.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Defines the relationships between Agents in a collection. Clarifies valid period and the purpose the relationship serve

Examples
==========
An individual employed by an Organization. A unit or project (organization) within another Organization.

Explanatory notes
===================
Describes relations between agents not roles within a project or in relationship to a product. Roles are defined by the parent class and relationship name that uses an Agent as a target.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A person who may have a relationship to another Agent and who may be specified as being associated with an act.

Examples
==========
Analyst performing edits on data, interviewer conducting an interview, a creator.

Explanatory notes
===================
A set of information describing an individual and means of unique identification and/or contact. Information may be repeated and provided effective date ranges to retain a history of the individual within a metadata record. Actions and relationships are specified by the use of the Individual as the target of a relationship (Creator) or within a collection of Agents in an AgentListing (employee of an Organization).

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Mechanism or computer program used to implement a process.

Examples
==========
SAS program, photocopier

Explanatory notes
===================
May be used as the target to describe how an action was performed. Relevent to data capture and data processing or wherever a role is performed by a Machine.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A framework of authority designated to act toward some purpose.

Examples
==========
U.S. Census Bureau, University of Michigan/ISR, Norwegian Social Data Archive 

Explanatory notes
===================
related to org:Organization which is described as "Represents a collection of people organized together into a community or other..."

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Identifies the authorizing agency and allows for the full text of the authorization (law, regulation, or other form of authorization).

Examples
==========
 May be used to list authorizations from oversight committees and other regulatory agencies.

Explanatory notes
===================
Supports requirements for some statistical offices to identify the agency or law authorizing the collection or management of data or metadata.

Synonyms
==========
Use for the Case Law, Case Law Description, and Case Law Date properties in ClassificationItem

DDI 3.2 mapping
=================
r:AuthorizationSourceType

RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Classification Family is a collection of Classification Series related from a particular point of view. The Classification Family is related by being based on a common Concept, as documented by the definingConcept relationship   (e.g. economic activity).[GSIM1.1]

Examples
==========
A family of industrial classifications each a separate series (i.e. U.S. Standard Industrial Classification (SIC) and North American Industrial Classification System (NAICS)

Explanatory notes
===================
Different classification databases may use different types of Classification Families and have different names for the families, as no standard has been agreed upon. [GSIM1.1]

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Classification Family


Note:
Definition
============
A Classification Index is an ordered list (alphabetical, in code order etc) of Classification Index Entries. A Classification Index can relate to one particular or to several Statistical Classifications. [GSIM Statistical Classification Model]

Examples
==========
An alphabetical index of a topically ordered Statistical Classification

Explanatory notes
===================
A Classification Index shows the relationship between text found in statistical data sources (responses to survey questionnaires, administrative records) and one or more Statistical Classifications.  A Classification Index may be used to assign the codes for Classification Items to observations in statistical collections. 
A Statistical Classification is a subtype of a Structured Collection.  [GSIM Statistical Classification Model]  Note that a GSIM Node is the equivalent of a DDI Member and a GSIM Node Set is a DDI Collection.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Classification Index


Note:
Definition
============
A Classification Index Entry is a word or a short text (e.g. the name of a locality, an economic activity or an occupational title) describing a type of object/unit or object property to which a Classification Item applies, together with the code of the corresponding Classification Item. Each Classification Index Entry typically refers to one item of the Statistical Classification. Although a Classification Index Entry may be associated with a Classification Item at any Level of a Statistical Classification, Classification Index Entries are normally associated with items at the lowest Level.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Classification Index Entry


Note:
Definition
============
A Classification Item represents a Category at a certain Level within a Statistical Classification.


Examples
==========
In the  2012 NAICS (North American Industry Classification System) one Classification Item has the Code 23 and the Category construction.

Explanatory notes
===================
A Classification Item defines the content and the borders of the Category. A Unit can be classified to one and only one item at each Level of a Statistical Classification. As such a Classification Item is a placeholder for a position in a StatisitcalClassification. It contains a Designation, for which Code is a kind; a Category; and other things. 

This differentiates it from Code which is a kind of Designation, in particular it is an alphanumeric string assigned to stand in place of a category. For example, the letter M might stand for the category Male in the CodeList called Gender.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Classification Item


Note:
Definition
============
A complex RelationStructure for use with statistical classification

Examples
==========
A ClassificationRelationStructure for ISCO-08 would describe each of the major classifications as a parent of its sub-classifications.   1 Managers, for example would be listed as a parent of four sub groups: 11 Chief Executives, Senior Officials and Legislators;  12 Chief Executives, Senior Officials and Legislators;  13 Production and Specialized Services Managers; and  14 Hospitality, Retail and Other Services Managers. 

Explanatory notes
===================
The ClassificationItemRelationStructure has a set of ClassificationItemRelations which are basically adjacency lists. A source ClassificationItem has a described relationship to a target list of ClassificationItem. The semantic might be, for example, "parentOf", or "contains", etc.. 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Classification Series is an ensemble of one or more Statistical Classifications, based on the same concept, as documented by the definingConcept relationship, and related to each other as versions or updates. Typically, these Statistical Classifications have the same name.

Examples
==========
ISIC or ISCO
SIC (with different published versions related to the publication year)

Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Classification Series


Note:
Definition
============
Describes the complex relation structure of a classification family.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A type of Designation that relates a representation expressed as a string with or without meaningful white space to a specific classification. For use in a Code List. The representation property (Value) is expressed as it would be found in a data file. Multiple representations may relate to the same Category but should be expressed as separate Codes.

Examples
==========
The letter M might stand for the category Male in the CodeList called Gender.

Explanatory notes
===================
A Code is a kind of Designation, in particular it is the assignment of an alphanumeric string to stand in place of a category. 

It should not be confused with a ClassificationItem which is a placeholder for a position in a StatisticalClassification. It contains a Designation, for which Code is a kind; a Category; and other things. For example, in 2012 NAICS (North American Industry Classification System) one Classification Item has the Code 23 and the Category construction.

Synonyms
==========


DDI 3.2 mapping
=================
l:CodeType

RDF mapping
=============


GSIM mapping
==============
Code


Note:
Definition
============
A list of Codes and associated Categories. May be flat or hierarchical. A hierarchical structure may have an indexed order for intended presentation even though the content within levels of the hierarchy are conceptually unordered. For hierarchical structures ClassificationRelationStructure is used to provide additional information on the structure and organization of the categories. Note that a CategorySet can be structured by a ClassificationRelationStructure without the need for associating any Codes with the Categories. This allows for the creation of a CategorySet, for example for a response domain, without an associated CodeList.

Examples
==========
The codes "M" and "F" could point to "Male" and "Female" categories respectively.

A CodeList for an occupational classification system like ISCO-08 could use a ClassificationRelationStructure to describe a hierarchy (Chief Executives and Administrative and Commercial Managers as subtypes of Managers)


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================
l:CodeListType

RDF mapping
=============


GSIM mapping
==============
Code List


Note:
Definition
============
Relation structure of codes within a codelist. Allows for the specification of complex relationships among codes.

Examples
==========


Explanatory notes
===================
The CodeRelationStructure employs a set of CodeRelations to describe the relationship among concepts. Each CodeRelation is a one to many description of connections between codes. Together they might commonly describe relationships as complex as a hierarchy.


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A Correspondence Table expresses relationships between the members within or between StatisticalClassifications.

Examples
==========
Correspondence between the U.S. Standard Industrial Classification (SIC) and North American Industrial Classification System (NAICS)

Explanatory notes
===================
CorrespondenceTables are used with Statistical Classifications. For instance, it can relate two versions from the same Classification Series; Statistical Classifications from different Classification Series; a variant and the version on which it is based; or, different versions of a variant. In the first and last examples, the Correspondence Table facilitates comparability over time.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Correspondence Table


Note:
Definition
============
A sign denoting a concept.

Examples
==========
A linking of the term “Unemployment” to an particular underlying concept.

Explanatory notes
===================
The representation of a concept by a sign (e.g., string, pictogram, bitmap) which denotes it. An example is the code M designating the marital status Married, which is a concept. In this context, M means Married.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Designation


Note:
Definition
============
An abstract base to allow all codifications (CodeList, StatisticalClassification, etc.) to be used as enumerated value representations.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
Structures relationship of Classification Index Entries in a Classification Index.

Examples
==========


Explanatory notes
===================


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The LevelStructure describes the nesting structure of a hierarchical collection. The levels within the structure begin at the root level '1' and continue as an ordered array through each level of nesting.



Examples
==========
ISCO-08 (Major, Sub-Major, and Minor) or NAICS (2 digit sector codes, 3 digit subsector code list, 4 digit industry group code list, and 5 digit industry code list)


Explanatory notes
===================
Levels are used to organize a hierarchy. Usually, a hierarchy often contains one root member at the top, though it could contain several. These are the first Level. All members directly related to those  in the first Level compose the second Level. The third and subsequent Levels are defined similarly. 

A Level often is associated with a Concept, which defines it. These correspond to kinds of aggregates. For example, in the US Standard Occupational Classification (2010), the Level below the top is called Major Occupation Groups, and the next Level is called Minor Occupational Groups. These ideas convey the structure. In particular, Health Care Practitioners (a Major Group) can be broken into Chiropractors, Dentists, Physicians, Vets, Therapists, etc. (Minor Groups) The Categories in the Nodes at the lower Level aggregate to the Category in Node above them.

"Classification schemes are frequently organized in nested levels of increasing detail. ISCO-08, for example, has four levels: at the top level are ten major groups, each of which contain sub-major groups, which in turn are subdivided in minor groups, which contain unit groups. Even when a classification is not structured in levels ("flat classification"), the usual convention, which is adopted here, is to consider that it contains one unique level." (http://rdf-vocabulary.ddialliance.org/xkos.html#) Individual classification items organized in a hierarchy may be associated with a specific level.

Synonyms
==========


DDI 3.2 mapping
=================
l:LevelType

RDF mapping
=============


GSIM mapping
==============
Level


Note:
Definition
============
The Value Domain for a sentinel conceptual domain. Sentinel values are defined in ISO 11404 as
"element of a value space that is not completely consistent with a datatype's properties and characterizing operations...". A common example would be codes for missing values.

Examples
==========
Missing categories expressed as Codes <-9, refused>; <-8, Don't Know> for a numeric variable with values greater than zero.  

Explanatory notes
===================
Sentinel values are used for processing, not to describe subject matter. Typical examples include missing values or invalid entry codes. Sentinel Value Domains are typically of the enumerated type, but they can be the described type, too.

This is not to say that sentinel values carry no information. Data on gender might be enumerated by "0, male" and "1, female". These are the substantive values (see Substantive Value Domain). However, there may be the need to include missing values along with that data, such as "m, missing" and "r, refused". These are sentinel values.

ISO/IEC 11404 - General purpose datatypes, defines sentinel values in terms of how that standard defines datatypes. But, the fact that the sentinels don't fit in terms of the calculations and statistics one would perform on the "clean" data is a distinguishing characteristic. In the example above, one would not include missing or refused data in calculating a ratio of females to the total population.

Sentinel values may be described rather than enumerated. For instance, there might be a range of values, each representing an out of range value, but there could be too many to enumerate. It is easier to describe the range.

In some software missing values are represented as values not in the datatype of the valid values. R has values of NA, NaN, Inf, and -Inf. SAS and Stata have values displayed as ".", ".A" through ".Z", and "._"

Other software might use values like 999 for missing that would otherwise be the same datatype as valid values but outside the parameters of the domain.

In the gender example above:
For SPSS the sentinel values might be represented as:
998 = "refused"
999 = "not recorded"

For SAS or Stata the sentinel values might be represented as:
.R = "refused"
.N = "not recorded"

Sentinel values can also be used for other purposes beyond missing. For a numeric variable "A" might represent a value somewhere in a defined range to prevent disclosure of information about an individual. This might be considered a "semi-missing value".
In SAS or Stata for example:
.A = "greater than or equal to 100 and less than 1000 "


Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Enumerated Value Domain


Note:
Definition
============
A Statistical Classification is a set of Categories represented by Classification Items which may be assigned to one or more variables registered in statistical surveys or administrative files, and used in the production and dissemination of statistics. The Categories at each Level of the classification structure must be mutually exclusive and jointly exhaustive of all objects/units in the population of interest. (Source: GSIM StatisticalClassification)

Examples
==========


Explanatory notes
===================
A Classification Item represents a Category at a certain Level within a Statistical Classification. The Categories are defined with reference to one or more characteristics of a particular universe of units of observation. A Statistical Classification may have a flat, linear structure or may be hierarchically structured, such that all Categories at lower Levels are sub-Categories of Categories at the next Level up. (Source: GSIM StatisticalClassification) 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============
Statistical Classification


Note:
Definition
============
A structure for describing the complex relationship between statistical classifications in a classification series

Examples
==========
A classification series that branches into separately versioned classifications

Explanatory notes
===================
Can use relation specification information to more fully describe the relationship between members such as parent/child, whole/part, general/specific, equivalence, etc.

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The Value Domain for a substantive conceptual domain. 

Examples
==========
All real decimal numbers relating to the subject matter of interest between 0 and 1 specified in Arabic numerals. [GSIM 1.1].
The codes "M" male and "F" for female .


Explanatory notes
===================
In DDI4 the value domain for a variable is separated into “substantive” and “sentinel” values. Substantive values are the values of primary interest. Sentinel values are additional values that may carry supplementary information, such as reasons for missing. This duality is described in ISO 11404. Substantive values for height might be real numbers expressed in meters. The full value domain might also include codes for different kinds of missing values - one code for “refused” and another for “don’t know”. Sentinel Values may also convey some substantive information and at the same time represent missing values. An example might be where a numeric variable like number of employees be sometimes a count and sometimes a code representing a range of counts in order to avoid disclosure of information about a specific entity. 

The SubstantiveValueDomain may use either a ValueDescription, for described values,  or a CodeList for enumerated values, or both. 

A value domain may consist of substantive values or sentinel values. Substantive values are those associated directly with some subject matter area. They do not address concerns around processing, such as missing values. Substantive values are called "regular values" in ISO/IEC 11404 - General purpose datatypes.

The enumerated case is one where all values are listed. An example is the categorical values for gender:
The conceptual domain could consist of the concept of male and the concept of female. These might be represented in codes and associated labels as
1 (="Male")
2 (="Female")

The described case is one where some description is needed to define the set of values.
Take the following description for height in meters:
"a real number between 0 and 3, represented to two Arabic decimal places". This description might be structured in some way to be machine actionable (datatype="double", min=0, max=3, decimals=2).


Synonyms
==========
value domain [ISO11179]

DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
A formal description of a set of values. 

Examples
==========
Example 1) 
The integers between 1 and 10 inclusive.  
The values of x satisfying the logicalExpression property:
" (1 <=x <= 10) AND mod(x,10)=0"
Also described with minimumValueInclusive = 1 and maximumValueInclusive = 10 (and datatype of integer)

Example 2)
The upper case letters A through C and X
described with the regularExpression "/[A-CX]/"


Example 3)
A date-time described with the Unicode Locale Data Markup Language pattern yyyy.MM.dd G 'at' HH:mm:ss zzz


Explanatory notes
===================
The ValueAndConceptDescription may be used to describe either a value domain or a conceptual domain. For a value domain, the ValueAndConceptDescription contains the details for a “described” domain (as opposed to an enumerated domain). There are a number of properties which can be used for the description. The description could be just text such as: “an even number greater than zero”. Or a more formal logical expression like “x>0 and mod(x,2)=0”. A regular expression might be useful for describing a textual domain. It could also employ a format pattern from the Unicode Locale Data Markup Language (LDML) (http://www.unicode.org/reports/tr35/tr35.html.
Some Conceptual Domains might be described with just a narrative. Others, though, might be described in much the same way as a value domain depending on the specificity of the concept.

In ISO 11404 a value domain may be described either through enumeration or description, or both. This class provides the facility for that description. It may be just a text description, but a description through a logical expression is machine actionable and might, for example, be rendered as an integrity constraint. If both text and a logical expression are provided the logical expression is to be taken as the canonical description.
The logical expression should conform to the expression syntax of VTL. https://sdmx.org/?page_id=5096 

Synonyms
==========


DDI 3.2 mapping
=================


RDF mapping
=============


GSIM mapping
==============


Note:
Definition
============
The permitted range of values for a characteristic of a variable. [GSIM 1.1]

Examples
==========
Age categories with a numeric code list; Age in years; Young, Middle-aged and Old

Explanatory notes
===================
The values can be described by enumeration or by an expression. Value domains can be either substantive/sentinel, or described/enumeration

Synonyms
==========
BUT NOT Grid/Numeric/Code/*_ResponseDomain [DDI-L/Questions] - this is "ResponseDomain"

DDI 3.2 mapping
=================
r:RepresentationType

RDF mapping
=============


GSIM mapping
==============
Value Domain


# t_package

Notes:
Purpose:
This view is intended to provide a structure for the information needed to understand and make intelligent use of a set of data without other communication from the person or organization producing the data. It can be used to move the data into and among multiple software platforms. This information is useful for discovery of the data.

The view includes basic information about how the data were collected, but does not provide machine actionable details.

The view provides information about:
Variables and the representation of the data for each, 
Basic statistics for individual variables
Universe and population, 
Spatial, temporal, and topical coverage
The study under which the data were created
Overviews of Methodology, Design, and Process
Physical storage


Use Cases:
Basic search to find data (general search, known item search) by users looking to use data. 
--Searches by variable, coverage, creators, time frame, population, methodology and more
Machine actionable ingest to statistical software allowing users to analyze the data
--An open standard for representing the metadata needed to read the data 
Informational content to support intelligent use and understanding of the data
--The essential information for interpreting and using the data (e.g. units of measurement, relevant population)


Target Audiences:
Individual researchers, research groups, National Statistical Organizations focusing on stand-alone codebooks, students, instructors, archives, and libraries. Software tool makers.

Restricted Classes:
DesignOverview references Precondition, Goal, and WorkflowProcess
InstanceVariable references RepresentedVariable, and ConceptualVariable, and the abstract class Act(InstrumentComponent, ComputationAction, StudyControl, and MetadataDrivenAction)
Methodology references Methodology
ProcessOverview references ProcessSequence
RepresentedMeasurement references ExternalAid
RepresentedQuestion references ExternalAid
SamplingProcedure references SamplingDesign, SamplingAlgorithm, and SamplingProcess
SentinelConceptualDomain references ConceptualSystem
SpatialCoverage references GeographicUnitClassification, and GeographicUnitTypeClassification
Study references AuthorizationSource
SubstantativeConceptualDomain references ConceptualSystem


Notes:
Purpose:
The Sampling View covers the methodology and process for drawing a sample from a designated sample frame. It provides the ability to describe sample designs from simple single stage samples to those with multiple stages and ones with more than one frame (necessitating drawing subsets of the sample from each frame). Probability sampling, including model-based, and non-probability sampling can each be described. The descriptive information of the methodologies used, design of the sample, algorithms to support the drawing of the sample, goals, sample frames used, and guidance on the use of the resulting sample (for defining weights, limitations, etc.) are supported. This includes the use of the Workflows which can define the process of creating simple or complex samples on a step-by-step basis. Can be used as metadata to drive sample selection.

Use Cases:
Defining Sample Frames for prospective use
Describing the process of simple or complex sampling procedures to inform the automated creation of a sample from a sample frame
Describe a sample to provide the information necessary to create sampling weights and estimation formulae.
Describe the processing of sampling for the purpose of informing the user of limitations or strengths of a particular sampling procedure and to provide guidance on the use of the procedure or the result of the procedure.

Target Audiences:
Organizations defining sample frames and sampling procedures for execution.
Users requiring information on the sampling process and its limitations.

Restricted Classes:
Parameter: valueRepresentation: ValueDomain: some subtypes not supported: SentinelValueDomain.

Precondition: basedOnPriorResult: Result: some subtypes not supported: SegmentDefintionResult, QualitativeCodingResult.

SamplingDesign: expressesAlgorithm: AlgorithmOverview: some subtypes not supported: SegmentDefinitionAlgorithm, QualitativeCodingAlgorithm, BusinessAlgorithm.

SamplingDesign: implementedBy: WorkflowProcess: all subtypes not supported.

SamplingProcedure: hasDesign: DesignOverview: some subtypes not supported: SegmentDefinitionDesign, QualitativeCodingDesign.

SamplingProcedure: isExpressedBy: AlgorithmOverview: some subtypes not supported: SegmentDefinitionAlgorithm, QualitativeCodingAlgorithm, BusinessAlgorithm.

SamplingProcedure: componentMethodology: MethodologyOverview: some subtypes not supported: SegmentDefinitionMethod, QualitativeCodingMethod.

Split: executeConcurrently: WorkflowStep: some subtypes not supported: Act, ConcurrentControlConstruct, SplitJoin.

SplitJoin: executeConcurrently: WorkflowStep: some subtypes not supported: Act, ConcurrentControlConstruct, Split.

Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.
Concept is extended by ConceptualVariable, RepresentedVariable and InstanceVariable.
ExternalMaterial is extended by ExternalAid.
WorkflowStepSequence is extended by StructuredWorkflowSteps.

General documentation:
In socio-economic statistics, samples are used to conduct surveys within time, accuracy, and expense constraints. When it comes time to conduct a survey, the sample is selected from a larger set, called the frame or sampling frame. Frames are an enumeration of the population the survey is designed to estimate, but they don’t contain the variables a survey or experiment might collect. The sample is a subset of the frame, and it is designed (in theory) to be representative of the population as a whole. In practice, for any selected sample, this might not be the case.

Samples can be based on probability or not. For a probability based sample, each element in the frame is assigned a probability it is selected for a sample. Non-probability samples do not have this feature, and the elements are selected in some other manner. The representativeness of a probability based sample is measured as sampling error, a statistical measure. Every probability sample has a sampling error associated with it. It is an indicator of how accurate estimates are to the theoretical population values.

Several methods can be used to select a sample. In the simple case, elements are selected from the frame in one step. In the probability based case, typical techniques are simple random sampling (with or without replacement), systematic random sampling, sampling proportional to size, and simple stratified random sampling. For non-probability samples, techniques include convenience, purposive, quota, self-selected, and snowball sampling.

Sampling in scientific experiments is different than for statistical surveys usually. Non-probability sampling is often used. Self-selected samples (for instance people who volunteer for a drug trial) are often seen. 

To help reduce sampling errors, improve estimates, reduce costs, and reduce the time to complete a survey, sampling is sometimes broken into parts. The first main way this is done is through the use of strata. Strata are subsets of a population with independent estimates. For example, the mean height of women is different than the mean height of men. Sampling based on stratification reduces sampling error.

The other main way samples are partitioned is through clusters. Clusters are subsets based on some convenience criteria. For example, to make sure interviews can be conducted in a short amount of time for a country-wide survey, selected sample units might need to be geographically close, or clustered. This will greatly reduce the time and cost for collecting data, but it has the reverse effect of increasing the sampling error. Representativeness is affected if only some geographical areas are used to select the sample.

Sometimes, so many clusters are identified that they are sampled themselves. Then within those selected, the units for collection are selected. This is a 2-stage sample, and it should not be hard to imagine more than 2 steps to reduce clusters to a manageable size before the ultimate sampling units are selected. Some statistical surveys in the US have 4 stages or more.

It is possible that for some survey, more than one frame is needed. For instance, in random dialing telephone surveys, a bank of valid telephone numbers is the frame, and some are selected for contact. However, the bank of valid telephone numbers might come from the telephone company, and they are all land-lines. To get full coverage of the population, one must also select from a bank of cellphone numbers. Thus, 2 frames are needed, 2 samples are selected for full coverage (representativeness) to be achieved.


Notes:
Purpose:
The Statistical Classification View brings together the structures need to record, organize, manage, and index Statistical Classifications. These classifications are often developed cooperatively and managed over time. They may be organized into series and families of classifications and use specified vocabularies. Mapping may be provided to express relationships between two or more Statistical Classifications in order to clarify change over time or the similarities and differences between Statistical Classifications in the same family (i.e. Industry, Occupation, Education).

Use Cases:
Industry: US-SIC, NAICS, GICS, ISIC; Occupational: ISCO, US-SOC; Geographic: US-FIPS, NUTS

Target Audience:
Organizations maintaining and managing shared Statistical Classifications.

Included Classes: 
AuthorizationSource, Category, ClassificationFamily, ClassificationIndex, ClassificationIndexEntry, ClassificationItem, ClassificationSeries, Code, Concept, ConceptParentChild, ConceptParentChildPair, ConceptPartWhole, ConceptPartWholePair, ConceptSystem, CorrespondenceTable, ExternalMaterial, Individual, Level, Map, Organization, StatisticalClassification, Vocabulary.

General Documentation:
The abstract class Designation serves as a relationship target for the following classes: ClassificationItem and Vocabulary. The only included class belonging to this abstract group is Code.
The abstract class Node serves as a relationship target for the following classes: Map and Level. The only included class belonging to this abstract group is ClassificationItem.
The abstract class NodeSet serves as a relationship target for the following class: CorrespondenceTable. The only included class belonging to this abstract group is StatisticalClassification.
The abstract class Agent serves as a relationship target for the following classes: CorrespondenceTable and AuthorizationSource. The only included classes belonging to this abstract group are Organization and Individual.
The abstract pattern class OrderedPair serves as a relationship target for the following class: Map. The only included class realizing this pattern is ConceptParentChildPair


Notes:
Purpose:
The purpose of Geographic Classification in DDI is to express relationships over time and space that are currently only available in geographic shape files or by exploring the data file itself. A great deal of legacy data does not have related geographic files. A large group of areas covered by DDI do not have clearly defined geography in terms of spatial extent, but have considerable relational information. Many geographic structures define geographic unit types with descriptive sub-sets (e.g. “Places of over 10,000 population” where the user must know whether a specific location meets that definition prior to determining if it is included in the data set).

Use Cases:
Describing geographic structures and their hierarchies
Describing geographic units and their corresponding locations (polygons, bounding boxes, points etc.)
Documenting changes to geographic units over time

Target Audiences:
Digital archivists
Search engines intent on exposing data by their geographical coverage
Researchers who need to describe complex geographical structures
Researchers who need to describe geographical structures and locations with changes over time

Restricted Classes:
ConceptSystem is extended by CategorySet
Concept is extended by Category, ConceptualVariable, RepresentedVariable, InstanceVariable, Population and Universe.
ExternalMaterial is extended by ExternalAid.

General Documentation:
Geographic classification uses unit, unit type, and collections to provide the basis for describing the geographic structure (unit types) and their individual locations (units) in a manner that supports complex layered hierarchies, changes in name, role, and geographic extent over time, and coding for direct use in value domains and responses. It supports the content of DDI Lifecycle Geographic Structure and Geographic Location.
The revision of the DDI 3.2 structure into the DDI4 structure addresses the following constraints in DDI 3.2:
·        Codes and names can be used directly wherever a code list can be used (both Geographic Unit Type Classification and Geographic Unit Classification are sub-types of Code List
·        A Geographic Unit (location) can belong to multiple Geographic Unit Type (geographic levels) with replicating its content
·        A Geographic Unit can version and/or define new units whenever there is a change in name or spatial extent as determined by the user. For example a Metropolitan Area may change only its spatial extent over time and be managed as versions of the same conceptual location; a city may annex additional land, or be renamed. Normally a new version of a Geographic Unit should have some common spatial extent with the old version. This can be described in the Geographic Unit precedes or supersedes using the Spatial Relationship using Spatial Relation Specification (Equals  Disjoint  Intersects  Contains  Touches).
·        Geographic Units can be used to describe points, lines, and/or polygons as well as include centroid information.


Equivalent Content between DDI 3.2 and DDI 4
DDI 3.2 - DDI 4 - Comment

Geographic Structure - Geographic Unit Type Classification - no comment

Geographic Level - Unit Type - Because no specialized information was being gathered a generic Unit Type is used. This allows users to declare any Unit Type as part of geography without requiring that it be of a specific type.

Parent Structure / Geographic Layer Base - Geographic Unit Type Relation Structure - Described as separate hierarchies; can have levels; Spatial relationships can be described

Geographic Level Code - Geographic Unit Type Instance - Codes are assigned when the Unit Type is used by a Geographic Unit Type Classification (see information on contains in Geographic Location)
Primary Component - Geographic Unit Type Relation Structure - Spatial relationships can be described

Geographic Location - Geographic Unit Classification - Inclusion of a Geographic Unit using “contains” allows for the assignment of a code in the same manner as in a code list. Different code sets should be expressed as different geographic unit classifications. Inclusion is by reference so that the described Geographic Unit can be assigned multiple codes without altering the Geographic Unit description

Location Value - Geographic Unit - Rather than grouping with other units of the same unit type, each unit can relate itself to one or more unit types. This allows for a location like Washington, D.C. to act as a State equivalent, County equivalent, and Place in the United States. Provides supersedes and precedes.


Notes:
Purpose:
DDI4 data management description aims to account for the ingestion and production of new data types (registry data, health data, big data, spell data, event data, etc.) and both legacy and new data management services that give shape to these data types in the course of the data lifecycle.  The Data Management View describes the prospective and retrospective use of multiple data management platforms and architectures including (1) ESB (Enterprise Service Bus) and SOA (Service Oriented Architecture); (2) the use of PROCs/Commands in statistical packages like SAS, Stata and R; and now (3) the use of iPaaS (integration Platform as a Service) in public clouds, private clouds and apparatuses as practiced by various ETL (Extract, Transform and Load) platforms.

Use Cases:
Create repeatable processes across a data network. More specifically, document and share the specifications for a demographic and epidemiological surveillance DataPipeline across surveillance sites
Produce a Data Management Plan (DMP) in the form of a DataPipeline so other researchers are able to replicate a study’s results
Document the actual data management in a study as a DataPipeline. This could underpin workflow tools for researchers
Use a DataPipeline description as the input to tools that trace the lineage of data during the data lifecycle of a Study 
Use a DataPipeline description and the GraphML it spawns to create workflow diagrams
Specialize the GLBPM to support the production of a dataset of geotagged tweets from the US where a wave corresponds to a day. Create a DataPipeline that describes in detail how this dataset is produced.
Programmatically create a Data Management View for an Extract, Transform and Load (ETL) platform using the ETL’s authoring environment and the instructions that authors create as input

Target Audiences:
Researchers who are preparing a Data Management Plan (DMP)
Data networks migrating from an Enterprise Service Bus (ESB) / Service Oriented Architecture (SOA) platform to a virtual (cloud-based) or actual integrated Platform as a Service (iPaaS) appliance (e.g. ETLs)
Industry-specific or generic standard groups who wish to integrate fully developed information models with domain-specific business process models
Search engines intent on exposing data lineage within a study

General Documentation:
At one level the Data Management View consists of a data pipeline that traverses a series of business activities from business process models like the GSBPM (Generic Statistical Business Process Model) for the production of statistics and the GLBPM (Generic Longitudinal Business Process Model) for the description of longitudinal studies. At another level the Data Management View decomposes these business processes into a series of workflow steps. At both levels components exchange data.

DataPipeline-
With the Data Management View, the user is able to construct a DataPipeline of BusinessProcesses where each BusinessProcess contains either a simple collection or a structured collection of WorkflowSteps. 
The DataPipeline itself is a simple collection of BusinessProcesses with the next one beginning after the preceding one ends.  
Use the Data Management View and its DataPipeline to traverse a business process model once to describe the data lifecycle of a Study and many times to describe the data lifecycle of a StudySeries.

BusinessProcess-
A BusinessProcess has an AlgorithmOverview, zero or more Preconditions, zero or more Postconditions and one or more StandardModelUsed. 
Note that Preconditions and Postconditions are LogicalRecords. One BusinessProcess creates/updates LogicalRecords as Postconditions. These Postconditions may become the Preconditions of the next BusinessProcess.

Figure 1: The DataPipeline

Note that support for business process models here is not limited to either the GSBPM or the GLBPM that the GSBPM has spawned.

The Generic Statistical Business Process Model (GSBPM) circumscribes a set of business processes that together describe a data lifecycle for building a single wave of national statistics. The Generic Longitudinal Business Process Model (GLBPM) specializes the GSBPM for longitudinal studies. Here each traversal of the GLBPM corresponds to the data lifecycle of a Study in a StudySeries.
Other business process models are more or less based on the GLBPM and the GSBPM. For example, a widely used demographic and epidemiological surveillance business process model specializes the GLBPM data lifecycle to create events, event histories and spells.

Figure 2: Support for Specialization of the GSBPM/GLBPM in DDI4 BusinessProcesses

WorkflowSteps-
The BusinessProcess decomposes into a WorkflowStepSequence.  Alternatively, the BusinessProcess AlgorithmOverview can be used to outline a WorkflowStepSequence. This would be appropriate in situations where only a higher-level description was needed.

Figure 3: Example AlgorithmOverview

The WorkflowStepSequence may be either a Simple Collection or a Structured Collection of WorkflowSteps. In a simple collection of WorkflowSteps, successive pairs in the sequence participate in a before/after relationship. In a structured collection, however, relationships among the WorkflowSteps can be complicated: a sequence may have multiple starting points and multiple end points. Here before and after relationships can be indeterminate, depending on a platform and its technology stack.
The structured collection of WorkflowSteps is called a WorkflowStepRelationStructure. Like other structured collections in DDI4, a WorkflowStepRelationStructure is specified in a graph form as an unordered list of adjacency lists where for each vertex we specify an array of adjacent vertices:

Figure 4: The DDI4 RelationStructure

Here each vertex and the array of its adjacencies are WorkflowSteps.

Figure 5: An Example WorkflowRelationStructure (fragment)

The Structured Collection in DDI4 is the successor to GSIM’s Node Set. Using graph representation, DDI4 RelationStructures, like the WorkflowStepRelationStructure, are easy to visualize and annotate using open source tools:

Figure 6: Graph Rendering of Example DDI4 WorkflowRelationStructure


Notes:
Purpose
Use the DataDescriptionView to describe a collection of LogicalRecords by themselves or along with their PhysicalRecordSegments in a Study and/or a StudySeries.

Recall that a LogicalRecord is a record definition and a PhysicalRecordSegment describes the physical storage arrangement of a LogicalRecord.

Think of the collection of LogicalRecords and their PhysicalRecordSegment counterparts in a Study as a succession of states that are the products of one or more data transforming processes. In the DataDescriptionView we just describe products in this succession, not the processes through which these products are created.

In this succession operational data may be transformed into analysis-ready data and then analytical data in a series of steps. The DataDescriptionView captures the products from one, some or all of these interim steps. 

Products can include “skinny” and “fat” data structures; relational datastores; star schemas (data warehouses); structured collections of instance variables that take the form of objects, not tables; data cubes (not supported in the prototype) and so forth.

Instead of using the DataDescriptionView, use the DataManagementView for creating data descriptions that are both process-centered and product-centered. 


Use Cases
Construct a catalog of data records produced across the life of a study. Order the records by category: initial or submission records, interim or archival records, analysis or dissemination records
Expose variables in LogicalRecords and their PhysicalRecordSegments so they are searchable by: 
study, 
structural role(s) (identifier, measure and attribute) in one or more viewpoints and 
their functional role(s) as specified in one or more external controlled vocabularies
Specify the information needed for a Submission Information Package (SIP), an Archival Information Package (AIP) or a Dissemination Information Package (DIP) when the data is a CSV file
Support the description of a CSV file that uses a list datatype to, for example, report health measures that consist of compound elements like blood pressure
Support the description of medical information as specified both by Fast Healthcare Interoperability Resources (FHIR) and the Clinical Information Modeling openEHR Initiative (CIMI). With respect to FHIR, support, for example, the Observation and DiagnosticReport resources. With respect to CIMI, support, for example, the various observation archetypes including the newborn Apgar score, blood pressure, body mass index, physical examination findings, etc.
Support the description of a NoSQL key/value store where the key is either a simple collection of one or more identifiers or a structured (hierarchical) collection and the value can be text, video, sound or a JSON document

Target Audiences
Digital archivists
Search engines intent on exposing data lineage within a study
Researchers who are preparing a Data Management Plan (DMP)
Governments intent on exposing in a single datastore registries that include demographic data and health information in order to promote various types of research

Restricted Classes
Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.
Concept is extended by ConceptualVariable, RepresentedVariable, UnitType and Universe.
ExternalMaterial is extended by ExternalAid.


Notes:
Purpose:
To review the conceptual concept structures and to manage concept systems (other than statistical classifications). The coverage go down to a RepresentedVariable. InstanceVariable has been included in the collection for use as a member of a VariableCollection. However it does not go into the detailed content of an InstanceVariable.

Restriction: 
InstanceVariable has been included for the sole purpose of membership in a VariableCollection. The classes required to completely describe an InstanceVariable have not been included.


Notes:
Purpose:
The ControlledVocabulary view is intended to allow for the structured description of a vocabulary in DDI4. A vocabulary can be described as a simple set of terms and definitions, or a set of terms and definitions with a structure such as a hierarchy.

Use Cases:
A DDI4 ExternalControlledVocabularyEntry could reference a vocabulary entry described in DDI4. This would allow processing by software able to interpret DDI4. 
DDI4 has a set of controlled vocabularies https://www.ddialliance.org/controlled-vocabularies, currently described in Genericode. These could be published in DDI4 as well.
Vocabularies having a structure more complex than a simple table.

Target Audiences:
DDI4 user communities.

Restricted Classes:
Concept is extended by Category, ConceptualVariable, RepresentedVariable, InstanceVariable, Population, UnitType and Universe
ExternalMaterial is extended by ExternalAid

General Documentation:
The representation of a controlled vocabulary in DDI4 consists of four classes:
ControlledVocabulary – The structured collection of vocabulary entries
VocabularyEntry – Assigns a definition to a term
VocabularyRelationStructure – Allows for the description of a complex structure among the terms, such as a hierarchy
ExternalMaterial – Points to material outside of a current DDI4 instance.

The ControlledVocabulary uses a set of  VocabularyEntryIndicators to delineate the entries in the vocabulary. These may be ordered with an index.
The VocabularyRelationStructure uses a set of VocabularyEntryRelations to describe relationships among the vocabulary entries. A "source" entry might have a relationship to several "target" entries, for example one entry (e.g. Vehicle) might be a more general term for several other terms (e.g. car, bike, skateboard). This relationship may be described with a semantic, a relationSpecification (e.g. GeneralSpecific), and whether the relation is total or not. 
The diagram below shows all inherited properties for the vocabulary classes.
[image to be inserted here]


Notes:
Purpose:
The DDI4 CustomMetadataView allows for the definition of a set of keys and their interrelationships. This structure can be shared and reused by a community. These keys can be used in key-value pairs to enter metadata that is more actionable than would be if an uncontrolled set of keys were employed. They could also be used in a NoSQL key/value store.

Use Cases:
User defined structures for notes. This corresponds to the UserAttributePair in DDI3.2, but allows for additional specification of a structure for the keys and a datatype and cardinalities for the values.
User defined structures for specifying the location of parts of qualitative objects. The example below shows the location of words or sentences from material arranged into volume, chapter, sentence and word
User defined structures for specifying the location of  parts of cited materials

Target Audiences:
Users of DDI4 needing structured extensions to be shared by their community. A user community, for example, could share the structure for locating material by volume, chapter, sentence and word.

Restricted Classes:
The list below displays each class in the View that is extended by classes not in the view.
Concept is extended by ConceptualVariable and Population.
ExternalMaterial is extended by ExternalAid.
Code is extended by ClassificationItem.
CodeList is extended by GeographicUnitClassification, GeographicUnitTypeClassification and StatisticalClassification.

General Documentation:
The keys and their interrelationships are defined in a CustomStructure which is a collection of CustomItems. Each CustomItem defines a key, giving it a cardinality and associating it with a RepresentedVariable and a ValueDomain. The set of CustomItems can be arranged into a structure, for example a hierarchy, by a CustomItemRelationStructure.
[image to be inserted]
Once the structure is defined, it can be used in a CustomInstance. This is a collection of CustomValues. A CustomValue contains a key-value pair where the key corresponds to a previously defined CustomItem. A CustomValue also may be associated with an InstanceVariable.  The CustomValues may also be structured by a CustomValueRelationStructure.
[image to be inserted]


