XML Schema Tag Library -- Version 2.1

<dataDscr> 4.0  Variable Description

Description: Description of variables.

<varGrp> 4.1  Variable Group

Description:

A group of variables that may share a common subject, arise from the interpretation of a single question, or are linked by some other factor.

Variable groups are created this way in order to permit variables to belong to multiple groups, including multiple subject groups such as a group of variables on sex and income, or to a subject and a multiple response group, without causing overlapping groups. Variables that are linked by use of the same question need not be identified by a Variable Group element because they are linked by a common unique question identifier in the Variable element. Note that as a result of the strict sequencing required by XML, all Variable Groups must be marked up before the Variable element is opened. That is, the mark-up author cannot mark up a Variable Group, then mark up its constituent variables, then mark up another Variable Group.

The "type" attribute refers to the general type of grouping of the variables, e.g., subject, multiple response.

Specific variable groups, included within the "type" attribute, are:

Section: Questions which derive from the same section of the questionnaire, e.g., all variables located in Section C.

Multiple response: Questions where the respondent has the opportunity to select more than one answer from a variety of choices, e.g., what newspapers have you read in the past month (with the respondent able to select up to five choices).

Grid: Sub-questions of an introductory or main question but which do not constitute a multiple response group, e.g., I am going to read you some events in the news lately and you tell me for each one whether you are very interested in the event, fairly interested in the fact, or not interested in the event.

Display: Questions which appear on the same interview screen (CAI) together or are presented to the interviewer or respondent as a group.

Repetition: The same variable (or group of variables) which are repeated for different groups of respondents or for the same respondent at a different time.

Subject: Questions which address a common topic or subject, e.g., income, poverty, children.

Version: Variables, often appearing in pairs, which represent different aspects of the same question, e.g., pairs of variables (or groups) which are adjusted/unadjusted for inflation or season or whatever, pairs of variables with/without missing data imputed, and versions of the same basic question.

Iteration: Questions that appear in different sections of the data file measuring a common subject in different ways, e.g., a set of variables which report the progression of respondent income over the life course.

Analysis: Variables combined into the same index, e.g., the components of a calculation, such as the numerator and the denominator of an economic statistic.

Pragmatic: A variable group without shared properties.

Record: Variable from a single record in a hierarchical file.

File: Variable from a single file in a multifile study.

Randomized: Variables generated by CAI surveys produced by one or more random number variables together with a response variable, e.g, random variable X which could equal 1 or 2 (at random) which in turn would control whether Q.23 is worded "men" or "women", e.g., would you favor helping [men/women] laid off from a factory obtain training for a new job?

Other: Variables which do not fit easily into any of the categories listed above, e.g., a group of variables whose documentation is in another language.

The "var" attribute is used to reference all the constituent variable IDs in the group.

The "varGrp" attribute is used to reference all the subsidiary variable groups which nest underneath the current varGrp. This allows for encoding of a hierarchical structure of variable groups.

The attribute "name" provides a name, or short label, for the group.

The "sdatrefs" are summary data description references that record the ID values of all elements within the summary data description section of the Study Description that might apply to the group. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the group. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).

The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Section 2.5 or Section 5.0 that pertain to this variable group.

The "access" attribute records the ID values of all elements in Section 2.4 of the document that describe access conditions for this variable group.

<labl> 4.1.1  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<txt> 4.1.2  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.1.3  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<defntn> 4.1.4  Definition

Description: Rationale for why the group was constituted in this way.

Example(s):

<varGrp><defntn>The following eight variables were only asked in Ghana.</defntn></varGrp>
<nCubeGrp><defntn>The following four nCubes form a single presentation table.</defntn></nCubeGrp>

<universe> 4.1.5  Universe

Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.

Example(s):

<universe clusion="I">Individuals 15-19 years of age. </universe> 

<universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe> 

<txt> 4.1.5.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.1.5.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<notes> 4.1.6  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<nCubeGrp> 4.2  nCube Group

Description:

A group of nCubes that may share a common subject, arise from the interpretation of a single question, or are linked by some other factor. This element makes it possible to identify all nCubes derived from a simple presentation table, and to provide the original table title and universe, as well as reference the source. Specific nesting patterns can be described using the attribute nCubeGrp.

nCube groups are also created this way in order to permit nCubes to belong to multiple groups, including multiple subject groups, without causing overlapping groups. nCubes that are linked by the same use of the same variable need not be identified by an nCubeGrp element because they are already linked by a common variable element. Note that as a result of the strict sequencing required by XML, all nCube Groups must be marked up before the Variable element is opened. That is, the mark-up author cannot mark up a nCube Group, then mark up its constituent nCubes, then mark up another nCube Group.

The "type" attribute refers to the general type of grouping of the nCubes. Specific nCube Groups, included within the 'type' attribute, are:

Display: nCubes that are part of the same presentation table.

Subject: nCubes that address a common topic or subject, e.g., income, poverty, children.

Iteration: nCubes that appear in different sections of the data file measuring a common subject in different ways, e.g., using different universes, units of measurement, etc.

Pragmatic: An nCube group without shared properties.

Record: nCubes from a single record in a hierarchical file.

File: nCube from a single file in a multifile study.

Other: nCubes that do not fit easily into any of the categories listed above, e.g., a group of nCubes whose documentation is in another language.

The "nCube" attribute is used to reference all the IDs of the nCubes belonging to the group.

The "nCubeGrp" attribute is used to reference all the subsidiary nCube groups which nest underneath the current nCubeGrp. This allows for encoding of a hierarchical structure of nCube groups.

The attribute "name" provides a name, or short label, for the group.

The "sdatrefs" are summary data description references that record the ID values of all elements within the summary data description section of the Study Description that might apply to the group. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the group. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).

The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Section 2.5 or Section 5.0 that pertain to this nCube group.

The "access" attribute records the ID values of all elements in Section 2.4 of the document that describe access conditions for this nCube group.

<labl> 4.2.1  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<txt> 4.2.2  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.2.3  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<defntn> 4.2.4  Definition

Description: Rationale for why the group was constituted in this way.

Example(s):

<varGrp><defntn>The following eight variables were only asked in Ghana.</defntn></varGrp>
<nCubeGrp><defntn>The following four nCubes form a single presentation table.</defntn></nCubeGrp>

<universe> 4.2.5  Universe

Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.

Example(s):

<universe clusion="I">Individuals 15-19 years of age. </universe> 

<universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe> 

<txt> 4.2.5.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.2.5.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<notes> 4.2.6  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<var> 4.3  Variable

Description:

This element describes all of the features of a single variable in a social science data file. It includes the following attributes:

The attribute "name" usually contains the so-called "short label" for the variable, limited to eight characters in many statistical analysis systems such as SAS or SPSS.

The attribute "wgt" indicates whether the variable is a weight.

The attribute "wgt-var" references the weight variable(s) for this variable.

The attribute "qstn" is a reference to the question ID for the variable.

The attribute "files" is the IDREF identifying the file(s) to which the variable belongs.

The attribute "vendor" is the origin of the proprietary format and includes SAS, SPSS, ANSI, and ISO.

The attribute "dcml" refers to the number of decimal points in the variable.

The attribute "intrvl" indicates the interval type; options are discrete or continuous.

The "rectype" attribute refers to the record type to which the variable belongs.

The "sdatrefs" are summary data description references which record the ID values of all elements within the summary data description section of the Study Description which might apply to the variable. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the variable. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).

The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements within Other Study Description Materials or Other Study-Related Materials that pertain to this variable.

The attribute "access" records the ID values of all elements in the Data Access section that describe access conditions for this variable.

The "aggrMeth" attribute indicates the type of aggregation method used, for example 'sum', 'average', 'count'.

The attribute "measUnit" records the measurement unit, for example 'km', 'miles', etc.

The "scale" attribute records unit of scale, for example 'x1', 'x1000', etc.

The attribute "origin" records the point of origin for anchored scales.

The "nature" attribute records the nature of the variable, whether it is 'nominal', 'ordinal', 'interval', or 'ratio'.

The attribute "additivity" records type of additivity, such as 'stock', 'flow', 'non-additive'.

The attribute "temporal" indicates whether the variable relays time-related information.

The "geog" attribute indicates whether the variable relays geographic information.

The attribute "geoVocab" records the coding scheme used in the variable.

The attribute "catQnty" records the number of categories found in the variable, and is used primarily for aggregate data files for verifying cell counts in nCubes.

<location> 4.3.1  Location

Description: This is an empty element containing only the attributes listed below. Attributes include "StartPos" (starting position of variable), "EndPos" (ending position of variable), "width" (number of columns the variable occupies), "RecSegNo" (the record segment number, deck or card number the variable is located on), and "fileid", an IDREF link to the fileDscr element for the file that this location is within (this is necessary in cases where the same variable may be coded in two different files, e.g., a logical record length type file and a card image type file). Note that if there is no width or ending position, then the starting position should be the ordinal position in the file, and the file would be described as free-format. The attribute "locMap" is an IDREF to the element locMap and serves as a pointer to indicate that the location information for the nCube's cells (aggregate data) is located in that section.

Example(s):

<var><location StartPos="55" EndPos="57" width="3" RecSegNo="2" fileid="CARD-IMAGE" ></location>

<location StartPos="167" EndPos="169" fileid="LRECL"></location></var> 

<nCube><location locMap="LM"/></nCube>
                    

<labl> 4.3.2  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<imputation> 4.3.3  Imputation

Description: According to the Statistical Terminology glossary maintained by the National Science Foundation, this is "the process by which one estimates missing values for items that a survey respondent failed to provide," and if applicable in this context, it refers to the type of procedure used. When applied to an nCube, imputation takes into consideration all of the dimensions that are part of that nCube.

Example(s):

<var><imputation>This variable contains values that were derived by substitution.</imputation></var> 
                    

<security> 4.3.4  Security

Description: Provides information regarding levels of access, e.g., public, subscriber, need to know. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.

Example(s):

<var><security date="1998-05-10"> This variable has been recoded for reasons of confidentiality.  
Users should contact the archive for information on obtaining access.</security></var> 

<var><security date="1998-05-10">Variable(s) within this nCube have been recoded for reasons of 
confidentiality.  Users should contact the archive for information on obtaining access.</security></var> 
                    

<embargo> 4.3.5  Embargo

Description:

Provides information on variables/nCubes which are not currently available because of policies established by the principal investigators and/or data producers. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. An "event" attribute is provided to specify "notBefore" or "notAfter" ("notBefore" is the default). A "format" attribute is provided to ensure that this information will be machine-processable, and specifies a format for the embargo element.

The "format" attribute could be used to specify other conventions for the way that information within the embargo element is set out, if conventions for encoding embargo information were established in the future.

Example(s):

<var><embargo event="notBefore" date="2001-09-30"> The data associated with this variable/nCube 
will not become available until September 30, 2001, because of embargo provisions established by the 
data producers.</embargo></var> 
                    

<respUnit> 4.3.6  Response Unit

Description: Provides information regarding who provided the information contained within the variable/nCube, e.g., respondent, proxy, interviewer.

Example(s):

<var><respUnit>Head of household</respUnit></var> 

<nCube><respUnit>Head of household</respUnit></nCube>
                    

<anlysUnit> 4.3.7  Analysis Unit

Description: Provides information regarding whom or what the variable/nCube describes.

Example(s):

<var><anlysUnit> This variable reports election returns at the constituency level. </anlysUnit></var> 

<nCube><anlysUnit>Household</anlysUnit></nCube>
                    

<txt> 4.3.7.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.3.7.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<qstn> 4.3.8  Question

Description: The question element may have mixed content. The element itself may contain text for the question, with the subelements being used to provide further information about the question. Alternatively, the question element may be empty and only the subelements used. The element has a unique question ID attribute which can be used to link a variable with other variables where the same question has been asked. This would allow searching for all variables that share the same question ID, perhaps because the questions was asked several times in a panel design. The "ID" attribute contains a unique identifier for the question. "Var" references the ID(s) of the variable(s) relating to the question. The attribute "seqNo" refers to the sequence number of the question. The attribute "sdatrefs" may be used to reference elements in the summary data description section of the Study Description which might apply to this question. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

Example(s):

<var><qstn ID="Q125">When you get together with your friends, would you say you discuss political 
matters frequently, occasionally, or never?</qstn></var> 

                    

<preQTxt> 4.3.8.1  PreQuestion Text

Description: Text describing a set of conditions under which a question might be asked.

Example(s):

<var><qstn><preQTxt>For those who did not go away on a holiday of four days or more in 1985... 
</preQTxt></qstn></var> 
                    

<qstnLit> 4.3.8.2  Literal Question

Description: Text of the actual, literal question asked.

Example(s):

<var><qstn><qstnLit>Why didn't you go away in 1985?</qstnLit></qstn></var> 
                    

<postQTxt> 4.3.8.3  PostQuestion Text

Description: Text describing what occurs after the literal question has been asked.

Example(s):

<var><qstn><postQTxt>The next set of questions will ask about your financial situation.</postQTxt> 
</qstn></var> 
                    

<forward> 4.3.8.4  Forward Progression

Description: Contains a reference to IDs of possible following questions. The "qstn" IDREFS may be used to specify the question IDs.

Example(s):

<var><qstn><forward qstn="Q120 Q121 Q122 Q123 Q124"> If yes, please ask questions 120-124.
</forward></qstn></var> 
                    

<backward> 4.3.8.5  Backflow

Description: Contains a reference to IDs of possible preceding questions. The "qstn" IDREFS may be used to specify the question IDs.

Example(s):

<var><qstn><backward qstn="Q12 Q13 Q14 Q15">For responses on a similar topic, see questions 
12-15.</backward></qstn> </var> 

<var><qstn><backward qstn="Q143"> </backward></qstn> </var> 
                    

<ivuInstr> 4.3.8.6  Interviewer Instructions

Description: Specific instructions to the individual conducting an interview.

Example(s):

<var><qstn><ivuInstr> Please prompt the respondent if they are reticent to answer this question.
</ivuInstr></qstn></var> 
                    

<valrng> 4.3.9  Range of Valid Data Values

Description: Values for a particular variable that represent legitimate responses.

Example(s):

<valrng><range min="1" max="3" /></valrng>

<valrng><item VALUE="1" /><item VALUE="2" /><item VALUE="3" /></valrng>
                    

<key> 4.3.9.1  Range Key

Description: This element permits a listing of the category values and labels. While this information is coded separately in the Category element, there may be some value in having this information in proximity to the range of valid and invalid values. A table is permissible in this element.

Example(s):

<valrng>
<range UNITS="INT" maxExclusive="95" min="05" max="80"> </range> 
<key> 

05 (PSU) Parti Socialiste Unifie et extreme gauche (Lutte Ouvriere) [United Socialists and extreme left 
(Workers Struggle)] 

50 Les Verts [Green Party] 

80 (FN) Front National et extreme droite [National Front and extreme right] 

</key>
 </valrng> 

<notes> 4.3.9.2  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<invalrng> 4.3.10  Range of Invalid Data Values

Description: Values for a particular variable that represent missing data, not applicable responses, etc.

Example(s):

<invalrng> 
<range UNITS="INT" min="98" max="99"> 
</range> 
<key> 
98 DK 
99 Inappropriate 
</key> </invalrng> 

<key> 4.3.10.1  Range Key

Description: This element permits a listing of the category values and labels. While this information is coded separately in the Category element, there may be some value in having this information in proximity to the range of valid and invalid values. A table is permissible in this element.

Example(s):

<valrng>
<range UNITS="INT" maxExclusive="95" min="05" max="80"> </range> 
<key> 

05 (PSU) Parti Socialiste Unifie et extreme gauche (Lutte Ouvriere) [United Socialists and extreme left 
(Workers Struggle)] 

50 Les Verts [Green Party] 

80 (FN) Front National et extreme droite [National Front and extreme right] 

</key>
 </valrng> 

<notes> 4.3.10.2  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<undocCod> 4.3.11  List of Undocumented Codes

Description: Values whose meaning is unknown.

Example(s):

<var><undocCod>Responses for categories 9 and 10 are unavailable.</undocCod></var> 
                    

<universe> 4.3.12  Universe

Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.

Example(s):

<universe clusion="I">Individuals 15-19 years of age. </universe> 

<universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe> 

<txt> 4.3.12.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.3.12.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<TotlResp> 4.3.13  Total Responses

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

Example(s):

<var><TotlResp>1,056</TotlResp></var>

OR

<var><TotlResp>There are only 725 responses to this question since it was not asked in Tanzania.</TotlResp></var> 
                    

<sumStat> 4.3.14  Summary Statistics

Description:

One or more statistical measures that describe the responses to a particular variable and may include one or more standard summaries, e.g., minimum and maximum values, median, mode, etc. The attribute "wgtd" indicates whether the statistics are weighted or not. The "weight" attribute is an IDREF(S) to the weight element(s) in the study description.

The attribute "type" denotes the type of statistics being shown: mean, median, mode, valid cases, invalid cases, minimum, maximum, or standard deviation.

Example(s):

<var><sumStat type="min">0</sumStat></var> 

<var><sumStat type="max">9</sumStat></var> 

<var><sumStat type="median">4</sumStat></var> 
                    

<txt> 4.3.15  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<stdCatgry> 4.3.16  Standard Categories

Description: Standard category codes used in the variable, like industry codes, employment codes, or social class codes. The attribute "date" is provided to indicate the version of the code in place at the time of the study. The attribute "URI" is provided to indicate a URN or URL that can be used to obtain an electronic list of the category codes.

Example(s):

<var><stdCatgry date="1981" source="producer">U. S. Census of Population and Housing, Classified 
Index of Industries and Occupations </stdCatgry></var> 
                    

<catgryGrp> 4.3.17  Category Group

Description: A description of response categories that might be grouped together. The attribute "missing" indicates whether this category group contains missing data or not. The attribute "missType" is used to specify the type of missing data, e.g., inap., don't know, no answer, etc. The attribute catGrp is used to indicate all the subsidiary category groups which nest underneath the current category group. This allows for the encoding of a hierarchical structure of category groups. The "levelno" attribute allows the addition of a level number, and "levelnm" allows the addition of a level name to the category group. The completeness attribute ("compl") should be set to "false" if the category group is incomplete (not a complete aggregate of all sub-nodes or children). The exclusiveness attribute ("excls") should be set to "false" if the category group can appear in more than one place in the classification hierarchy.

<labl> 4.3.17.1  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<catStat> 4.3.17.2  Category Level Statistic

Description: May include frequencies, percentages, or crosstabulation results. This field can contain one of the following: 1. textual information (e.g., PCDATA), or 2. non-parseable character data (e.g., the statistics), or 3. some other form of external information (table, image, etc.) In case 1, the tag can be used to mark up character data; tables can also be included in the actual markup. In cases 2 or 3, the element can be left empty and the "URI" attribute used to refer to the external object containing the information. The attribute "type" indicates the type of statistics presented - frequency, percent, or crosstabulation.

Example(s):

<var><catgryGrp ><catStat type='freq'>256 </catStat></catgryGrp></var> 
                    

<txt> 4.3.17.3  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<catgry> 4.3.18  Category

Description:

A description of a particular response.

The attribute "missing" indicates whether this category group contains missing data or not.

The attribute "missType" is used to specify the type of missing data, e.g., inap., don't know, no answer, etc.

The attribute "country" allows for the denotation of country-specific category values.

The "sdatrefs" attribute records the ID values of all elements within the summary data decription that apply to this category.

The exclusiveness attribute ("excls") should be set to "false" if the category can appear in more than one place in the classification hierarchy.

The attribute "catgry" is an IDREF referencing any child categories of this category element. Used to capture nested hierarchies of categories.

The attribute "level" is an IDREF referencing the catLevel ID in which this category exists.

Example(s):

						
                        <catlevel ID="Level1" levelnm="Broader sectors" />
						<catlevel ID="Level2" levelnm="Narrower sectors" />
						<catlevel ID="Level3" levelnm="Occupations" />
                        <!-- ... -->
						<catgry ID="C1" catgry="C2" Level="Level1">
							<catValu>0</catValu>
							<labl> Management, professional and related occupations </labl>
						</catgry>
						<catgry ID="C2" catgry="C3, C4" Level="Level2">
							<catValu>01</catValu>
							<labl> Management occupations</labl>
						</catgry>
						<catgry ID="C3" Level="Level3">
							<catValu>011</catValu>
							<labl> Top executives </labl>
						</catgry>
						<catgry ID="C4" Level="Level3">
							<catValu>012</catValu>
							<labl> Financial managers</labl>
						</catgry>
						
					

<catValu> 4.3.18.1  Category Value

Description: The explicit response.

Example(s):

<var><catgry missing="Y" missType="inap"><catValu>9 </catValu> </catgry></var> 
                    

<labl> 4.3.18.2  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<txt> 4.3.18.3  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<catStat> 4.3.18.4  Category Level Statistic

Description: May include frequencies, percentages, or crosstabulation results. This field can contain one of the following: 1. textual information (e.g., PCDATA), or 2. non-parseable character data (e.g., the statistics), or 3. some other form of external information (table, image, etc.) In case 1, the tag can be used to mark up character data; tables can also be included in the actual markup. In cases 2 or 3, the element can be left empty and the "URI" attribute used to refer to the external object containing the information. The attribute "type" indicates the type of statistics presented - frequency, percent, or crosstabulation.

Example(s):

<var><catgryGrp ><catStat type='freq'>256 </catStat></catgryGrp></var> 
                    

<mrow> 4.3.18.5  Mathematical Row

Description: This element is a wrapper containing the presentation expression mi. It creates a single string without spaces consisting of the individual elements described within it. It can be used to create a single variable by concatenating other variables into a single string. It is used to create linking variables composed of multiple non-contiguous parts, or to define unique strings for various category values of a single variable.

<mi> 4.3.18.5.1  Mathematical Identifier

Description: Token element containing the smallest unit in the mrow that carries meaning.

<codInstr> 4.3.19  Coder Instructions

Description: Any special instructions to those who converted information from one form to another for a particular variable. This might include the reordering of numeric information into another form or the conversion of textual information into numeric information.

Example(s):

<var><codInstr>Use the standard classification tables to present responses to the question:  
What is your occupation? into numeric codes.</codInstr></var> 
                    

<verStmt> 4.3.20  Version Statement

Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.

Example(s):

<verStmt><version type="version" date="1999-01-25">Second version</version>
                    

<version> 4.3.20.1  Version

Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.

Example(s):

<version type="edition" date="1999-01-25">Second ICPSR Edition</version> 

<var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> 

<nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube> 

<verResp> 4.3.20.2  Version Responsibility Statement

Description: The organization or person responsible for the version of the work.

Example(s):

<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> 

<verResp>Inter-university Consortium for Political and Social  Research</verResp> 

<var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> 

<nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube> 

<notes> 4.3.20.3  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<concept> 4.3.21  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<derivation> 4.3.22  Derivation

Description: Used only in the case of a derived variable, this element provides both a description of how the derivation was performed and the command used to generate the derived variable, as well as a specification of the other variables in the study used to generate the derivation. The "var" attribute provides the ID values of the other variables in the study used to generate this derived variable.

<drvdesc> 4.3.22.1  Derivation Description

Description: A textual description of the way in which this variable was derived.

Example(s):

<var><derivation><drvdesc> VAR215.01 "Outcome of first pregnancy" (1988 NSFG=VAR611 PREGOUT1) 
If R has never been pregnant (VAR203 PREGNUM EQ 0) then OUTCOM01 is blank/inapplicable. Else, OUTCOM01 
is transferred from VAR225 OUTCOME for R's 1st pregnancy. </drvdesc></derivation></var> 

                    

<drvcmd> 4.3.22.2  Derivation Command

Description: The actual command used to generate the derived variable. The "syntax" attribute is used to indicate the command language employed (e.g., SPSS, SAS, Fortran, etc.)

Example(s):

<var><derivation><drvcmd syntax="SPSS" >RECODE V1 TO V3 (0=1) (1=0) (2=-1) INTO DEFENSE WELFARE 
HEALTH. </drvcmd></derivation></var> 
                    

<varFormat> 4.3.23  Variable Format

Description: The technical format of the variable in question. Attributes for this element include: "type," which indicates if the variable is character or numeric; "formatname," which in some cases may provide the name of the particular, proprietary format actually used; "schema," which identifies the vendor or standards body that defined the format (acceptable choices are SAS, SPSS, IBM, ANSI, ISO, XML-data or other); "category," which describes what kind of data the format represents, and includes date, time, currency, or "other" conceptual possibilities; and "URI," which supplies a network identifier for the format definition.

Example(s):

<var><varFormat type="numeric" schema="SAS" formatname="DATE" category="date" >The number in this 
variable is stored in the form 'ddmmmyy' in SAS format. </varFormat></var> 

<var><varFormat type="numeric" formatname="date.iso8601" schema="XML-Data" category="date" 
URI="http://www.w3.org/TR/1998/NOTE-XML-data/">19541022 </varFormat></var> 
                    

<geoMap> 4.3.24  Geographic Map

Description: This element is used to point, using a "URI" attribute, to an external map that displays the geography in question. The "levelno" attribute indicates the level of the geographic hierarchy relayed in the map. The "mapformat" attribute indicates the format of the map.

<catLevel> 4.3.25  Category Level

Description:  Used to describe the levels of the category hierarchy. Note that we do not indicate nesting levels or roll-up structures here. This is done to be able to support ragged hierarchies.

Example(s):

						
						<catlevel ID="Level1" levelnm="Broader sectors" />
						<catlevel ID="Level2" levelnm="Narrower sectors" />
						<catlevel ID="Level3" levelnm="Occupations" />
						
					

<notes> 4.3.26  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<nCube> 4.4  nCube

Description:

Describes the logical structure of an n-dimensional array, in which each coordinate intersects with every other dimension at a single point. The nCube has been designed for use in the markup of aggregate data. This element includes the following attributes:

The attribute "name" includes a short label for the nCube. Following the rules of many statistical analysis systems such as SAS and SPSS, names are usually up to eight characters long.

The "sdatrefs" are summary data description references which record the ID values of all elements within the summary data description section of the Study Description which might apply to the nCube. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

The "methrefs" are methodology and processing references which record the ID values of all elements within the study methodology and processing section of the Study Description which might apply to the nCube. These elements include information on data collection and data appraisal (e.g., sampling, sources, weighting, data cleaning, response rates, and sampling error estimates).

The "pubrefs" attribute provides a link to publication/citation references and records the ID values of all citations elements in Other Study Description Materials or Other Study-Related Materials that pertain to this nCube.

The "access" attribute records the ID values of all elements in the Data Access section that describe access conditions for this nCube. The "dmnsQnty" attribute notes the number of dimensions in the nCube. The "cellQnty" attribute indicates the total number of cells in the nCube.

<location> 4.4.1  Location

Description: This is an empty element containing only the attributes listed below. Attributes include "StartPos" (starting position of variable), "EndPos" (ending position of variable), "width" (number of columns the variable occupies), "RecSegNo" (the record segment number, deck or card number the variable is located on), and "fileid", an IDREF link to the fileDscr element for the file that this location is within (this is necessary in cases where the same variable may be coded in two different files, e.g., a logical record length type file and a card image type file). Note that if there is no width or ending position, then the starting position should be the ordinal position in the file, and the file would be described as free-format. The attribute "locMap" is an IDREF to the element locMap and serves as a pointer to indicate that the location information for the nCube's cells (aggregate data) is located in that section.

Example(s):

<var><location StartPos="55" EndPos="57" width="3" RecSegNo="2" fileid="CARD-IMAGE" ></location>

<location StartPos="167" EndPos="169" fileid="LRECL"></location></var> 

<nCube><location locMap="LM"/></nCube>
                    

<labl> 4.4.2  Label

Description: A short description of the parent element. In the variable label, the length of this phrase may depend on the statistical analysis system used (e.g., some versions of SAS permit 40-character labels, while some versions of SPSS permit 120 characters), although the DDI itself imposes no restrictions on the number of characters allowed. A "level" attribute is included to permit coding of the level to which the label applies, i.e. record group, variable group, variable, category group, category, nCube group, nCube, or other study-related materials. The "vendor" attribute was provided to allow for specification of different labels for use with different vendors' software. The attribute "country" allows for the denotation of country-specific labels. The "sdatrefs" attribute records the ID values of all elements within the Summary Data Description section of the Study Description that might apply to the label. These elements include: time period covered, date of collection, nation or country, geographic coverage, geographic unit, unit of analysis, universe, and kind of data.

<txt> 4.4.3  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<universe> 4.4.4  Universe

Description: The group of persons or other elements that are the object of research and to which any analytic results refer. Age, nationality, and residence commonly help to delineate a given universe, but any of a number of factors may be involved, such as sex, race, income, veteran status, criminal convictions, etc. The universe may consist of elements other than persons, such as housing units, court cases, deaths, countries, etc. In general, it should be possible to tell from the description of the universe whether a given individual or element (hypothetical or real) is a member of the population under study. A "level" attribute is included to permit coding of the level to which universe applies, i.e., the study level, the file level (if different from study), the record group, the variable group, the nCube group, the variable, or the nCube level. The "clusion" attribute provides for specification of groups included (I) in or excluded (E) from the universe. If all the variables/nCubes described in the data documentation relate to the same population, e.g., the same set of survey respondents, this element would be unnecessary at data description level. In this case, universe can be fully described at the study level.

Example(s):

<universe clusion="I">Individuals 15-19 years of age. </universe> 

<universe clusion="E">Individuals younger than 15 and older than 19 years of age.</universe> 

<txt> 4.4.4.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.4.4.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<imputation> 4.4.5  Imputation

Description: According to the Statistical Terminology glossary maintained by the National Science Foundation, this is "the process by which one estimates missing values for items that a survey respondent failed to provide," and if applicable in this context, it refers to the type of procedure used. When applied to an nCube, imputation takes into consideration all of the dimensions that are part of that nCube.

Example(s):

<var><imputation>This variable contains values that were derived by substitution.</imputation></var> 
                    

<security> 4.4.6  Security

Description: Provides information regarding levels of access, e.g., public, subscriber, need to know. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the date attribute.

Example(s):

<var><security date="1998-05-10"> This variable has been recoded for reasons of confidentiality.  
Users should contact the archive for information on obtaining access.</security></var> 

<var><security date="1998-05-10">Variable(s) within this nCube have been recoded for reasons of 
confidentiality.  Users should contact the archive for information on obtaining access.</security></var> 
                    

<embargo> 4.4.7  Embargo

Description:

Provides information on variables/nCubes which are not currently available because of policies established by the principal investigators and/or data producers. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute. An "event" attribute is provided to specify "notBefore" or "notAfter" ("notBefore" is the default). A "format" attribute is provided to ensure that this information will be machine-processable, and specifies a format for the embargo element.

The "format" attribute could be used to specify other conventions for the way that information within the embargo element is set out, if conventions for encoding embargo information were established in the future.

Example(s):

<var><embargo event="notBefore" date="2001-09-30"> The data associated with this variable/nCube 
will not become available until September 30, 2001, because of embargo provisions established by the 
data producers.</embargo></var> 
                    

<respUnit> 4.4.8  Response Unit

Description: Provides information regarding who provided the information contained within the variable/nCube, e.g., respondent, proxy, interviewer.

Example(s):

<var><respUnit>Head of household</respUnit></var> 

<nCube><respUnit>Head of household</respUnit></nCube>
                    

<anlysUnit> 4.4.9  Analysis Unit

Description: Provides information regarding whom or what the variable/nCube describes.

Example(s):

<var><anlysUnit> This variable reports election returns at the constituency level. </anlysUnit></var> 

<nCube><anlysUnit>Household</anlysUnit></nCube>
                    

<txt> 4.4.9.1  Descriptive Text

Description: Lengthier description of the parent element. The attribute "level" indicates the level to which the element applies. The attribute "sdatrefs" allows pointing to specific dates, universes, or other information encoded in the study description.

Example(s):

<varGrp type="subject"><txt>The following five variables refer to respondent attitudes toward 
national environmental policies: air pollution, urban sprawl, noise abatement, carbon dioxide emissions, 
and nuclear waste.</txt></varGrp> 

<nCubeGrp type="subject"><txt>The following four nCubes are grouped to present a cross tabulation of the 
variables Sex, Work experience in 1999, and Income in 1999.</txt></nCubeGrp> 

<var><txt>Total population for the agency for the year reported.</txt></var> 

<catgryGrp><txt>When the respondent indicated his political party reference, his response was coded on a 
scale of 1-99 with parties with a left-wing orientation coded on the low end of the scale and parties 
with a right-wing orientation coded on the high end of the scale.  Categories 90-99 were reserved 
miscellaneous responses.</txt></catgryGrp> 

<catgry><txt>Inap., question not asked in Ireland, Northern Ireland, and Luxembourg.</txt></catgry> 

<nCube><txt>Detailed poverty status for age cohorts over a period of five years, to be used in determining 
program eligibility</txt></nCube> 

<otherMat URI="http://www.icpsr.umich.edu/.."><txt>This is a PDF version of the original questionnaire 
provided by the principal investigator.</txt></otherMat> 

<otherMat><txt>Glossary of Terms. Below are terms that may  prove useful in working with the technical 
documentation for this study.. </txt></otherMat> 

<otherMat><txt>This is a PDF version of the original questionnaire provided by the principal investigator.
</txt></otherMat> 

<concept> 4.4.9.2  Concept

Description: The general subject to which the parent element may be seen as pertaining. This element serves the same purpose as the keywords and topic classification elements, but at the data description level. The "vocab" attribute is provided to indicate the controlled vocabulary, if any, used in the element, e.g., LCSH (Library of Congress Subject Headings), MeSH (Medical Subject Headings), etc. The "vocabURI" attribute specifies the location for the full controlled vocabulary.

Example(s):

<nCubeGrp><concept>Income</concept></nCubeGrp> 

<nCubeGrp><concept vocab="LCSH" vocabURI="http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
more experience</concept></nCubeGrp>

<var><concept>Income</concept></var> 

<var><concept vocab="LCSH" vocabURI= "http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html" source="archive">
SF: 311-312 draft horses</concept></var> 
                    

<verStmt> 4.4.10  Version Statement

Description: Version statement for the work at the appropriate level: marked-up document; marked-up document source; study; study description, other material; other material for study. A version statement may also be included for a data file, a variable, or an nCube.

Example(s):

<verStmt><version type="version" date="1999-01-25">Second version</version>
                    

<version> 4.4.10.1  Version

Description: Also known as release or edition. If there have been substantive changes in the data/documentation since their creation, this statement should be used at the appropriate level. The ISO standard for dates (YYYY-MM-DD) is recommended for use with the "date" attribute.

Example(s):

<version type="edition" date="1999-01-25">Second ICPSR Edition</version> 

<var><verStmt><version type="version" date="1999-01-25">Second version of V25</version></verStmt> </var> 

<nCube><verStmt><version type="version" date="1999-01-25">Second version of N25</version></verStmt> </nCube> 

<verResp> 4.4.10.2  Version Responsibility Statement

Description: The organization or person responsible for the version of the work.

Example(s):

<verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp> 

<verResp>Inter-university Consortium for Political and Social  Research</verResp> 

<var><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></var> 

<nCube><verStmt><verResp>Zentralarchiv fuer Empirische Sozialforschung</verResp></verStmt></nCube> 

<notes> 4.4.10.3  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<purpose> 4.4.11  

Description: Explains the purpose for which a particular nCube was created.

Example(s):

<nCube><purpose>Meets reporting requirements for the Federal Reserve Board</purpose></nCube> 
                    

<dmns> 4.4.12  Dimension

Description: This element defines a variable as a dimension of the nCube, and should be repeated to describe each of the cube's dimensions. The attribute "rank" is used to define the coordinate order (rank="1", rank="2", etc.) The attribute "varRef" is an IDREF that points to the variable that makes up this dimension of the nCube.

<cohort> 4.4.12.1  Cohort

Description: The element cohort is used when the nCube contains a limited number of categories from a particular variable, as opposed to the full range of categories. The attribute "catRef" is an IDREF to the actual category being used. The attribute "value" indicates the actual value attached to the category that is being used.

Example(s):

<dmns><cohort catRef="CV24_1" value="1"></cohort></dmns> 
                    

<range> 4.4.12.1.1  Value Range

Description: This is the actual range of values. The "UNITS" attribute permits the specification of integer/real numbers. The "min" and "max" attributes specify the lowest and highest values that are part of the range. The "minExclusive" and "maxExclusive" attributes specify values that are immediately outside the range. This is an empty element consisting only of its attributes.

Example(s):

For example, x < 1 or 10 <= x < 20 would be expressed as <range maxExclusive="1"/><range min="10" 
maxExclusive="20" />. 

<measure> 4.4.13  Measure

Description: The element measure indicates the measurement features of the cell content: type of aggregation used, measurement unit, and measurement scale. An origin point is recorded for anchored scales, to be used in determining relative movement along the scale. Additivity indicates whether an aggregate is a stock (like the population at a given point in time) or a flow (like the number of births or deaths over a certain period of time). The non-additive flag is to be used for measures that for logical reasons cannot be aggregated to a higher level - for instance, data that only make sense at a certain level of aggregation, like a classification. Two nCubes may be identical except for their measure - for example, a count of persons by age and percent of persons by age. Measure is an empty element that includes the following attributes: "varRef" is an IDREF; "aggrMeth" indicates the type of aggregation method used, for example 'sum', 'average', 'count'; "measUnit" records the measurement unit, for example 'km', 'miles', etc.; "scale" records unit of scale, for example 'x1', 'x1000'; "origin" records the point of origin for anchored scales;"additivity" records type of additivity such as 'stock', 'flow', 'non-additive'.

<notes> 4.4.14  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat> 

<notes> 4.5  Notes and comments

Description:

For clarifying information/annotation regarding the parent element.

The attributes for notes permit a controlled vocabulary to be developed ("type" and "subject"), indicate the "level" of the DDI to which the note applies (study, file, variable, etc.), and identify the author of the note ("resp").

Example(s):

<docDscr><verStmt><notes resp="Jane Smith">Additional information on derived variables  
has been added to this marked-up version of the documentation.</notes></verStmt></docDscr>

<docDscr><citation><notes resp="Jane Smith">This citation was prepared by the archive 
based on information received from the markup authors.</notes></citation></docDscr> 

<docSrc><verStmt><notes resp="Jane Smith">The source codebook was produced from  
original hardcopy materials using  Optical Character Recognition (OCR).</notes><verStmt>
</docSrc> 

<docSrc><notes>A machine-readable version of the source codebook was supplied by the 
Zentralarchiv</notes></docSrc>

<docDscr><notes>This Document Description, or header information, can be used  within an 
electronic resource discovery environment.</notes></docDscr> 

<stdyDscr><verStmt><notes resp="Jane Smith">Data for 1998 have been added to this 
version of the data collection.</notes></verStmt></stdyDscr>

<stdyDscr><citation><notes resp="Jane Smith">This citation was sent to ICPSR by the 
agency depositing the data.</notes></citation></stdyDscr> 

<stdyInfo><notes>Data on employment and income refer to the preceding year, although 
demographic data refer to the time of the survey.</notes></stdyInfo> 

<method><notes>Undocumented codes were found in this data collection. Missing data are 
represented by blanks.</notes></method>

<method><notes>For this collection, which focuses on employment, unemployment, and 
gender equality, data from EUROBAROMETER 44.3: HEALTH CARE ISSUES AND PUBLIC SECURITY, 
FEBRUARY-APRIL 1996 (ICPSR 6752) were merged with an oversample.</notes></method> 

<setAvail><notes> Data from the Bureau of Labor Statistics used in the analyses for the 
final report are not provided as part of this collection.</notes></setAvail> 

<dataAccs><notes>Users should note that this is a beta version of the data. The 
investigators therefore request that users who encounter any problems with the dataset 
contact them at the above address.</notes></dataAccs> 

<fileStrc><notes>The number of arrest records for an individual is dependent on the 
number of arrests an offender had.</notes></fileStrc> 

<fileTxt><verStmt><notes>Data for all previously-embargoed variables are now available 
in  this version of the file.</notes></verStmt></fileTxt> 

<fileDscr><notes>There is a restricted version of this file containing confidential 
information,  access to which is controlled by the principal investigator.</notes>
</fileDscr> 

<varGrp><notes>This variable group was created for the purpose of combining all derived 
variables.</notes></varGrp> 

<varGrp><notes source="archive" resp="John Data">This variable group and all other 
variable groups in this data file were organized according to a schema developed by 
the adhoc advisory committee. </notes></varGrp> 

<nCubeGrp><notes>This nCube Group was created for the purpose of presenting a cross-
tabulation between variables "Tenure" and "Age of householder."</notes></nCubeGrp> 

<valrng><notes subject="political party">Starting with Euro-Barometer 2 the coding of 
this variable has been standardized following an approximate ordering of each country's 
political parties along a "left" to "right" continuum in the first digit of the codes. 
Parties coded 01-39 are generally considered on the "left", those coded 40-49 in the 
"center", and those coded 60-89 on the "right" of the political spectrum. Parties coded 
50-59 cannot be readily located in the traditional meaning of "left" and "right". The 
second digit of the codes is not significant to the "left-right" ordering. Codes 90-99 
contain the response "other party" and various missing data responses. Users may modify 
these codings or part of these codings in order to suit their specific needs. </notes>
</valrng> 

<invalrng><notes>Codes 90-99 contain the response "other party" and various missing 
data responses. </notes></invalrng> 

<var><verStmt><notes>The labels for categories 01 and 02 for this variable, were 
inadvertently switched in the first version of this variable and have now been 
corrected.</notes></verStmt></var> 

<var><notes>This variable was created by recoding location of residence to Census 
regions.</notes></var> 

<nCube><verStmt><notes>The labels for categories 01 and 02 in dimension 1 were 
inadvertently switched in the first version of the cube, and have now been corrected.
</notes></verStmt></nCube> 

<nCube><notes>This nCube was created to meet the needs of local low income programs 
in determining eligibility for federal funds.</notes></nCube> 

<dataDscr><notes>The variables in this study are identical to earlier waves. </notes>
</dataDscr> 

<otherMat><notes>Users should be aware that this questionnaire was modified  during 
the CAI process.</notes></otherMat>