<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>There are tons of XML Unit testing frameworks we can use, it's
just that we never got that far to need them...</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2020-02-05 10:00 a.m., Wackerow,
Joachim wrote:<br>
</div>
<blockquote type="cite"
cite="mid:80d4e7384d344bc49285643ffb79d8f7@gesis.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jay,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">I think MRT is still very weak on the T.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">We would need test cases formalized as XML
and/or RDF. Furthermore, the definitions of constraints for
these use cases would be important. Then, validation on this
secondary level could take place.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> Jay Greenfield
[<a class="moz-txt-link-freetext" href="mailto:nightcleaner@gmail.com">mailto:nightcleaner@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, February 5, 2020 15:54<br>
<b>To:</b> Wackerow, Joachim<br>
<b>Cc:</b> DDI - Structural Reform Group<br>
<b>Subject:</b> Re: [DDI-SRG] [MRT] Open model issues
for decision<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Achim:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Does the production system include a test
suite so we can ascertain whether model changes first break
the usability of the remaining model and then whether model
changes actually work as expected?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">How do we test a model before it is
published?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jay<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Feb 5, 2020, at 9:33 AM,
Wackerow, Joachim <<a
href="mailto:Joachim.Wackerow@gesis.org"
moz-do-not-send="true">Joachim.Wackerow@gesis.org</a>>
wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Here is an additional list. Attached
is a list of all classes and their possible super
classes.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">The identifiable ones are marked in
blue.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">The classes without a super class are
marked in red.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"> </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US">Achim</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"
lang="EN-US"> </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<div>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
class="apple-converted-space"><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> </span></span><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"><a
href="mailto:ddi-srg-bounces@icpsr.umich.edu"
moz-do-not-send="true"><span
style="color:purple">ddi-srg-bounces@icpsr.umich.edu</span></a><span
class="apple-converted-space"> </span>[<a
href="mailto:ddi-srg-bounces@icpsr.umich.edu"
moz-do-not-send="true"><span
style="color:purple">mailto:ddi-srg-bounces@icpsr.umich.edu</span></a>]<span
class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Wackerow,
Joachim<br>
<b>Sent:</b><span
class="apple-converted-space"> </span>Wednesday,
February 5, 2020 13:35<br>
<b>To:</b><span class="apple-converted-space"> </span>DDI
- Structural Reform Group<br>
<b>Subject:</b><span
class="apple-converted-space"> </span>[DDI-SRG]
[MRT] Open model issues for decision</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Here is a list of open model issues.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US"> </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">The goal would be that we either find
today an agreement or we describe the issue and
possible solutions and park the issue.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">I’ll then make changes to the model
according to the agreed decisions.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US"> </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">1.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Leaf classes without attributes and
associations to other classes</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">a.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">ControlStep, ScriptingAgent and
RulesEngine</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:108.0pt">
<p class="MsoNormal" style="text-indent:-108.0pt"><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">i.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Jay: they can be removed</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">b.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Sequence and Service</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:108.0pt">
<p class="MsoNormal" style="text-indent:-108.0pt"><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">i.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Jay: need to remain as is in line
with idea that this is a conceptual/logical model
that some but not all will use for implementation
too (Smile).<span class="apple-converted-space"> </span><br>
Sequence is a container for other
ControlConstructs and because it inherits from
ControlLogic which is reflexive maybe Sequence can
host other ControlLogic and itself.<br>
Service is an idea we would like to finish at
another time.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">c.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Designation</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:108.0pt">
<p class="MsoNormal" style="text-indent:-108.0pt"><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">i.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Ja: Designation is another touchpoint
with Signifier, Sign and Signified</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:108.0pt">
<p class="MsoNormal" style="text-indent:-108.0pt"><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">ii.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Flavio: We are not using Designation
anymore</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:108.0pt">
<p class="MsoNormal" style="text-indent:-108.0pt"><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">iii.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Dan: Designation isn’t really needed
since we have the signification pattern. As a
result, each application of designation, whether
it be a code, term, or other, will be modeled in
the realization. Designation, being a generic
term, probably is not needed.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">d.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">What is the purpose of
UnitSegmentLayout? Does it make sense for future
expansion.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">2.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">PhysicalSegmentLocation has no
attributes, only one association to ValueMapping,
and only one sub class, SegmentByText. Currently
it doesn’t make much sense. Should this be
maintained for future expansion?</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">3.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">The current approach of string types
seems to be too complicated. The structured string
types could be folded into the regular ones.
Furthermore, there are some inconsistencies.<br>
Diagrams on the current approach and the suggested
approach are attached.<span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">4.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Missing identifiers for classes in
DataDescription, Process, and value? of a Code ,
see Jay’s email on “new model version 2020-02-04 /
generated files” from 2020-02-04.<br>
Attached is a list of classes in DataDescription
and Process. The classes which inherit from
Identifable are highlighted.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:36.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">5.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Identification and Annotation.
Identification could be an attribute not a super
class (otherwise “, annotation could be a separate
class.<br>
The current model uses Identifiable and
AnnotatedIdentifiable as super classes. The
Identifable is just “Data-Based Inheritance”.
There are currently 16 classes which inherit
directly from Identifiable and 23 classes which
inherit directly from AnnotatedIdentifiable. There
are overall 110 classes which inherit from other
classes and finally from Identifiable.<br>
The information which is captured by Identifiable
can be modeled as a data type which could be used
as attribute with the name “identifier” for each
class. Even the information which is captured by
AnnotatedIdentifiable can be modeled as a data
type. The exception is the association to
AgentAssociation. There are four m:n associations
from AnnotatedIdentifiable to AgentAssociation,
each with some kind of role (publisher,
contributor, versioning agent, creator). The weird
thing is that AgentAssociation itself has again a
role item (external CV).<br>
I see here some requirement for discussion how
this could be simplified. Diagrams on the current
approach and one suggested approach are attached.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">a.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">The information of Identifiable and
AnnotatedIdentifiable could be collapsed into one
structured data type with the exception of
AgentAssociation.<br>
Annotation could be an attribute of Identifier.
This would be more limited than the current
solution in terms of the annotation relationship.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">b.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Another approach would be to have
associations from classes which need Annotation.
One annotation could be then used for many
classes. A related super class could be
constructed. The latter approach would make
distinction between identification (which would be
an attribute) and annotation (to which an
association would exist).</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div style="margin-left:72.0pt">
<p class="MsoNormal" style="text-indent:-18.0pt"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">c.</span><span
style="font-size:7.0pt" lang="EN-US"> <span
class="apple-converted-space"> </span></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">A third approach would be to include
the identification information in the super class
described in b). This is similar to the current
approach but Annotation is not tied to a single
class. This seems to be a flexible solution.</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US"> </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""
lang="EN-US">Achim</span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><ClassesAndTheirSuperClasses.xlsx><span
style="font-size:10.0pt;font-family:"Helvetica","sans-serif"">_______________________________________________<br>
DDI-SRG mailing list<br>
</span><a href="mailto:DDI-SRG@icpsr.umich.edu"
moz-do-not-send="true"><span
style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:purple">DDI-SRG@icpsr.umich.edu</span></a><span
style="font-size:10.0pt;font-family:"Helvetica","sans-serif""><br>
</span><a
href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg"
moz-do-not-send="true"><span
style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:purple">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</span></a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
DDI-SRG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DDI-SRG@icpsr.umich.edu">DDI-SRG@icpsr.umich.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</a>
</pre>
</blockquote>
</body>
</html>