# 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. A recommended role for contributors is the CASRAI Contributor Roles Vocabulary (CRediT) http://dictionary.casrai.org/Contributor_Roles


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:
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. Strongly recommend the use of language codes supported by xs:language which include the 2 and 3 character and extended structures defined by RFC4646 or its successors.


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:
An abstract (description) 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:
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:
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:
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:
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:
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:
The type of relationship between the two CustomValues. 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:
Explanation of the reasons for relating the external material to the identified object. Supports the use of multiple languages and structured text.


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 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.


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 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:
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:
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.


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:
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:
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:
The following xhtml tags are available for use in Content: address, blockquote, pre, h1, h2, h3, h4, h5, h6, hr, div, p, a, abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var, b, big, i, small, sub, sup, tt, br, span, dl, dt, dd, ol, ul, li, table, caption, thead, tfoot, tbody, colgroup, col, tr, th, and td. They should be used with the xhtml namespace prefix, i.e., xhtmdiv. See DDI Technical Manual Part I for additional details.


Notes:
Indicates whether content is translatable (true) or not (false).


Notes:
List the language or language codes in a space delimited array. The language original may or may not be provided in this bundle of language specific strings.


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:
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:
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:
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:
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:
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:
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:
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:
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:
A display label for the MemberCorrespondence. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.


Notes:
The name of the software package, including its producer.


Notes:
A coded value from a controlled vocabulary, describing the software package.


Notes:
The version of the software package. Defaults to '1.0'.


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


Notes:
Supported date of the software package with, at minimum, a release date if known.


Notes:
Identifies the functions handled by this software. Repeat for multiple functions. It may be advisable to note only those functions used in the specific usage of the software.


Notes:
Language (human language) of the software package. 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:
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:
Identifies the type of sequence to use. Values include InOrderOfAppearance, Random, Rotate, and Other.


Notes:
Information on the command used to generate an alternative means of determining sequence changes. If used, the ItemSequenceType should be "Other".


Notes:
This key (sometimes referred to as a name) expressed as a string. Supports the use of an external controlled vocabulary which is the recommended approach.


Notes:
The value assigned to the named Key expressed as a string. Supports the use of an external controlled vocabulary.


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:
The value of the statistic expressed as a decimal


Notes:
A descriptive term for the type of relation


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:
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:
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:
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:
The actual content of this value as a string


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 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:
Specify the namespace which the prefix represents.


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:
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:
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:
Controlled Vocabulary to specify whether the relation is total, partial or unknown.


Notes:
Controlled vocabulary for the ImmediatePrecedenceRelation semantics. It should contain, at least, the following: Parent_Of, Child_Of, Next, Previous, Instance_Of, Temporal_Meets.


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


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:
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:
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:
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 contains in Symmetric Relation for mapping similar concepts.


Notes:
An Instance Variable can take different roles, e.g. Identifier, Measure and Attribute. Note that DataStructure takes care of the ordering of Identifiers.


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


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:
The 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 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:
Optionally an act has an instructionalCommand expressed as Command Code. Acts are abstract so, in addition to an instructionalCommand, we can expect other specializations or instructions to be provided by the class which extends it.


Notes:
An optional high level overview or summary of the algorithm for coding


Notes:
Provides a high level overview or summary of the design of the coding.


Notes:
A linguistic signifier for the coding method.


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


Notes:
Explanation of the reasons some decision was made or why the coding method 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 the coding method.


Notes:
The ordinal number of the object in the list


Notes:
Defines the type of relationship by choosing a complex datatype defining reflexivity, symmmetry, transitivity, and  totality. Allows for the specification of a semantic


Notes:
A reference to a member of this singleton (a bag with just one member


Notes:
The type of strict order relation - THis allows the entry of a semantic while fixing the values of reflexivity, symmetry, transitivity and totality


Notes:
A reference to a member of the list, ordered by strictOrderType


Notes:
Sets the array base for the list (that is, whether the first value is in position 0 or 1).


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:
Specialization of contains in Asymmetric Relation for Information Flows.


Notes:
Specifies where the service can be accessed.


Notes:
Position of the item in an ordered list. xs:decimal is used to allow later insertion of an item into an existing list


Notes:
If false hierarchical collection is organized vertically


Notes:
A high level overview or summary of the algorithm for defining segments


Notes:
Provides a high level overview or summary of the design of segment definition.


Notes:
A linguistic signifier for the segment definition method.


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


Notes:
Explanation of the reasons some decision was made or why the segment definition method 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 the segment definition method.


Notes:
A high level summary of this process of defining segments


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:
Specification of a code which relates to an area of coverage of the standard. Supports the use of an external controlled vocabulary.


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


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:
Identifies the evaluator and specifies the role of the evaluator using an external controlled vocabulary.


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:
A perceivable object used to denote a signified.


Notes:
Perceivable object in the extension of the signifier.


Notes:
The type of clip, preferably drawn from a controlled vocabulary.


Notes:
The set of parameters describing the polygon, square, etc


Notes:
Points to the descriptive term expressed as a codeValue along with related information


Notes:
Points to parameters using start line and character withing line and end line and character within that line


Notes:
Points to parameter pairs using start character (from the beginning of the document) and end character


Notes:
A description of the endpoint to be queried by the SPARQL Query


Notes:
The type of the database. An example might be MySQL


Notes:
The version of the database. For MySQl an example might be 5.7


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


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:
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:
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:
Supports the use of an External Controlled Vocabulary to describe or define the algorithm.


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:
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:
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:
Intensional definition of the order criteria (e.g. alphabetical, numerical, increasing, decreasing, etc.)


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:
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. The default value is ".". 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 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. The default value is null. 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:
Each CustomItemParentChipdPair defines the ordering between two CustomItems.


Notes:
Each pair describes the relationship specified by a predicate between a source and a target.


Notes:
Contains a set of CustomItemSequencePairs which together define a sequence among a set of CustomItems.


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


Notes:
Each CustomValueParentChipdPair defines the ordering between two CustomValues.


Notes:
Each pair describes the relationship specified by a predicate between a source and a target


Notes:
Contains a set of CustomValueSequencePairs which together define a sequence among a set of CustomValues.


Notes:
An explanation (definition) of the value


Notes:
Enumerates the VocabularyParentChildPairs which taken together defines the hierarchy for the vocabulary


Notes:
Enumerates the set of VocabularySequencePairs, each of which defines the order within the pair.


Notes:
Pairs of Process Steps in the temporal relation.


Notes:
An execution pair conforms to one of three patterns. In one case the pairs are siblings in a sequence. In a second case a binding might obtain between the control construct that parents the sequence and the sequence. In a third case a binding might obtain between the last element of a sequence and the output of the construct construct that has parented the sequence


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


Notes:
Pairs of Process Steps in the temporal relation


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:
Type of object the parameter accepts (DDI object, Datatype, etc.). If not present the parameter is untyped.


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:
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:
Specifies the type of note. Supports the use of a controlled vocabulary.


Notes:
Reference to one or more identifiable objects which the note is related to.


Notes:
The person or agency responsible for adding the note.


Notes:
A brief label or heading for the note contents.


Notes:
The content of the note. Note should contain content except when it is a production flag that is fully explained by its "type". If the note provides system specific information in a structured way using XHTML formating, DDI strongly recommends the use of local extensions or the Key/Value pair structure in ProprietaryInfo whenever possible.


Notes:
A set of actions related to the object as described by a set of name-value pairs. This would commonly be used in a case where additional information needs to be recorded regarding the content of a new element or attribute that has not yet been added to the schema, for example when a bug for a missing object has been filed and the user wishes to record the content prior to correction in the schema. Ideally this should be handled by local extensions of the schema as described in Part 2 of the formal documentation. However, the structure in Note allows for an unanticipated need for an extension at run time by providing a means of capturing system specific information in a structured way.


Notes:
Controlled vocabulary for the AcyclicPrecedenceRelationsemantics. It should contain, at least, the following: Tangential_Proper_Part and Temporal_Overlaps


Notes:
Controlled Vocabulary to specify whether the relation is reflexive, anti-reflexive, neither or unknown.


Notes:
Controlled Vocabulary to specify whether the relation is symmetric, anti-symmetric, asymmetric or unknown.


Notes:
Controlled Vocabulary to specify whether the relation is transitive, anti-transitive, neither or unknown.


Notes:
Controlled vocabulary for the equivalence relation semantics. It should contain, at least, the following: Same_As, Similar_To, Congruent_To, Compatible_With, Equidistant_From, Temporal_Equals.


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:
Controlled vocabulary for the strict order relation semantics. It should contain, at least, the following: Descendant_Of, Strict_Part_Of, Less_Than, Strict_Subtype_Of, Predecessor_Of, Successor_Of, Temporal_Precedes, Temporal_Finishes, Temporal_Contains and Temporal_Starts


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.


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:
Date when the current version of the Classification Index was released.


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


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


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.


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


Notes:
ClassificationSeries can be designed in a specific context.


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:
The statistical office or other authority, which created and maintains the StatisticalClassification (s) related to the ClassificationSeries. A ClassificationSeries may have several owners.


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


Notes:
The value as expressed in the data file.


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:
Preceding-following pair of entries in the sequence.


Notes:
Parent-child pair of Nodes in the hierarchy.


Notes:
Part-whole pair of nodes in the relation.


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 currently valid.


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. Repeat for each langauge.


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.


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:
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:
The data types that are recommended for use with this domain


Notes:
Location of external resource providing information about the vocabulary.


Notes:
Information for the user regarding the reasons for use of the vocabulary and appropriate usage constraints.


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:
Specification of the type of Signification


Notes:
Layout ordered pairs describing the Instance Variable sequence.


Notes:
Correspondences between Instance Variables of different Logical Record Layout. Realization of contains in Symmetric Relation.


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:
Define the specific nature of the relationship if not captured within the semantics of the specific relation type such as simple similarity or Parent/Child 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:
Pair of Agents whose relationship is hierarchical in nature.


Notes:
The agent responsible for maintaining the Agent Listing


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


Notes:
Explanation of the intent of creating and maintaining this registry. Supports the use of multiple languages and structured text.


Notes:
Explanation of the ways in which the contents of the registry, Agent Listing and Agent Relationships can be employed. Supports the use of multiple languages and structured text.


Notes:
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 agent who maintains the relationship information


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


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


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:
Provides annotation information on the object to support citation and crediting of the creator(s) of the object.


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:
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:
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.


# 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:
A set of access information for a Machine including URI, mime type, and physical location


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:
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.


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:
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.


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:
Used to define a pair of agents in a hierarchical structure where the source is the parent and the target is the child.


Note:
||Definition
============
Used to define a pair of agents in a hierarchical structure where the source is the parent and the target is the child. |||

||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)|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Persistent identifier for a researcher using a system like ORCID


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:
Describes simple pair of similar agents of any type (i.e. Organization, Individual, Machine, etc.). Uses the pattern for an UnorderedPair.


Note:
||Definition
============
Describes simple pair of similar agents of any type (i.e. Organization, Individual, Machine, etc.). Uses the pattern for an UnorderedPair.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


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


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:
A generic date type for use in Annotation which provides that standard date structure plus a property to define the date type (Publication date,  Accepted date, Copyrighted date, Submitted date, etc.). Equivalent of http://purl.org/dc/elements/1.1/date where the type of date may identify the Dublin Core refinement term.


Note:
||Definition
============
A generic date type for use in Annotation which provides that standard date structure plus a property to define the date type (Publication date,  Accepted date, Copyrighted date, Submitted date, etc.). Equivalent of http://purl.org/dc/elements/1.1/date where the type of date may identify the Dublin Core refinement term.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


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


Note:
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.


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:
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.


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:
Mapping between WorkflowParameters of Workflow Steps representing the flow of information within a Workflow.


Note:
||Definition
============
Mapping between WorkflowParameters of Workflow Steps representing the flow of information within a Workflow.|||

||Examples
==========
Binding the output of a question to the input of a generation instruction. Question A has an output X. Generation Instruction has an input Y used in the recode instruction. Binding defines the content of input Y to be whatever is provided by output X for use in the calculation of the recode.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:BindingType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Specification of the character offset for the beginning and end of the segment, or beginning and length.


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:
Provides the following information on the command. The content of the command and the programming language used.


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:
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.


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:
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.


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:
Specifies the Parent Concept and Child Concept in the Concept Parent Child Relationship.


Note:
||Definition
============
Specifies the Parent Concept and Child Concept in the Concept Parent Child Relationship.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Identifies the concept defining the Whole and the concept defining the Part.


Note:
||Definition
============
Identifies the concept defining the Whole and the concept defining the Part.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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).


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).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:ConditionalTextType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
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.


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:
A parent-child relationship between a pair of CustomItems.


Note:
Defines an 'order' relationship with a predicate between two CustomItems (a triple).


Note:
||Definition
============
Defines an 'order' relationship with a predicate between two CustomItems (a triple).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines a simple ordering between two CustomItems - one precedes the other.


Note:
||Definition
============
Defines a simple ordering between two CustomItems - one precedes the other.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A parent-child relationship between a pair of CustomValues.


Note:
Relationship specification between this item and the item to which it is related. Provides a reference to any identifiable object and a description of the relationship.


Note:
||Definition
============
Relationship specification between this item and the item to which it is related. Provides a reference to any identifiable object and a description of the relationship.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:RelationshipType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A structured display label. Label provides display content of a fully human readable display for the identification of the object.


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:
Describes a bounding value for a number range expressed as an xs:double.


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:
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.).


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:DynamicTextType|||

||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:
A reference to an image, with a description of its properties and type.


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:
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.


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 Coordinates provides the information required to define it.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:ImageAreaType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Indexing order, defined either by predecessor-successor pairs or by a criteria (e.g. alphabetical, in code order, etc.)


Note:
||Definition
============
Indexing order, defined either by predecessor-successor pairs or by a criteria (e.g. alphabetical, in code order, etc.)|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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 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/location 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, and translationDate.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:StringType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Supports the optional use of XHTML formatting tags within the string structure. XHTML tag content is controlled by the schema, see http://www.w3.org/1999/xhtml/ for a detailed list of available tags. Language of the string is defined by the attribute language. The content can be identified as translated (isTranslated), subject to translation (isTranslatable), the result of translation from one or more languages (translationSourceLanguages), and carry an indication whether or not it should be treated as plain text (isPlain).


Note:
||Definition
============
Supports the optional use of XHTML formatting tags within the string structure. XHTML tag content is controlled by the schema, see http://www.w3.org/1999/xhtml/ for a detailed list of available tags. Language of the string is defined by the attribute language. The content can be identified as translated (isTranslated), subject to translation (isTranslatable), the result of translation from one or more languages (translationSourceLanguages), and carry an indication whether or not it should be treated as plain text (isPlain).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:ContentType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The pair of Instance Variables in a Record Layout which are being placed in a logical sequence.


Note:
||Definition
============
The pair of Instance Variables in a Record Layout which are being placed in a logical sequence.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


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


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:
Literal (static) text to be used in the instrument using the StructuredString structure plus an attribute allowing for the specification of white space to be preserved.


Note:
||Definition
============
Literal (static) text to be used in the instrument using the StructuredString structure plus an attribute allowing for the specification of white space to be preserved.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:LiteralTextType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
Name of the location using the DDI Name structure and the ability to add an effective date.


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
============
Relationship between Nodes in NodeSets.|||

||Examples
==========
|||

||Explanatory notes
===================
A Map is the pairing of similar categories in a correspondence between Node Sets. Each Node in the Map belongs to a different set. The collection of maps for all the Nodes in corresponding Node Sets 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:
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. 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.


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. 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.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:NameType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Parent-child pair of nodes in a Node Hierarchy.


Note:
Part-whole pair of nodes in a Node Partitive Relation


Note:
Used to preserve an historical date, formatted in a non-ISO fashion.


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:
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.


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:
Describes a bounding value for a number range expressed as an xs:demical.


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
============
The pair of Value Mappings in a Physical Layout which are being placed in a sequence.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A geographic point consisting of an X and Y coordinate. Each coordinate value is expressed separately providing its value and format.


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:
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. A geographic time designating the time period that the shape is valid should be included. If the date range is unknown use a SingleDate indicating a date that the shape was known to be valid.


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. A geographic time designating the time period that the shape is valid should be included. If the date range is unknown use a SingleDate indicating a date that the shape was known to be valid.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:PolygonType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
Indicates the range of items expressed as a string, such as an alphabetic range.


Note:
||Definition
============
Indicates the range of items expressed as a string, such as an alphabetic range.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:RangeType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines an 'order' relationship with a predicate between two CustomValues (a triple)


Note:
||Definition
============
Defines an 'order' relationship with a predicate between two CustomValues (a triple)|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines a simple ordering between two CustomValuess - one precedes the other.


Note:
||Definition
============
Defines a simple ordering between two CustomValuess - one precedes the other.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
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.


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:
An additional condition and resulting step to take if the condition in the parent IfThenElse is false. It cannot exist without a parent IfThenElse.


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:
An e-mail address which conforms to the internet format (RFC 822) including its type and time period for which it is valid.


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:
Allows for unstructured content which may be taken from an externally maintained as an entry in a 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.


Note:
||Definition
============
Allows for unstructured content which may be taken from an externally maintained as an entry in a 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:
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.


Note:
Relation between Instance Variables in different Logical Record Layouts.


Note:
||Definition
============
Relation between Instance Variables in different Logical Record Layouts.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:InternationalIdentifierType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
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/location 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, and translationDate.


Note:
The result of applying a particular Capture in an Instrument to some Unit.


Note:
||Definition
============
The result of applying a particular Capture in an Instrument to some Unit.|||

||Examples
==========
1) The event of receiving a response to a survey question (the Capture) in a questionnaire (the Instrument) that is put to a respondent (the Unit).
2) The recording of a blood pressure after a procedure in an experiment.|||

||Explanatory notes
===================
See background paper at:
https://ddi-alliance.atlassian.net/wiki/download/attachments/491697/Linking%20Instrument%20Observation%20Datum%20and%20Variables%20v3.docx?api=v2|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Ordered pair of Process Steps in a Temporal Interval Relation.


Note:
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.


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:
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.


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.
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The pair of Value Mappings in a Physical Layout which are being placed in a sequence.


Note:
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. For example, 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 "/". Note that if needed you may use Start and Duration or Duration and End. These options may not be recognizable by all systems.


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. For example, 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 "/". Note that if needed you may use Start and Duration or Duration and End. These options may not be recognizable by all systems.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:ReferenceDateType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Provides a means of identifying a related resource and provides the typeOfRelationship. Makes use of a controlled vocabulary for typing the relationship. Standard usage may include: describesDate, isDescribedBy,  isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires, etc.


Note:
||Definition
============
Provides a means of identifying a related resource and provides the typeOfRelationship. Makes use of a controlled vocabulary for typing the relationship. Standard usage may include: describesDate, isDescribedBy,  isFormatOf, isPartOf, isReferencedBy, isReplacedBy, isRequiredBy, isVersionOf, references, replaces, requires, etc.

|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
A reference to a concept with similar meaning and a description of their differences. The similar concept structure allows specification of similar concepts to address cases where confusion may affect the appropriate use of the concept.


Note:
||Definition
============
A reference to a concept with similar meaning and a description of their differences. The similar concept structure allows specification of similar concepts to address cases where confusion may affect the appropriate use of the concept.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
c:SimilarConceptType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Describes a specific software package, which may be commercially available or custom-made.


Note:
||Definition
============
Describes a specific software package, which may be commercially available or custom-made.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:SoftwareType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
Describes the ordering of items when not otherwise indicated. There are a set number of values for ItemSequenceType, but also a provision for describing an alternate ordering using a command language.


Note:
||Definition
============
Describes the ordering of items when not otherwise indicated. There are a set number of values for ItemSequenceType, but also a provision for describing an alternate ordering using a command language.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A basic data representation for computing systems and applications expressed as a tuple (attribute key, value). Attribute keys may or may not be unique.


Note:
||Definition
============
A basic data representation for computing systems and applications expressed as a tuple (attribute key, value). Attribute keys may or may not be unique.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:StandardKeyValuePairType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The value of the statistics and whether it is weighted and/or includes missing values.


Note:
||Definition
============
The value of the statistics and whether it is weighted and/or includes missing values.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
pi:StatisticType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A datatype defining the properties for a strict order relation


Note:
Specifies details of target sample size, percentage, type, and universe


Note:
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.


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:
Unordered pair of Process Steps in a Temporal Interval Relation.


Note:
The Value expressed as an xs:string with the ability to preserve whitespace if critical to the understanding of the content.


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:
Describes the type and length of the video segment.


Note:
a parent-child relationship between two vocabularyEntries


Note:
Defines a simple ordering between two VocabularyEntry(s) one precedes the other.


Note:
The static portion of the text expressed as a StructuredString with the ability to preserve whitespace if critical to the understanding of the content.


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:
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.


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.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:TextContentType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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
============
Defines a simple ordering between two VocabularyEntry(s) one precedes the other.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A web site (normally a URL) with information on type of site, privacy flag, and effective dates.


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:
Maps a specified prefix to a namespace. For each XML namespace used in the profile's XPath expressions, the XML namespaces must have their prefix specified using this element.


Note:
||Definition
============
Maps a specified prefix to a namespace. For each XML namespace used in the profile's XPath expressions, the XML namespaces must have their prefix specified using this element.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
pr:XMLPrefixMapType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Concept whose role is to define and measure a characteristic.


Note:
||Definition
============
A Concept whose role is to define and measure a characteristic.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
l:CategoryType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Unit of thought differentiated by characteristics [GSIM 1.1]


Note:
||Definition
============
Unit of thought differentiated by characteristics [GSIM 1.1]|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
c:ConceptType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Concept|||


Note:
Parent-child specialization of OrderRelation between Concepts within a ConceptSystem.


Note:
||Definition
============
Parent-child specialization of OrderRelation between Concepts within a ConceptSystem.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Part-whole specialization of OrderRelation between Concepts within a ConceptSystem.


Note:
||Definition
============
Part-whole specialization of OrderRelation between Concepts within a ConceptSystem.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A set of Concepts structured by the relations among them. [GSIM 1.1]


Note:
||Definition
============
A set of Concepts structured by the relations among them. [GSIM 1.1]|||

||Examples
==========
Here are 2 examples 1) Concept of Sex: Male, Female, Other 2) ISIC (the list is too long to write down)|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
c:ConceptSchemeType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Concept System|||


Note:
Relationship between Concept Systems used to group similarity mappings between their Concepts.


Note:
||Definition
============
Relationship between Concept Systems used to group similarity mappings between their Concepts.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Set of Concepts, both sentinel and substantive, that can be described by either enumeration or by an expression.


Note:
||Definition
============
Set of Concepts, both sentinel and substantive, that can be described by either enumeration or by an expression.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The use of a Concept as a characteristic of a Universe intended to be measured [GSIM 1.1]


Note:
||Definition
============
The use of a Concept as a characteristic of a Universe intended to be measured [GSIM 1.1]|||

||Examples
==========
Here are 3 examples - 
1. Sex of person
2. Number of employees 
3. Value of endowment|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
c:ConceptualVariableType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Variable|||


Note:
The use of a Represented Variable within a Data Set.


Note:
||Definition
============
The use of a Represented Variable within a Data Set.  |||

||Examples
==========
The InstanceVariable is to describe actual instances of data that have been collected.  Here are 3 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.|||

||Explanatory notes
===================
It can inherit information from Represented Variable (which again can inherit from Conceptual Variable)|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Instance Variable|||


Note:
Set of specific units (people, entities, objects, events) with specification of time and geography.


Note:
||Definition
============
Set of specific units (people, entities, objects, events) with specification of time and geography.|||

||Examples
==========
Here are three 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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Population|||


Note:
A combination of a characteristic of a universe to be measured and how that measure will be represented.


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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Description or list of possible sentinel concepts , e.g. missing values.


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:
Set of valid Concepts. The Concepts can be described by either enumeration or by an expression.


Note:
||Definition
============
Set of valid Concepts. The Concepts can be described by either enumeration or by an expression.|||

||Examples
==========
|||

||Explanatory notes
===================
[GSIM 1.1]|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Conceptual Domain|||


Note:
The object of interest in a process step related to the collection or use of observational data.


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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Unit|||


Note:
A Unit Type is a class of objects of interest.


Note:
||Definition
============
A Unit Type is a class of objects of interest.|||

||Examples
==========
|||

||Explanatory notes
===================
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:
A defined class of people, entities, events, or objects, with no specification of time and geography, contextualizing a Unit Type


Note:
||Definition
============
A defined class of people, entities, events, or objects, with no specification of time and geography, contextualizing a Unit Type|||

||Examples
==========
Here are three examples:
1. Canadian adults (not limited to those residing in Canada)
2. Computer companies 
3. Universities|||

||Explanatory notes
===================
If the Universe consist 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:
Attaches a Category to a segment of a PhysicalResource


Note:
Attaches a Code to a segment of a PhysicalResource


Note:
Attaches a Memo to a segment of a PhysicalResource


Note:
A CustomStructure designed for AnalyticMetadata. Defines a set of CustomItems each defining a  valid key and and associated value domains along with the cardinality of each. The CustomItems are referenced by CustomValues which, in turn contain the actual AnalyticMetadata key,value pairs.


Note:
||Definition
============
A CustomStructure designed for AnalyticMetadata. Defines a set of CustomItems each defining a  valid key and and associated value domains along with the cardinality of each. The CustomItems are referenced by CustomValues which, in turn contain the actual AnalyticMetadata key,value pairs.|||

||Examples
==========
Contains two CustomItems:
one labeled "Associated gender" with a key of "gender' and values of m and f
the other labeled "speaker age" with integer values between 0 and 135|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Collection of AnalyticMetadatum produced by a common Process.


Note:
||Definition
============
A Collection of AnalyticMetadatum produced by a common Process.|||

||Examples
==========
All of the codes assigned on segments of a LogicalResource. All of the memos assigned to speakers in a PhysicalResource.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An Abstract class for the various types of metadata that can be attached to a PhysicalSegment (and potentially by inference to a LogicalSegment)


Note:
||Definition
============
An Abstract class for the various types of metadata that can be attached to a PhysicalSegment (and potentially by inference to a LogicalSegment) |||

||Examples
==========
A code attached to a segment of text in a Qualitative Data Analysis package. A speaker name attached to a segment of video.|||

||Explanatory notes
===================
Note that this could potentially be an input or output from a process|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The Method used to attach AnalyticMetadata to segments.


Note:
A piece of some resource independent of a physical representation. Multiple PhysicalSegments can correspond to the same LogicalSegment.


Note:
||Definition
============
A piece of some resource independent of a physical representation. Multiple PhysicalSegments can correspond to the same LogicalSegment.|||

||Examples
==========
One person's response to a question in a focus group. Three physical representations of the focus group exist. Audio and video recordings were used to make a transcript. The response is delineated in each medium and all three PhysicalSegments correspond to one LogicalSegment.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Collection of LogicalSegments defined on some Logical Resource.


Note:
||Definition
============
A Collection of LogicalSegments defined on some Logical Resource.|||

||Examples
==========
All of the speaker utterances in a conversation independent of the recording medium.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The set of pairs defining the relations between the physical resources in a PhysicalDataCollection


Note:
||Definition
============
The set of pairs defining the relations between the physical resources in a PhysicalDataCollection|||

||Examples
==========
Chapter 1 is stored as two pdf files. One relation could define the hierarchy (chapters) and another the sequence within the hierarchy (parts 1 and 2 of chapter 1).

Equivalence relationships could show alternate versions of a chapter.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Collection of physical resources (DataStores). Logical resources may be represented in multiple physical instances in multiple, formats and media.


Note:
||Definition
============
A Collection of physical resources (DataStores). Logical resources may be represented in multiple physical instances in multiple, formats and media. |||

||Examples
==========
A document stored as a pdf, a Word processing program file, and a TEI instance.

A dataset stored as a CSV, and an R binary file |||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
The Method used to attach AnalyticMetadata to segments.|||

||Examples
==========
Entering a code or a memo for a segment in a qualitative data analysis package. Attaching a category to a segment of video with custom software.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An AnalyticMetadatum which is not a Code, Category or memo - these all have defined structures. Instead this uses the custom metadata facility to allow for a predefined set of key,value pairs to be used. These key,value pairs are defined with an AnalyticMetadataCustomStructure


Note:
||Definition
============
An AnalyticMetadatum which is not a Code, Category or memo - these all have defined structures. Instead this uses the custom metadata facility to allow for a predefined set of key,value pairs to be used. These key,value pairs are defined with an AnalyticMetadataCustomStructure |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A grouping of Logical Resources. This could be encoded as text documents, videos, audio recordings, and potentially quantitative data.


Note:
||Definition
============
A grouping of Logical Resources. This could be encoded as text documents, videos, audio recordings, and potentially quantitative data.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A LogicalResource represents some data object either qualitative or quantitative independent of its physical manifestation. Multiple DataStores might encode a single LogicalResource, possibly in different media.


Note:
||Definition
============
A LogicalResource represents some data object either qualitative or quantitative independent of its physical manifestation. Multiple DataStores might encode a single LogicalResource, possibly in different media.|||

||Examples
==========
An interview recorded in video and audio and then transcribed into a text file.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An OrderRelation specifying the order of Logical Resources in a Collection


Note:
||Definition
============
An OrderRelation specifying the order of Logical Resources in a Collection|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
A physical segment of a DataStore. |||

||Examples
==========
A paragraph of a document, the whole document, a 10 second slice of an audio file.|||

||Explanatory notes
===================
Segments are described on the physical representations (DataStore) of some LogicalResouce. Physical segments in different DataStores may correspond to the same LogicalSegment.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines relations among PhysicalSegments (e.g. hierarchy, sequence, equivalence). Multiple PhysicalSegments might encode a LogicalSegment. THis allows for the specification of how those multiple parts fit together.


Note:
||Definition
============
Defines relations among PhysicalSegments (e.g. hierarchy, sequence, equivalence). Multiple PhysicalSegments might encode a LogicalSegment. THis allows for the specification of how those multiple parts fit together.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Collection of PhysicalSegments. One or more ProcessSteps delineate the segments. The same or other ProcessSteps may assign AnalyticMetadata to each PhysicalSegment or its corresponding LogicalSegment.


Note:
||Definition
============
A Collection of PhysicalSegments. One or more ProcessSteps delineate the segments. The same or other ProcessSteps may assign AnalyticMetadata to each PhysicalSegment or its corresponding LogicalSegment.|||

||Examples
==========
The set of PhysicalSegments in a transcript of an interviewer where the speaker was male and loud.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An OrderRelation defining the order of LogicalResourceSegments. Note that segments may overlap. Segments from some logical resources may be linear and Allen's interval algebra may apply. In other cases more general spatial relations may apply as in the Region Connection Calculus https://en.wikipedia.org/wiki/Region_connection_calculus


Note:
||Definition
============
An OrderRelation defining the order of LogicalResourceSegments. Note that segments may overlap. Segments from some logical resources may be linear and Allen's interval algebra may apply. In other cases more general spatial relations may apply as in the Region Connection Calculus https://en.wikipedia.org/wiki/Region_connection_calculus |||

||Examples
==========
Segment 1 "meets" Segment 2  (1 comes before 2 with no overlap and nothing between) |||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The ProcessStep assigning AnalyticMetadata to LogicalSegments


Note:
||Definition
============
The ProcessStep assigning AnalyticMetadata to LogicalSegments|||

||Examples
==========
assigning a Gender to each speaker in a set of utterences in an interview independent (and across) all physical representations of the interview (video, audio, transcription).|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The PrecessStep that produces AnalyticMetadata on PhysicalSegments


Note:
||Definition
============
The PrecessStep that produces AnalyticMetadata on PhysicalSegments|||

||Examples
==========
Typing a code on a defined segment in a qualitative data analysis package.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An algorithm for coding qualitative segments. 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.


Note:
||Definition
============
An algorithm for coding qualitative segments. 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.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
How, in general, coding will be performed.The design informs a specific or implemented process as to its general parameters.


Note:
||Definition
============
How, in general, coding will be performed.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
==============
|||


Note:
The method by which coding is performed.


Note:
Describes the results of a coding process.


Note:
Describes how the design of the coding is used to meet the goal of the coding.


Note:
||Definition
============
Describes how the design of the coding is used to meet the goal of the coding.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Sequencing of coding that can be defined either by Temporal or Order Relations as wel as conditional control constructs.


Note:
||Definition
============
Sequencing of coding that can be defined either by Temporal or Order Relations as wel as conditional control constructs. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A means of performing the qualitative coding 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).


Note:
||Definition
============
A means of performing the qualitative coding 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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A process step within the overall coding process.


Note:
A Member of a list, having an orderNumber to define the ordering.


Note:
This class serves as a place to annotate a Collection without adding an annotation to each element of the Collection.


Note:
||Definition
============
This class serves as a place to annotate a Collection without adding an annotation to each element of the Collection.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A type of StrictList defining the relationship between a Singleton and a Bag.


Note:
||Definition
============
A type of StrictList defining the relationship between a Singleton and a Bag.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
Mapping between inputs and outputs of Process Steps representing the flow of information to, from and within a Process.|||

||Examples
==========
An output of a Process Step can be mapped to an input of another Process Step.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Collection of Inputs and Outputs of the Process Step.


Note:
||Definition
============
An Input or Output to a Process Step. |||

||Examples
==========
|||

||Explanatory notes
===================
It could be class, a generic container or placeholder for an object instance, or an actual object instance.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
==========
Clinical research follows a process. This process can be described as a whole. Optionally, the whole can also be broken out in a series of process steps.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Process Design|||


Note:
A Process Step that controls the execution flow of the Process by determining the next Process Step in its scope.


Note:
||Definition
============
A Process Step that controls the execution flow of the Process by determining the next Process Step in its scope.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A bundle of properties that define the type of a relationship.


Note:
A Bag with one and only one Member. NOTE: this is intended only for the use as the source in a relationship.


Note:
||Definition
============
A Bag with one and only one Member. NOTE: this is intended only for the use as the source in a relationship.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Mapping between inputs and outputs of Process Steps representing the flow of information to, from and within a Process.


Note:
One of the constituents of a Process. It can be a composition or atomic and might be performed by a Service.


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:
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).


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:
Hierarchy or ParentChild relation where the Source is the Parent and Target is the Child


Note:
||Definition
============
Hierarchy or ParentChild relation where the Source is the Parent and Target is the Child|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Abstract base to describe and ordered or unordered list.


Note:
defines the order and member of a list item


Note:
Abstract base to classes describing relations between lists in a List Collection


Note:
||Definition
============
Abstract base to classes describing relations between lists in a List Collection|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A collection of lists and list relationships used to define a variety of collections


Note:
||Definition
============
A collection of lists and list relationships used to define a variety of collections|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Partative WholePart where source is the whole and target is the part


Note:
Subtype of list supporting a strict order list.


Note:
Subtype of List supporting and unordered list


Note:
An algorithm for defining segments. 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.


Note:
||Definition
============
An algorithm for defining segments. 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. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
How, in general, segments will be defined.The design informs a specific or implemented process as to its general parameters.


Note:
||Definition
============
How, in general, segments will be defined.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
==============
|||


Note:
What the segment definition aims to achieve.


Note:
The method by which segments are delineated.


Note:
||Definition
============
The method by which segments are delineated. |||

||Examples
==========
An analyst might highlight segments of text in a qualitative data analysis program. A web site developer might outline a part of an image with a polygon.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Describes how the design of the segment definition is used to meet the goal of the segment definition.


Note:
||Definition
============
Describes how the design of the segment definition is used to meet the goal of the segment definition.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The ProcessStep resulting in delineations of PhysicalSegments.


Note:
||Definition
============
The ProcessStep resulting in delineations of PhysicalSegments. |||

||Examples
==========
Highlighting pieces of text in a qualitative data analysis package.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Describes the results of a process of segment definition


Note:
A description of the budget for any of the main publication types that can contain a reference to an external budget document.


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:
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. ComplianceDescription can provide further details or a general description of compliance with a standard.


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. ComplianceDescription 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:
Provides information about data that are not currently available because of policies established by the principal investigators and/or data producers. This item may be attached to specific levels of a study such as a specific variable by reference. Embargo provides a name, label and description 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.


Note:
||Definition
============
Provides information about data that are not currently available because of policies established by the principal investigators and/or data producers. This item may be attached to specific levels of a study such as a specific variable by reference. Embargo provides a name, label and description 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:
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.


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:
A statement of quality which may be related to an external standard or contain a simple statement of internal quality goals or expectations. When relating to an external standard information on compliance may be added providing a reference to a ComplianceConcept, an ExternalComplianceCode, as well as a description. Optionally, a general statement of quality may be provided using OtherQualityStatement.


Note:
||Definition
============
A statement of quality which may be related to an external standard or contain a simple statement of internal quality goals or expectations. When relating to an external standard information on compliance may be added providing a reference to a ComplianceConcept, an ExternalComplianceCode, as well as a description. Optionally, a general statement of quality may be provided using OtherQualityStatement.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:QualityStatementType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


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


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:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
s:StudyUnitType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
StudySeries describes a series and therefore collection of collection activities as instances of Study.


Note:
||Definition
============
StudySeries describes a series and therefore collection of collection activities as instances of Study.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Something that suggests the presence or existence of a fact, condition, or quality.


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:
Concept or object denoted by the signifier associated to a sign.


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:
Concept whose extension includes perceivable objects.


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:
Contains parameters for the beginning and ending of a Clip of a type drawn from a controlled vocabulary


Note:
||Definition
============
Contains parameters for the beginning and ending of a Clip of a type drawn from a controlled vocabulary|||

||Examples
==========
clipBegin = 2013.3 clipEnd= 5987.5 of type AudioMilliseconds |||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines the location of a segment in a DataStore (e.g. 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.


Note:
||Definition
============
Defines the location of a segment in a DataStore (e.g. 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:
Points to a CustomInstance and a StructureForSegmentByCustom to define segments using a scheme not built in to DDI. The CustomInstance contains a set of key, value pairs defining each segment. The StructureForSegmentByCustom defines the keys.


Note:
||Definition
============
Points to a CustomInstance and a StructureForSegmentByCustom to define segments using a scheme not built in to DDI. The CustomInstance contains a set of key, value pairs defining each segment. The StructureForSegmentByCustom defines the keys.|||

||Examples
==========
using keys of "buildingName" "floor" and "room" to locate segments of a campus|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Points to a set of DDI identifiers that together identify a segment of DDI.


Note:
Points to a SPARQL query and related information


Note:
Points to the BeginEndClip parameter specifications for a Video Clip


Note:
Defines a segment of an XML file (or well formed HTML) using an XPointer.


Note:
Contains a SPARQL query and the necessary related information for retrieving a segment from a triple store.


Note:
||Definition
============
Contains a SPARQL query and the necessary related information for retrieving a segment from a triple store.|||

||Examples
==========
from: http://www.w3.org/TR/rdf-sparql-query/ 
SELECT ?title
WHERE
{
  <http://example.org/book/book1> <http://purl.org/dc/elements/1.1/title> ?title .
}   


or  

PREFIX foaf:   <http://xmlns.com/foaf/0.1/>
SELECT ?name ?mbox
WHERE
  { ?x foaf:name ?name .
    ?x foaf:mbox ?mbox }|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains an SQL statement and related information allowing the description of a segment of a relational database.


Note:
||Definition
============
Points to a set of DDI identifiers that together identify a segment of DDI.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines an area of an image - e.g. by a rectangle, a polygon


Note:
||Definition
============
Defines an area of an image - e.g. by a rectangle, a polygon|||

||Examples
==========
A bounding box for Mona Lisa's smile|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The description of a segment using a descriptive term from a controlled vocabulary.


Note:
||Definition
============
The description of a segment using a descriptive term from a controlled vocabulary.|||

||Examples
==========
The "superior vena cava"|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Points to one or more specifications of an SQL query and related information


Note:
||Definition
============
Points to one or more specifications of an SQL query and related information|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines the location of a segment of text.


Note:
||Definition
============
Defines the location of a segment of text.|||

||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.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
Contains an SQL statement and related information allowing the description of a segment of a relational database. |||

||Examples
==========
databaseType: MYSQL
sqlStatement: SELECT * FROM my_table WHERE name = 'Smith AND age < 30;|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Defines a custom set of key,value pairs for the description of the location of segments in some type of PhysicalResource


Note:
||Definition
============
Defines a custom set of key,value pairs for the description of the location of segments in some type of PhysicalResource|||

||Examples
==========
Location of segments of a well known religious text
Keys of:
"book" drawn from a controlled vocabulary 
 "chapter" an integer between 1 and 150 inclusive
"verse" an integer between 1 and 176|||

||Explanatory notes
===================
This structure defines a set of CustomItems each of which can be referenced for validation by a CustomValue. The CustomItems define the valid values and cardinalities of the keys used by teh CustomValues. A SegmentOfCustom will reference one or more CustomInstances each of which may contain a set pf CustomValues.
In the example above there would be 3 CustomItems one for each key (Book, Chapter, and Verse)

Specific references in CustomValues would use a Book from the controlled vocabulary and chapter and verse values within the allowable ranges.
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains an XPointer for identifying part of an XML document


Note:
||Definition
============
Contains an XPointer for identifying part of an XML document|||

||Examples
==========
See the examples in http://www.w3.org/TR/xptr-xpointer/ 
such as
xpointer(id("chap1")/range-to(id("chap2"))) |||

||Explanatory notes
===================
Should there be a ComplexDatatype of XPinterExpression that can be validated? This just is a String as is.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
High level, descriptive, human informative, algorithm statement used to describe the overall methodology. 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.


Note:
||Definition
============
High level, descriptive, human informative, algorithm statement used to describe the overall methodology. 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.
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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. 
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 hasProcess is not limited to any specific type of Process and can support the use of any 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.


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. 
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 hasProcess is not limited to any specific type of Process and can support the use of any 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.
|||

||Examples
==========
The target of a relationship has StudyMethodology
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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. Process Overview should be used when a description of the process in general is all that is desired.


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. Process Overview should be used when a description of the process in general is all that is desired.|||

||Examples
==========
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.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
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).


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:
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.


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:
Provides general description and specific targets for sample sizes including sub-populations.


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:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
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.


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:
Methodology may be used to define the design and process used within data collection, management, and use to achieve overall studies or specific activities such as sampling or weighting. A methodology in normally informed by earlier research and clarifies how earlier research methods were incorporated into the current work.


Note:
||Definition
============
Methodology may be used to define the design and process used within data collection, management, and use to achieve overall studies or specific activities such as sampling or weighting. 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:
The CubeLayout supports the description of the structure of aggregate data, and how it may be linked to the microdata of which it is a  cross-tabulation.


Note:
||Definition
============
The CubeLayout supports the description of the structure of aggregate data, and how it may be linked to the microdata of which it is a  cross-tabulation.|||

||Examples
==========
A tabulation of median income by single year of age and gender. One value of median income might be calculated for 46 year old (dimension 1) females (dimension 2).|||

||Explanatory notes
===================
In a cube a value resides in a cell which can be referenced (identified) by the values of one or more variables considered as dimensions. |||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The EventLayout exists to permit the description of data stored in a "tall" dataset format. For event data typically each row in the dataset will contain a single data point's value, a unit identifier, a reference to a variable, a start time, and end time, and a datatype (that of the referenced variable).


Note:
||Definition
============
The EventLayout exists to permit the description of data stored in a "tall" dataset format. For event data typically each row in the dataset will contain a single data point's value, a unit identifier, a reference to a variable, a start time, and end time, and a datatype (that of the referenced variable).|||

||Examples
==========
Data records as below

ID    value       Variable       Start                  End                     DataType
1      2.0          height         2016-01-14      2016-01_14        numeric
1      Boston     residence   2001-07-22       ---                      string|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The PhysicalLayout is an abstract class used as an extension point in the description of the different layout styles of data structure description. Examples include rectangular layouts, event data layouts, and cube layouts (e.g. summary data).


Note:
||Definition
============
The PhysicalLayout is an abstract class used as an extension point in the description of the different layout styles of data structure description. Examples include rectangular layouts, event data layouts, and cube layouts (e.g. summary data).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A realization of OrderRelation that is used to describe the sequence of Value Mappings in a Physical Layout.


Note:
||Definition
============
A realization of OrderRelation that is used to describe the sequence of Value Mappings in a Physical Layout. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
RectangularLayout supports the description of unit-record ("wide") data sets, where each row in the data set provides a group of values for variables all relating to a single unit. The columns will contain data relating to the values for a single variable.


Note:
||Definition
============
RectangularLayout supports the description of unit-record ("wide") data sets, where each row in the data set provides a group of values for variables all relating to a single unit. The columns 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.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The information needed for understanding the physical structure of data coming from a file or other source. Multiple styles of structural description are supported: including describing files as unit-record (rectangular) files; describing cubes; and describing event-history (spell) data. A StructureDescription also points to the Data Store it physically represents. StructureDescription is reusable.


Note:
||Definition
============
The information needed for understanding the physical structure of data coming from a file or other source. Multiple styles of structural description are supported: including describing files as unit-record (rectangular) files; describing cubes; and describing event-history (spell) data. A StructureDescription also points to the Data Store it physically represents. StructureDescription is reusable.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Provides physical characteristics for an InstanceVariable as part of a PhysicalLayout


Note:
||Definition
============
Provides physical characteristics for an InstanceVariable as part of a PhysicalLayout|||

||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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The specification of a controlled vocabulary defines a set of values and their definitions together with the order relationships among those entries.


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:
A set of CustomValues to be attached to some object.


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:
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.


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:
Contains the set of CustomItemParentChildPairs that define the parent child relationships in a CustomStructure.


Note:
||Definition
============
Contains the set of CustomItemParentChildPairs that define the parent child relationships in a CustomStructure.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains a set of CustomItemRelationshipPairs which together define the relationships of the type described by a predicate in each pair. A set of triples.


Note:
||Definition
============
Contains a set of CustomItemRelationshipPairs which together define the relationships of the type described by a predicate in each pair. A set of triples.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains a set of CustomItemSequencePairs which taken together define the sequence relationships among a set of CustomItems.


Note:
||Definition
============
Contains a set of CustomItemSequencePairs which taken together define the sequence relationships among a set of CustomItems.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Collection containing a set of item descriptions defining a structure for a set of key,value pairs


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:
An instance of a  key, value pair for a  particular  key.


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:
Contains the set of CustomValueParentChildPairs that define the parent child relationships in a CustomInstance.


Note:
||Definition
============
Contains the set of CustomValueParentChildPairs that define the parent child relationships in a CustomInstance.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains a set of CustomValueRelationshipPairs which together define the relationships of the type described by a predicate in each pair. A set of triples.


Note:
||Definition
============
Contains a set of CustomValueRelationshipPairs which together define the relationships of the type described by a predicate in each pair. A set of triples.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains a set of CustomValueSequencePairs which taken together define the sequence relationships among a set of CustomValues.


Note:
||Definition
============
Contains a set of CustomValueSequencePairs which taken together define the sequence relationships among a set of CustomValues.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
One value and its definition in an ordered list comprising a controlled vocabulary.


Note:
||Definition
============
One value 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:
Contains the set of VocabularyParentChildPairs that define the a hierarchical relationship among the vocabulary entries.


Note:
||Definition
============
Contains the set of VocabularyParentChildPairs that define the a hierarchical relationship among the vocabulary entries.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Contains a set of VocabularySequencePairs which taken together define an ordering for a ControlledVocabulary


Note:
||Definition
============
Contains a set of VocabularySequencePairs which taken together define an ordering for a ControlledVocabulary|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the contains relation in Allen's interval algebra.

We say that an interval A contains another interval B if and only if A begins before B but finishes after it. 

More precisely, A.start < B.start < B.end < A.end.

Instead of saying that A contains B we can also say that B is during A (converse).


Note:
||Definition
============
Representation of the contains relation in Allen's interval algebra.

We say that an interval A contains another interval B if and only if A begins before B but finishes after it. 

More precisely, A.start < B.start < B.end < A.end.

Instead of saying that A contains B we can also say that B is during A (converse).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the equals relation in Allen's interval algebra.

We say that an interval A equals another interval B if and only if they both begin and finish at the same time.

More precisely, A.start = B.start < A.end = B.end.

Instead of saying that A equals B we can also say the B equals A (reflexive).


Note:
||Definition
============
Representation of the equals relation in Allen's interval algebra.

We say that an interval A equals another interval B if and only if they both begin and finish at the same time.

More precisely, A.start = B.start < A.end = B.end.

Instead of saying that A equals B we can also say the B equals A (reflexive).
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
During execution ProcessSteps follow one another over time. This is also true when we parallelize because within each thread work flows. In every thread during execution we advance through a sequence of pairs. Each pair has a "prev" and a "cur". In the course of execution "cur" becomes "prev" and a new "cur" comes along.

In this context the Execution Pair is the current "prev" and "cur".

It is between the current "prev" and "cur" that messages flow. The output of prev can be mapped to the input of "cur". This mapping is commonly referred to as a "binding" or in the terms of a collection an OrderedMemberCorrespondence.


Note:
||Definition
============
During execution ProcessSteps follow one another over time. This is also true when we parallelize because within each thread work flows. In every thread during execution we advance through a sequence of pairs. Each pair has a "prev" and a "cur". In the course of execution "cur" becomes "prev" and a new "cur" comes along.

In this context the Execution Pair is the current "prev" and "cur".

It is between the current "prev" and "cur" that messages flow. The output of prev can be mapped to the input of "cur". This mapping is commonly referred to as a "binding" or in the terms of a collection an OrderedMemberCorrespondence.|||

||Examples
==========
Let's think of Acts. Acts are ProcessSteps with inputs and outputs. Imagine two acts -- first a calculation and next a question we ask. Together they form an ExecutionPair in the course of time. In this pair the output of the calculation becomes the input of the question we ask perhaps as "fill". |||

||Explanatory notes
===================
There are two other patterns in connect with ExecutionPairs.

Imagine a loop. In the body of the loop there is a sequence (an "iteration" in the context of a loop). Within the iteration we can imagine binding the previous output to the current input. At some point there is a last iteration. What happens to the output of the last element in the sequence? Instead of binding it to next input we might bind its output to the output of the loop.

Likewise we might bind the input of the loop to "something" or not. |||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the finishes relation in Allen's interval algebra.

We say that an interval A finishes another interval B if and only if A begins after B but both finish at the same time.

More precisely, B.start < A.start < B.end = A.end.

Instead of saying that A finishes B we can also say that B is finished by A (converse)


Note:
||Definition
============
Representation of the finishes relation in Allen's interval algebra.

We say that an interval A finishes another interval B if and only if A begins after B but both finish at the same time.

More precisely, B.start < A.start < B.end = A.end.

Instead of saying that A finishes B we can also say that B is finished by A (converse)|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the meets relation in Allen's interval algebra.

We say that an interval A meets another interval B if and only if A finishes when B begins.

More precisely, A.ends = B.start.

Instead of saying that A meets B we can also say that B is met by A (converse).


Note:
||Definition
============
Representation of the meets relation in Allen's interval algebra.

We say that an interval A meets another interval B if and only if A finishes when B begins.

More precisely, A.ends = B.start.

Instead of saying that A meets B we can also say that B is met by A (converse).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the overlaps relation in Allen's interval algebra.

We say that an interval A overlaps another interval B if and only if A begins before B but finishes during B.

More precisely, A.start < B.start < A.end < B.end.

Instead of saying that A overlaps B we can also say that B is overlapped by A (converse).


Note:
||Definition
============
Representation of the overlaps relation in Allen's interval algebra.

We say that an interval A overlaps another interval B if and only if A begins before B but finishes during B.

More precisely, A.start < B.start < A.end < B.end.

Instead of saying that A overlaps B we can also say that B is overlapped by A (converse).
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the precedes relation in Allen's interval algebra.

We say that an interval A precedes another interval B if and only if A finishes before B begins.

More precisely, A.end < B.start.

Instead of saying that A precedes B we can also say that B is preceded by A (converse).


Note:
||Definition
============
Representation of the precedes relation in Allen's interval algebra.

We say that an interval A precedes another interval B if and only if A finishes before B begins.

More precisely, A.end < B.start.

Instead of saying that A precedes B we can also say that B is preceded by A (converse).
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The components of a Split process are a bag of process components to be executed concurrently. Split completes as soon as all of its component processes have been scheduled for execution


Note:
||Definition
============
The components of a Split process are a bag of process components to be executed concurrently. Split completes as soon as all of its component processes have been scheduled for execution|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Here the process consists of concurrent execution of a bunch of process components with barrier synchronization. That is, SplitJoin completes when all of its components processes have completed. With Split and SplitJoin, we can define processes that have partial synchronization (e.g., split all and join some sub-bag)


Note:
||Definition
============
Here the process consists of concurrent execution of a bunch of process components with barrier synchronization. That is, SplitJoin completes when all of its components processes have completed. With Split and SplitJoin, we can define processes that have partial synchronization (e.g., split all and join some sub-bag)|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Representation of the starts relation in Allen's interval algebra.

We say that an interval A starts another interval B if and only if they both start at the same time but A finishes first.

More precisely, A.start = B.start < A.end <B.end

Instead of saying that A starts B we can also say that B is started by A (converse).


Note:
||Definition
============
Representation of the starts relation in Allen's interval algebra.

We say that an interval A starts another interval B if and only if they both start at the same time but A finishes first.

More precisely, A.start = B.start < A.end <B.end

Instead of saying that A starts B we can also say that B is started by A (converse).
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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]


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:
Relation that specifies temporal constraints between pairs of Process Steps in a Sequence following Allen's interval algebra. A Sequence in the Process Model is a Control Construct in which the elements of the sequence (i.e. Process Steps) have positions on a timeline with respect to each other.

In Allen's interval algebra between Process Steps a and b there are seven possible relations. All but one are asymmetric and thus have a converse. The exception is the situation where two intervals are coextensive. Then the relation and its converse are the same, namely equal, which is an equivalence relation.


Note:
||Definition
============
Relation that specifies temporal constraints between pairs of Process Steps in a Sequence following Allen's interval algebra. A Sequence in the Process Model is a Control Construct in which the elements of the sequence (i.e. Process Steps) have positions on a timeline with respect to each other.

In Allen's interval algebra between Process Steps a and b there are seven possible relations. All but one are asymmetric and thus have a converse. The exception is the situation where two intervals are coextensive. Then the relation and its converse are the same, namely equal, which is an equivalence relation.|||

||Examples
==========
|||

||Explanatory notes
===================
Here are the relations in Allen's interval algebra:

a precedes b (p) and b is preceded by a (P)
a meets b (m) and b is met by a (M)
a overlaps b (o) and b is overlapped by a (O)
a is finished by b (F) and b finishes a (f)
a contains B (D) and b is during a (d)
a starts b (s) and b is started by a (S)
a and b equal (e) each other 

There is no guarantee that a set of pairs will be tractable. A simple example of a collection of relations and intervals that is not tractable is three intervals a, b, and c such that a(p)b, b(p)c, and c(p)a (each precedes the next, and the last precedes the first).  There are no definite intervals for which all these relations can hold. In this event we say that the collection is unsatisfiable.

That being said certain collections of pairwise relations are in fact composable. Composition is not commutative but is both left and right associative, and distributes over union. Collections that are composable support inference over their pairs. In fact, certain mixes of pairwise relations have been found to be composable over a collection. These mixes are call tractable subalgebras. Eighteen of these have been identified.

For a more in-depth discussion see http://www.ics.uci.edu/~alspaugh/cls/shr/allen.html.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Provides an extensible framework for specific transformation objects.


Note:
||Definition
============
Provides an extensible framework for specific transformation objects.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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.|||

||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:
Type of WorkflowStep in which the execution flow is determined by one or more conditions.


Note:
||Definition
============
Type of WorkflowStep 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:
IfThenElse describes an if-then-else decision type of control construct. If the stated condition is met, then the associated Workflow Sequence in contains (inherited from Conditional Control Construct) is triggered, otherwise the Workflow Sequence that is triggered is the one associated via elseContains.


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 contains (inherited from Conditional Control Construct) is triggered, otherwise the Workflow Sequence that is triggered is the one associated via elseContains.
|||

||Examples
==========
(add example)|||

||Explanatory notes
===================
Contains a condition and two associations:
- one to the Workflow Sequence that is triggered when the condition is true (contains), and 
- another to the Workflow Sequence that is triggered when the condition is false (elseContains). 
The contains relationship is inherited from Conditional Control Construct.|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:IfThenElseType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
==========
|||

||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
==========
|||

||DDI 3.2 mapping
=================
d:LoopType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Iterative control structure to be repeated until a specified condition is met. Before 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.


Note:
||Definition
============
Iterative control structure to be repeated until a specified condition is met. Before 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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:RepeatUntilType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:RepeatWhileType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Generic container for an parameter used to identify specific information moving into and out of WorkflowStep.


Note:
||Definition
============
Generic container for an parameter used to identify specific information moving into and out of WorkflowStep. |||

||Examples
==========
Input variables for imputation.|||

||Explanatory notes
===================
|||

||Synonyms
==========
InParameter, Binding|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Workflow Process is a realization of Process which identifies the Workflow Step Collection which contains the WorkflowSteps and their order. It may identify the algorithm that it implements.


Note:
||Definition
============
A Workflow Process is a realization of Process which identifies the Workflow Step Collection 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|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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).


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
One of the constituents of a Workflow. It can be a composition or atomic and might be performed by a Service.


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:
Ordering of Workflow Steps that can be defined either by Temporal or Order Relations. 

The sequence can be typed to support local processing or classification flags and alternate sequencing instructions (such as randomize for each respondent).


Note:
||Definition
============
Ordering of Workflow Steps that can be defined either by Temporal or Order Relations. 

The sequence can be typed to support local processing or classification flags and alternate sequencing instructions (such as randomize for each respondent).

|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:SequenceType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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 an extension base for specific external materials found within DDI (such as an External Aid); as a target object from a relationship which clarifies its role within a class; or as the target of a relatedResource within an annotation.


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 an extension base for specific external materials found within DDI (such as an External Aid); 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. It is used as a base for specifically related material (ExternalAid, ExternalInstructions, etc.) by creating a relationship whose name clarifies the purpose of the related material. 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
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:OtherMaterialType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:FundingInformationType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A note related to one or more identifiable objects. Note is designed to be an inherent part of the DDI. (Unlike XML comments or other types of system-level annotations, which may be removed during processing.) DDI recommends placing the note within the maintainable object containing the objects this note relates to in order to assist tracking of note items within a study. Each note may indicate who is responsible for the note, its type using a controlled vocabulary, the subject of the note, a head and note content, a set of key/value pairs and language specification for the overall note. In addition each note must be related to one or more identifiable objects.


Note:
||Definition
============
A note related to one or more identifiable objects. Note is designed to be an inherent part of the DDI. (Unlike XML comments or other types of system-level annotations, which may be removed during processing.) DDI recommends placing the note within the maintainable object containing the objects this note relates to in order to assist tracking of note items within a study. Each note may indicate who is responsible for the note, its type using a controlled vocabulary, the subject of the note, a head and note content, a set of key/value pairs and language specification for the overall note. In addition each note must be related to one or more identifiable objects.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:NoteType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Neither.

It must contain like items.


Note:
||Definition
============
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Neither.

It must contain like items.
|||

||Examples
==========
|||

||Explanatory notes
===================
It includes the Temporal_Overlaps semantics to express the overlaps relation in Allen's temporal algebra.

It includes the Tangential_Proper_Part semantics to express the TPP relation in Region Connection Calculus (RCC) for qualitative spatial representations.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a Collection (set or bag) characterized by the following assignments to the types inherited from Binary Relation:
- Symmetry = Asymmetric.


Note:
||Definition
============
Relation over members in a Collection (set or bag) characterized by the following assignments to the types inherited from Binary Relation:
- Symmetry = Asymmetric.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation whose n-ary tuples are ordered. It could be the result of a join between one or more Binary Relations.


Note:
||Definition
============
Relation whose n-ary tuples are ordered. It could be the result of a join between one or more Binary Relations.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Correspondence Table|||


Note:
Set of ordered pairs of Members of the Collection the Binary Relation structures.


Note:
||Definition
============
Set of ordered pairs of Members of the Collection the Binary Relation structures.|||

||Examples
==========
Same-As, Successor-Of, Parent-Of, Part-Of, Subclass-Of are all Binary Relations.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Collection container (set or bag). It could have an optional order relation (total or partial) associated to it to model linear order, hierarchies and nesting. A Collection is also a subtype of Member to allow for nested collections.


Note:
||Definition
============
Collection container (set or bag). It could have an optional order relation (total or partial) associated to it to model linear order, hierarchies and nesting. A Collection is also a subtype of Member to allow for nested collections.|||

||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.

Collection is not extended, it is realized (see Collection Pattern documentation).|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Symmetric Binary Relation:
- Reflexivity = Reflexive;
- Symmetry = Symmetric (same as parent class);
- Transitivity = Transitive.

It must contain like items.


Note:
||Definition
============
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Symmetric Binary Relation:
- Reflexivity = Reflexive;
- Symmetry = Symmetric (same as parent class);
- Transitivity = Transitive.

It must contain like items.|||

||Examples
==========
|||

||Explanatory notes
===================
It includes the Temporal_Equals semantics to express the equals relation in Allen's temporal algebra. |||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Anti_Transitive.

It must contain like items.


Note:
||Definition
============
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Anti_Transitive.

It must contain like items.
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Generic class representing members of a collection.


Note:
||Definition
============
Generic class representing members of a collection. 
|||

||Examples
==========
Node, 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
==============
|||


Note:
Set of ordered, n-ary tuples of Members of the Collection the Relation structures.


Note:
||Definition
============
Set of ordered, n-ary tuples of Members of the Collection the Relation structures. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Reflexive;
- Symmetry  = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Transitive.

It must contain like items.


Note:
||Definition
============
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Reflexive;
- Symmetry  = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Transitive.

It must contain like items.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Ordered pair of Members of the Collection structured by the Asymmetric Binary Relation to which the pair belongs.


Note:
||Definition
============
Ordered pair of Members of the Collection structured by the Asymmetric Binary Relation to which the pair belongs.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Ordered n-ary tuple of Members of the Collection structured by the Asymmetric Relation to which the tuple belongs. Members are separated into two groups: source and target.


Note:
||Definition
============
Ordered n-ary tuple of Members of the Collection structured by the Asymmetric Relation to which the tuple belongs. Members are separated into two groups: source and target.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Transitive.

It must contain like items.


Note:
||Definition
============
Relation over members in a collection (set or bag) characterized by the following assignments to the types inherited from Asymmetric Binary Relation:
- Reflexivity = Anti_Reflexive;
- Symmetry = Anti_Symmetric (more restrictive than parent class) ;
- Transitivity = Transitive.

It must contain like items.
|||

||Examples
==========
|||

||Explanatory notes
===================
It includes the Temporal_Precedes, Temporal_Finishes, Temporal_Contains and Temporal_Starts semantics to express the precedes, finishes, contains and starts relations, respectively, in Allen's temporal algebra.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A response domain capturing a binary response, such as selected/unselected or checked/unchecked or true/false.


Note:
||Definition
============
A response domain capturing a binary response, such as selected/unselected or checked/unchecked or true/false.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
Design plan for creating a data capture tool.


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, utlizing the same sequence and questions.
similarly 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:
Relation over members in a Collection (set or bag) characterized by the following assignments to the types inherited from Binary Relation:
- Symmetry = Symmetric.


Note:
||Definition
============
Relation over members in a Collection (set or bag) characterized by the following assignments to the types inherited from Binary Relation:
- Symmetry = Symmetric.

|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Relation whose n-ary tuples are not ordered. It could be the result of a join between one or more Binary Relations.


Note:
||Definition
============
Relation whose n-ary tuples are not ordered. It could be the result of a join between one or more Binary Relations.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Unordered pair of Members of the Collection structured by the Symmetric Binary Relation to which the pair belongs.


Note:
||Definition
============
Unordered pair of Members of the Collection structured by the Symmetric Binary Relation to which the pair belongs.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Unordered n-ary tuple of Members of the Collection structured by the Symmetric Relation to which the tuple belongs.


Note:
||Definition
============
Unordered n-ary tuple of Members of the Collection structured by the Symmetric Relation to which the tuple belongs.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
ImplementedInstruments are mode and/or unit specific.


Note:
||Definition
============
ImplementedInstruments are mode and/or unit specific.|||

||Examples
==========
Implementing 2 versions (CAPI and mail) of a conceptual instrument.|||

||Explanatory notes
===================
|||

||Synonyms
==========
aka PhysicalInstrument|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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:
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.


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:
Provides the content and description of data capture instructions. Contains the "how to" information for administering an instrument.


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
============
|||

||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:
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.


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:
A response domain capturing a numeric response (the intent is to analyze the response as a number) for a question.


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:
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.


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:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The description of a reusable question, that can be used as a template that describes the components of a question


Note:
||Definition
============
The description of a reusable question, that can be used as a template that describes the components of a question|||

||Examples
==========
|||

||Explanatory notes
===================
A question that is repeated across waves of a panel study can be reused and also allow reference to a RepresentedVariable.|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
d:QuestionItemType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The possible list of values that are allowed by a Capture.


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:
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.


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:
A Statement is human readable text or referred material.


Note:
||Definition
============
A Statement is human readable text or referred material.|||

||Examples
==========
Introductory text; Explanations; Labels, Headers, Help screens, etc.  |||

||Explanatory notes
===================
|||

||Synonyms
==========
DDI:StatementItem|||

||DDI 3.2 mapping
=================
d:StatementItemType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A response domain capturing a textual response including the length of the text and restriction of content using a regular expression.


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:
Identifies the authorizing agency and allows for the full text of the authorization (law, regulation, or other form of authorization).


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
===================
|||

||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:
A Category Set is a type of Node Set which groups Categories.


Note:
||Definition
============
A Category Set is a type of Node Set which groups Categories.
|||

||Examples
==========
For example: 
Male, Female|||

||Explanatory notes
===================
The Categories in a Category Set typically have no assigned Designations (Codes).|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
l:CategorySchemeType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Category Set|||


Note:
A Classification Family is a group of Classification Series related from a particular point of view. The Classification Family is related by being based on a common Concept (e.g. economic activity).[GSIM1.1]


Note:
||Definition
============
A Classification Family is a group of Classification Series related from a particular point of view. The Classification Family is related by being based on a common Concept (e.g. economic activity).[GSIM1.1]|||

||Examples
==========
|||

||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:
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]


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
==========
|||

||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 Node Set. The relationship between Statistical Classification and Classification Index can also be extended to include the other Node Set types - Code List and Category Set.  [GSIM Statistical Classification Model]|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Classification Index|||


Note:
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.


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
===================
A Classification Item is a subtype of Node. The relationship between Classification Item and Classification Index Entry can also be extended to include the other Node types - Code Item and Category Item.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Classification Index Entry|||


Note:
A Classification Item represents a Category at a certain Level within a Statistical Classification.


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:
A Classification Series is an ensemble of one or more Statistical Classifications, based on the same concept, and related to each other as versions or updates. Typically, these Statistical Classifications have the same name (for example, ISIC or ISCO).


Note:
||Definition
============
A Classification Series is an ensemble of one or more Statistical Classifications, based on the same concept, and related to each other as versions or updates. Typically, these Statistical Classifications have the same name (for example, ISIC or ISCO).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Classification Series|||


Note:
||Definition
============
A Designation for a Category.|||

||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 an alphanumeric string assigned to stand in place of a category. 

It should not be confused with a ClassificationItem which is a placeholder for a position in a StatisitcalClassification. 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:
A type of Node contained in a CodeList that has a Code associated to a Category. In addition, a CodeItem can have a number of optional Designations. All Designations associated to the Code Item, including the Code, are synonyms, i.e. are associated with the same Concept.


Note:
||Definition
============
A type of Node contained in a CodeList that has a Code associated to a Category. In addition, a CodeItem can have a number of optional Designations. All Designations associated to the Code Item, including the Code, are synonyms, i.e. are associated with the same Concept.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A list of Codes and associated Categories. May be flat or hierarchical.


Note:
||Definition
============
A list of Codes and associated Categories. May be flat or hierarchical. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
l:CodeListType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Code List|||


Note:
A Correspondence Table expresses a relationship between two NodeSets.


Note:
||Definition
============
A Correspondence Table expresses a relationship between two NodeSets.|||

||Examples
==========
|||

||Explanatory notes
===================
CorrespondenceTables are typically used in specializations of NodeSet, like 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:
Sequence of Classification Index Entries in a Classification Index.


Note:
The Level describes the nesting structure of a hierarchical collection.


Note:
||Definition
============
The Level describes the nesting structure of a hierarchical collection.

|||

||Examples
==========
|||

||Explanatory notes
===================
Levels are used to organize the Nodes in a hierarchical Node Set. Usually, a hierarchy contains one Node at the top, though it could contain several. These are the first Level. All Nodes directly related to the Nodes in the first Level compose the second Level. The third and subsequent Levels are defined similarly. The special kind of Node Set called a Statistical Classification is almost always organized as a hierarchy. They typically contain 3 to 5 Levels.

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.|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
l:LevelType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
Level|||


Note:
A combination of a category and its designations.


Note:
||Definition
============
A combination of a category and its designations.
|||

||Examples
==========
Within a CodeList (a subtype of NodeSet) each CodeItem is a Node and contains the representation of the code and the category the code denotes.|||

||Explanatory notes
===================
A Node is created as a CategoryItem, CodeItem or Classification Item for the purpose of defining the situation in which the Category is being used.


|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Node|||


Note:
Parent-child hierarchy of Nodes in a Node Set.


Note:
The Value Domain for a substantive conceptual domain.


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
===================
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:
A formal description of a set of values.


Note:
||Definition
============
A formal description of a set of values. |||

||Examples
==========
The integers between 1 and 10 inclusive.  
The values of x satisfying the logical expression:
 (1 <=x <= 10) AND mod(x,10)=0|||

||Explanatory notes
===================
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:
The permitted range of values for a characteristic of a variable. [GSIM 1.1]


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|||


Note:
A vocabulary is an established list of standardized terminology for use in indexing and retrieval of information.


Note:
||Definition
============
A vocabulary is an established list of standardized terminology for use in indexing and retrieval of information.|||

||Examples
==========
A dictionary or thesauri, specialist vocabulary such as HASSET, MESH|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
c:VocabularyType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Part-whole relation of Nodes in a Node Set.


Note:
A NodeSet is a set of Nodes, which could be organized into a hierarchy of Levels.


Note:
||Definition
============
A NodeSet is a set of Nodes, which could be organized into a hierarchy of Levels.|||

||Examples
==========
Here are 2 examples: 

1) Sex Categories
Male
Female
Other 

2) Sex Codes
<m, male>
<f, female>
<o, other>|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Node Set|||


Note:
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.


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:
A Statistical Classification is a set of Categories 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)


Note:
||Definition
============
A Statistical Classification is a set of Categories 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
===================
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.Categories in Statistical Classifications are represented in the information model as Classification Items. (Source: GSIM StatisticalClassification|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Statistical Classification|||


Note:
A MeasureRole  identifies an InstanceVariable as being an attribute within a ViewPoint.


Note:
||Definition
============
A MeasureRole  identifies an InstanceVariable as being an attribute within a ViewPoint.

|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
A DataPoint is a container for a Datum.|||

||Examples
==========
|||

||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:
A Record is a Collection of DataPoints with an optional OrderRelation.

[Name of the class needs to be changed to Record].


Note:
||Definition
============
A Record is a Collection of DataPoints with an optional OrderRelation.

[Name of the class needs to be changed to Record].|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
An organized collection of data 

Additional information:
Using its datapoints and their processing instructions, a datastore can host questionnaire and variable datum wiring them together to form processing pipelines in all shapes and forms. Also, in line with a spreadsheet, a datastore can host multiple data structures. So a datastore can contain unit data as well as a pivot table that represents the unit data dimensionally. Likewise, the same datastore may contain both a normalized recordset in which entities are columns and its denormalized counterpart in which the rows are entities. Given processing instructions, one can losslessly be constructed from the other.


Note:
||Definition
============
An organized collection of data 

Additional information:
Using its datapoints and their processing instructions, a datastore can host questionnaire and variable datum wiring them together to form processing pipelines in all shapes and forms. Also, in line with a spreadsheet, a datastore can host multiple data structures. So a datastore can contain unit data as well as a pivot table that represents the unit data dimensionally. Likewise, the same datastore may contain both a normalized recordset in which entities are columns and its denormalized counterpart in which the rows are entities. Given processing instructions, one can losslessly be constructed from the other.
|||

||Examples
==========
Data could live in either files, a relational database table/view/procedure, or an RDF-feed. Many other possibilities exist.|||

||Explanatory notes
===================
This is the entry point to interact with data. 

A DataStore has a set of properties which enable you to appropriately read the data.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Data Set|||


Note:
||Definition
============
A Collection or Library of DataStores|||

||Examples
==========
This is intended to support for instance the losses transformation of datastores, from say a SAS database to a SQL database, but the logical datastore is identical|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A Datum is the designation of a concept with a notion of equality defined.


Note:
||Definition
============
A Datum is the designation of a concept with a notion of equality defined.|||

||Examples
==========
|||

||Explanatory notes
===================
A Datum is the actual instance of data that was collected or derived. It is the value which populates a Data Point. A Datum is the value found in a cell of a table. [GSIM 1.1]

NOTE: This is NOT datum from DDI3.2 (which is quite specific).|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Datum|||


Note:
An IdentifierRole  identifies an InstanceVariable as being an identifier within a ViewPoint.


Note:
||Definition
============
An IdentifierRole  identifies an InstanceVariable as being an identifier within a ViewPoint.
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Collection of Instance Variables that function as a record type describing the structure of individual records.


Note:
||Definition
============
Collection of Instance Variables that function as a record type describing the structure of individual records. 
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
Data Structure|||


Note:
A realization of OrderRelation that is used to describe the sequence of Instance Variables in a record layout for those cases where there is a logical order of the variables.


Note:
||Definition
============
A realization of OrderRelation that is used to describe the sequence of Instance Variables in a record layout for those cases where there is a logical order of the variables.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A MeasureRole  identifies an InstanceVariable as being a measure within a ViewPoint.


Note:
||Definition
============
A MeasureRole  identifies an InstanceVariable as being a measure within a ViewPoint.
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The RecordRelation object is used to indicate relationships among record types within and between datasets. For InstanceVariables existing in a data set 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.


Note:
||Definition
============
The RecordRelation object is used to indicate relationships among record types within and between datasets. For InstanceVariables existing in a data set 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
==========
|||

||Explanatory notes
===================
A household record type might contain an InstanceVariable called HouseholdID and a person record might contain an InstanceVariable called HID. Describing a link between HouseholdID and HID would allow the linking of person records to their corresponding household record.|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
The assignment of measure, identifier and attribute roles to InstanceVariables


Note:
||Definition
============
The assignment of measure, identifier and attribute roles to InstanceVariables|||

||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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A ViewpointRole designates the function an InstanceVariable performs in the context of the ViewPoint. (IdentifierRole, AttributeRole, or MeasureRole of interest).


Note:
||Definition
============
A ViewpointRole designates the function an InstanceVariable performs in the context of the ViewPoint. (IdentifierRole, AttributeRole, or MeasureRole of interest).
|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A collection of Agent Listings and/or AgentRelationships describing individual agents and their relationships to each other over time.


Note:
||Definition
============
A collection of Agent Listings and/or AgentRelationships describing individual agents and their relationships to each other over time.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A collection of relationships between pairs of Agents.


Note:
A specific type of Agent Binary relationship that is used when the intent is to express the similarity between a pair of agents. Uses the pattern for EquivalenceRelation. Each pair must contain like items. The relation of the members in the collection is characterized by the following assignments: Reflexivity=Reflexive; Symmetry=Semetric; Transitivity=Transitive.


Note:
||Definition
============
A specific type of Agent Binary relationship that is used when the intent is to express the similarity between a pair of agents. Uses the pattern for EquivalenceRelation. Each pair must contain like items. The relation of the members in the collection is characterized by the following assignments: Reflexivity=Reflexive; Symmetry=Semetric; Transitivity=Transitive.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A person who acts, or is designated to act towards a specific purpose.


Note:
||Definition
============
A person who acts, or is designated to act towards a specific purpose.|||

||Examples
==========
Analyst performing edits on data, interviewer conducting an interview.|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Mechanism or computer program used to implement a process.


Note:
||Definition
============
Mechanism or computer program used to implement a process.|||

||Examples
==========
SAS program, photocopier|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A framework of authority designated to act toward some purpose.


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:
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.


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:
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.


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:
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.


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
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
a:AccessType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A type of Spatial coverage describing a rectangular area within which the actual range of location fits. A BoundingBox can be described by 4 numbers, or two x,y coordinates - the maxima of the north, south, east, and west coordinates found in the area.


Note:
||Definition
============
A type of Spatial coverage describing a rectangular area within which the actual range of location fits. A BoundingBox can be described by 4 numbers, or two x,y coordinates - the maxima of the north, south, east, and west coordinates found in the area.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
r:BoundingBox|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A catalog item is designed to provide a bibliographic, coverage and related description of an item in a catalog.


Note:
||Definition
============
A catalog item is designed to provide a bibliographic, coverage and related description of an item in a catalog.|||

||Examples
==========
A bibliographic record in collection catalog|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Means of creating a catalog of items in a collection or sub-sets of a larger catalog


Note:
||Definition
============
Means of creating a catalog of items in a collection or sub-sets of a larger catalog|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Coverage information for an annotated object. Includes coverage information for temporal, topical, and spatial coverage.


Note:
||Definition
============
Coverage information for an annotated object. Includes coverage information for temporal, topical, and spatial coverage. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

||DDI 3.2 mapping
=================
r:CoverageType|||

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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.|||

||Explanatory notes
===================
|||

||Synonyms
==========
r:SpatialCoverage, place|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Describes the date or time period covered by the annotated object. Allows for the use of a specifying the type of coverage date as well as associated subjects or keywords.


Note:
||Definition
============
Describes the date or time period covered by the annotated object. Allows for the use of a specifying the type of coverage date as well as associated subjects or keywords.|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
Describes the topical coverage of the module using Subject and Keyword. Note that upper level modules should include all the members of lower level modules. 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.


Note:
An actor that performs a role in relation to a process.


Note:
||Definition
============
An actor that performs a role in relation to a process. |||

||Examples
==========
Analyst performing edits on data, interviewer conducting an interview, a relational database management system managing data, organization publishing data on a regular basis.|||

||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:
This abstract structure is used as the extension base for all Binary Relations between two agents. It allows new Binary Relations to be created without changing the collection Agent Relationships in order to accommodate them. As an extension base it provides a consistent set of properties to all Binary Relations used between Agents.


Note:
||Definition
============
This abstract structure is used as the extension base for all Binary Relations between two agents. It allows new Binary Relations to be created without changing the collection Agent Relationships in order to accommodate them. As an extension base it provides a consistent set of properties to all Binary Relations used between Agents. |||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
A set of relationships between pairs of Agents that is hierarchical (Parent/Child) in nature. Uses the pattern for Immediate Precedence Relation where the relation over members in the Agent Registry is characterized by the following: Reflexivity=Anti_Reflexive; Symmetry=Anti_Symmedtric; Transitivity=Anti_Transitive. It must contain like items (Agents).


Note:
||Definition
============
A set of relationships between pairs of Agents that is hierarchical (Parent/Child) in nature. Uses the pattern for Immediate Precedence Relation where the relation over members in the Agent Registry is characterized by the following: Reflexivity=Anti_Reflexive; Symmetry=Anti_Symmedtric; Transitivity=Anti_Transitive. It must contain like items (Agents).|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
||Definition
============
Describes the topical coverage of the module using Subject and Keyword. Note that upper level modules should include all the members of lower level modules. 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:
Links the guidance instructions to specific unit types.


Note:
||Definition
============
Links the guidance instructions to specific unit types.|||

||Examples
==========
Links a guide 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:
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.


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:
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:
A basic set of objects that can support structured searching for discovery and ingest to statistical software, and provide sufficient information for the intelligent use and understanding of the associated data. Making data independently understandable so people can reuse it. 

Use Cases:
This Functional View supports three major uses
* Basic search to find data (general search, known item search). Users are looking to use data.
* Machine actionable to allow users to analyze the data (ingest to statistical software)
* Informational content to support Intelligent use and understanding the data

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

General Usage Instructions:
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.


Note:
Purpose:
The purpose of the Instrument Functional View is to describe the data collection instrument and procedures involved in fielding a simple survey questionnaire. It allows only basic Domains (Text, Numeric, and CodeList), but supports the full questionnaire flow (Sequence, IfThenElse, ElseIf, Loop, RepeatUntil, and RepeatWhile). The specific flow of the Instrument is described using PrecedesIntervalRelation. Support has also been provided for binding the output of one capture to the input of another, for example, the number of persons in the household output used as the condition of a Loop. 

Target Audience:
Creator's of simple questionnaires.

Included Classes: 
Category, CategorySet, CodeItem, CodeList, Concept, ConceptualInstrument, ConceptualVariable, ExternalAid, ExternalMaterial, IfThenElse, ImplementedInstrument, InstanceQuestion, Instruction, InstrumentCode, Level, Loop, OrderedIntervalPair,  PrededesIntervalRelation, RepeatUntil, RepeatWhile, RepresentedQuestion, RepresentedVariable, ResponseDomain, SentinelConceptualDomain, SentinelValueDomain, Statement , SubstantiveConceptualDomain, SubstantiveValueDomain, UnitType, Universe, ValueAndConceptDescription, WorkflowParameter, WorkflowSequence 

Restricted Classes:
The following classes have been restricted. 
The relationships with target class "WorkflowService" must be external references, they cannot be included in an implementation of the view. These were restricted as no specific type of WorkflowService relating to an Instrument has been created. 
Conceptualinstrument can only include Design, Algorithm, Result, and Precondition only by use of an external reference.

General Documentation
The general top-level entry points are ImplementedInstrument or ConceptualInstrument for content and PrecedesIntervalRelation for the ordering of Sequences and other control construct types.


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:
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.


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:
Provides a guide for the usage of a result within a specified application


Note:
||Definition
============
Provides a guide for the usage of a result within a specified application|||

||Examples
==========
|||

||Explanatory notes
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


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
===================
|||

||Synonyms
==========
|||

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

||RDF mapping
=============
|||

||GSIM mapping
==============
|||


Note:
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.


Note:
Purpose:
The Data Dictionary View provides the limited information on a data file structure including: the name of the data file, name of variable, physical location (order) of variable, type of variable (character, numeric, etc.), variable label, variable universe/population, substantive (valid) and sentinel (invalid) values with labels if appropriate, and variable concept. 

Use Cases:
This is a core section of most codebooks as well as often being supplied as a structured document as import to various statistical package set-up files.

Target Audience:
Creators of data files for access and distributors.

Included Classes:
Access, AttributeRole, Category, CategorySet, Code, CodeItem, CodeList, Concept, Coverage DataPoint, DataRecord, DataStore, Datum, FundingInformation, IdentifierRole, Individual, InstanceVariable, InstanceVariableMapping, Level, LogicalRecordLayout, MeasureRole, Organization, PhysicalLayoutOrder, PhysicalLayoutOrderPairs, Population, RecordRelation, RectangularLayout (physicalLayout), SegmentByText, SentinalConceptualDomain, SentinelValueDomain, StructureDescription, SpatialCoverage, SubstantiveConceptualDomain, SubstantiveValueDomain, TemporalCoverage, TopicalCoverage, Unit, UnitType, Universe, ValueAndConceptDescription, ValueMapping, Viewpoint

Restricted Classes: 
The following classes contain relationships NOT found in this view. (If the instance of the related class is available in another functional view or other DDI store it may be identified with an external reference):
BoundingBox from SpatialCoverage
RepresentedVariable from InstanceVariable
ConceptualVariable from InstanceVariable

General Documentation:
InstanceVariable contains a relationship to a RepresentedVariable and ConceptualVariable. These two classes have not been included in the Data Dictionary View. The specific content of these two classes are found in the InstanceVariable. Reference may be made instances of these two classes held externally to the Data Dictionary View instance. The entry point for this view is generally the StructureDescription which identifies the DataStore (leading to logical and physical descriptions) and the specific layout information (CSV, Rectangular, etc.).


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 in pair-wise descriptions within Agent Relationships. These may be typed and provided with effective date ranges either as a set of relationships of a specified type or as individual pairs.

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.

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

Included Classes: Agent Registry, Agent Listing, Agent Relationships, Organization, Individual, Machine, Agent Similarity, Agent Similarity Pair, Agent Hierarchy, Agent Hierarchy Pair, Access, Funding Information, External Material, Coverage, Bounding Box. 

Restricted Classes:
All classes are included in their entirety, there are no restrictions.

General Documentation:
The primary class is the Agent Registry which contains Agent Listings and Agent Relationships. Agents may be of any type supported by DDI at the time of this release. Agent Relationships are described by Agent Similarity specified with Agent Similarity Pair (unordered pair of agents) or Agent Hierarchy specified with Agent Hierarchy Pair (ordered pair reflecting a hierarchical relationship between the agents). The Functional View includes the standard document description and Access, Coverage,  Funding Information, External Materials, and Bounding Box classes have been added to support a full description of the instance to support discovery and access.


# t_projectroles

Description:
Define and model the application structure


Notes:
Define and communicate application architecture


# t_requiretypes

Description:
System will display in a specified format

Notes:
Information will be displayed in a particular way


Notes:
The system must meet some performance criteria


Notes:
The system will allow the user(s) to print out some artifact as required by the specification.


Notes:
The system will have the facility to produce a report as required


Notes:
The system will validate a specific rule as supplied in the business requirements


# t_scenariotypes

Notes:
Path of execution that includes exceptional conditions.


Notes:
The standard execution path with no exceptions


# t_stereotypes

Description:
A classifier whose instances represent a flow


Description:
Source class will be notified when an event occurs in target


Description:
A worker who directly interacts with actors outside the system


Description:
Passive class accessed and manipulated by workers


Description:
A worker that interacts with other workers and entities inside the system.


Description:
An abstraction of a human that works within the system.


Description:
Contains business process objects, work units, organization units and relationships


Description:
Subsystem corresponding to an organizational unit of the actual business


Description:
Specifies an element that is at the system boundary (e.g.. User Interface)


Description:
A class that represents a client based web page


Description:
Specifies an element that controls the work and lifetimes of other objects


Description:
Specifies a persistent element mainly concerned with managing its own state


Description:
An event may be thrown or caught by operation


Description:
A class that represents a html frame set


Description:
Implementation of a class in some programming language


Description:
A collection of operations that specify a service of a class or component


Description:
A classifier whose objects are all children of a given parent


Description:
A library of subroutines/functions for web pages


Description:
A class that represents a server based web page


Description:
Specifies an asynchronous stimulus communicated amongst instances


Description:
The classifier is a stereotype that may be applied to other elements


Description:
A class that represents a database table


Description:
A classifier whose instances represent a lightweight flow of control


Description:
An abstract class specifying the structure but not implementation of a set of objects


Description:
A class whose attributes and operations are all class-scoped


Description:
A classifier whose objects are all classes


Description:
Specifies a desired feature, property or behavior of system


Description:
Specifies a contract by or an obligation of a class


Description:
Component represents a document containing source code


Description:
A component that represents a database table


Description:
Constrain must always hold for associated element


Description:
A constraint must hold after the invocation of an element


Description:
A constraint that must hold before an element is invoked


Description:
Public contents of target are accessible to namespace of source


Description:
Source instantiates target template using given parameters


Description:
Source is given special visibility of target


Description:
Public contents of target are imported into source namespace


Description:
The source object is an instance of the target


Description:
Operations on the source class create instances of the target class


Description:
Source is at a finer degree of abstraction than source


Description:
The target is an historical ancestor of source


Description:
The semantics of the source depend on the public part of the target


Description:
Child inherits implementation of parent but does not support its interfaces


Description:
A GUI element that forces user selection


Description:
A GUI element for grouping other controls


Description:
A List of Information with an expandable text field


Description:
A List of Information with a tree structure


Description:
Corresponding object is visible because of enclosing scope


Description:
The corresponding object is visible in local scope


Description:
The corresponding element is visible because it is a parameter


Description:
The corresponding object is visible because it is the dispatcher


Description:
Target is same as source but later in time


Description:
Target is exact but independent copy of source


Description:
Contains analysis classes - entities, boundaries and control elements


Description:
Contains implementation subsystems and/or components and relationships


Description:
Specifies the services offered to the users


Description:
A class that represents a personal computer


Description:
A class that represents a storage device


Description:
A Check constraint to enforce domain integrity


Description:
A trigger which executes automatically when an UPDATE, INSERT, or DELETE statement is issued


Description:
A Unique constraint to enforce the integrity of a database automatically


Description:
Package is a view of another concrete package


Description:
A semantically closed abstraction of a system


Description:
A package serves as a proxy for the public contents of another package


Description:
A grouping of elements that constitute a specification of behavior offered by other contained elements


Description:
A package representing the entire system being modeled


Description:
Communication between actor and use case


Description:
Target use case extends the source at a given extension point


Description:
Source use case explicitly includes the behavior of target


# t_tcf

Description:
Response or throughput performance objectives


Description:
Special user training faciities are required


