<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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]-->
</head>
<body lang="DE" link="blue" vlink="purple" style="word-wrap: break-word;-webkit-nbsp-mode: space;line-break:after-white-space">
<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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I think MRT is still very weak on the T.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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 lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Jay Greenfield [mailto:nightcleaner@gmail.com]
<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">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </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 lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span class="apple-converted-space"><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> </span></span><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><a href="mailto:ddi-srg-bounces@icpsr.umich.edu"><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"><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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">1.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">a.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">i.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">b.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">i.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">c.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">i.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">ii.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">iii.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">d.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">2.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">3.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">4.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">5.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">a.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">b.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">c.</span><span lang="EN-US" style="font-size:7.0pt"> <span class="apple-converted-space"> </span></span><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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 lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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"><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"><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>
</body>
</html>