<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:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-US;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:614992566;
mso-list-template-ids:1041553986;}
@list l0:level1
{mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:939989617;
mso-list-template-ids:442425608;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">There is a new Canonical XMI available. I fixed all issues mentioned in the email exchange below.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The new XMI files (<a href="https://www.dropbox.com/s/bx0lc62lzocrlle/DDI-CDI_2021-08-13.xmi?dl=0">DDI-CDI_2021-08-13.xmi</a>,
<a href="https://www.dropbox.com/s/i4kzjggi4ep01dt/DDI-CDI_UniqueNames_2021-08-13.xmi?dl=0">
DDI-CDI_UniqueNames_2021-08-13.xmi</a>) and the change documentation (<a href="https://www.dropbox.com/s/mi58tlxyqhii7zo/ModelTransformation_2021-08-13.docx?dl=0">ModelTransformation_2021-08-13.docx</a>) are available for download.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Please review.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:DE">From:</span></b><span lang="EN-US" style="mso-fareast-language:DE"> ddi-srg-bounces@icpsr.umich.edu <ddi-srg-bounces@icpsr.umich.edu>
<b>On Behalf Of </b>Wackerow, Joachim<br>
<b>Sent:</b> Freitag, 6. August 2021 13:42<br>
<b>To:</b> DDI Structural Reform Working Group. <ddi-srg@icpsr.umich.edu><br>
<b>Subject:</b> Re: [DDI-SRG] [CDI] new Canonical XMI after model transform<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Thanks Flavio, for the things you noticed. This is helpful. My comments are below in the message.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Keep checking!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Achim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:DE">From:</span></b><span lang="EN-US" style="mso-fareast-language:DE"> Flavio Rizzolo <<a href="mailto:flavio.rizzolo@gmail.com">flavio.rizzolo@gmail.com</a>>
<br>
<b>Sent:</b> Freitag, 6. August 2021 03:39<br>
<b>To:</b> Wackerow, Joachim <<a href="mailto:Joachim.Wackerow@gesis.org">Joachim.Wackerow@gesis.org</a>>; DDI Structural Reform Working Group. <<a href="mailto:ddi-srg@icpsr.umich.edu">ddi-srg@icpsr.umich.edu</a>><br>
<b>Subject:</b> Re: [DDI-SRG] [CDI] new Canonical XMI after model transform<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>A couple of other issues:<o:p></o:p></p>
<p>- The "refine" association seems to have a unique name now, even in the non-unique names xmi. For instance, Concept "refines" IndividualMember. Instead, we have Concept "Concept_refines_IndividualMember" IndividualMember.<o:p></o:p></p>
<p><b><i><span lang="EN-US">[JW] The name should be probably removed in the regular XMI file. The long name should be in the version with the unique association names. The background of the refine names is that some UML tools are not able to consume the abstraction
stereotypes. They just ignore them which results in a Abstraction relationship without further specification. Using the name is a workaround. But this is confusing in a tool like EA which can consume the abstraction stereotypes. The name repeats what is already
expressed in the specific abstraction relationship. Another workaround would be to describe the kind of relationship in the definition.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">I will remove the names in the regular XMI file. I’ll add the long names to the version with the unique association names.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">You could think about if the abstraction definitions could be improved in a way that the kind of relationship is clear even if an UML tool doesn’t understand the related stereotypes like refine.<o:p></o:p></span></i></b></p>
<p><span lang="EN-US">- Identifier appears in all classes in the inheritance chains.
</span>For instance, Activity has Identifier, and so does Step, which is an extension of Activity. However, only the top non-abstract class in any inheritance chain should have Identifiable.<o:p></o:p></p>
<p><b><i><span lang="EN-US">[JW] I didn’t think about this.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">I will remove the attribute identifier at all classes which inherit from a non-abstract class.</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">- Which brings me to the next issue: abstract classes should not be identifiable, should they?
</span>They are never instantiated, so it seems pointless they hay an identifier.<o:p></o:p></p>
<p><b><i>[JW] Absolutely.<o:p></o:p></i></b></p>
<p><b><i><span lang="EN-US">I’ll remove the attribute identifier from abstract classes.</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">Flavio<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal">On 2021-08-05 2:00 p.m., Flavio Rizzolo wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p>Achim,<o:p></o:p></p>
<p>A few issues I noticed on a quick review: <o:p></o:p></p>
<p>- The definition of Identifier seems old. It says "Basic object requiring identification. Elements of this type are versioned and provide administrative metadata properties." It's a datatype now, so it should probably say "identifier for objects requiring
short- or long-lasting referencing and management", or something like that. The example seems wrong as well "Use for First Order Classes whose content does not need to be discoverable in its own right but needs to be related to multiple classes.". I suggest
to remove it.<o:p></o:p></p>
<p><b><i><span lang="EN-US">[JW] For the next transformation run, I would need the documentation of both the class attribute identifier and the data type Identifier. It could be the same definition.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">“Identifier for objects requiring short- or long-lasting referencing and management.” seems to be good enough.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">The suggested removal is fine with me.<o:p></o:p></span></i></b></p>
<p><span lang="EN-US">- Some of the attributes, e.g. ddiIdentifier, uri, appear to be of type "EA_Java_Types_Package".
</span>I'm not sure how that happened. <o:p></o:p></p>
<p><b><i><span lang="EN-US">[JW] I typed them as strings. I will look into this. This is an issue with EA and their use of UML primitives and how they express them in their version of XMI.</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">- There is a ModelIdentification datatype, right under the DataTypes package, that doesn't seem to be used anywhere.
<o:p></o:p></span></p>
<p><b><i><span lang="EN-US">[JW] I added this already to the public review version. It is not used anywhere in the model but it can be used by any program which uses the model or its representations. This way a program can recognize with which specification
and version it deals with.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">This could stay on the level of the data types like currently or it could be located just below DDICDILibrary. What do you think?</span></i></b><span lang="EN-US"><o:p></o:p></span></p>
<p><span lang="EN-US">- I was just going over the Documentation.xlsx and noticed a couple of enumerations that didn't ring a bell.
</span>I checked and couldn't find them in the latest EA file. They are WorkflowPattern and StringStructureType. There might be others. I'm not sure where they are coming from.<o:p></o:p></p>
<p><b><i><span lang="EN-US">[JW] StringStructureType was removed because I simplified all string data types. It is now an external controlled vocabulary. Hard coding would be too limited.<o:p></o:p></span></i></b></p>
<p><b><i><span lang="EN-US">WorkflowPattern is not used at all. I removed it but missed to document it.<o:p></o:p></span></i></b></p>
<p><span lang="EN-US">That's all for now. </span>I'll keep checking.<o:p></o:p></p>
<p>Flavio<o:p></o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2021-07-30 2:59 p.m., Wackerow, Joachim wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span lang="EN-US">I did the programmatic model transformation for a couple of issues we talked about. Prior to that I edited manually the EA model regarding some other issues.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">I documented all changes in <a href="https://www.dropbox.com/s/8fkxs38snd6ss2d/ModelTransformation_2021-07-30.docx?dl=0">
ModelTransformation_2021-07-30.docx</a>.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">The file lists also some items which need documentation. Volunteers sought.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">While doing this work I filed a couple of additional issues:</span><o:p></o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="color:blue;margin-left:0cm;mso-list:l0 level1 lfo3">
<span class="MsoHyperlink"><span lang="EN-US"><a href="https://ddi-alliance.atlassian.net/browse/CDI-57"><span lang="DE">Missing documentation
<b>CDI-57</b></span></a></span></span><o:p></o:p></li><li class="MsoListParagraph" style="color:blue;margin-left:0cm;mso-list:l0 level1 lfo3">
<span class="MsoHyperlink"><span lang="EN-US"><a href="https://ddi-alliance.atlassian.net/browse/CDI-56">Boolean class attributes: should they have a default value?
<b>CDI-56</b></a></span></span><o:p></o:p></li><li class="MsoListParagraph" style="color:blue;margin-left:0cm;mso-list:l0 level1 lfo3">
<span class="MsoHyperlink"><span lang="EN-US"><a href="https://ddi-alliance.atlassian.net/browse/CDI-55">Data type ObjectName attributes are not clear.
<b><span lang="DE">CDI-55</span></b></a></span></span><span lang="EN-US" style="color:windowtext;mso-fareast-language:DE">
</span><o:p></o:p></li><li class="MsoListParagraph" style="color:blue;margin-left:0cm;mso-list:l0 level1 lfo3">
<span class="MsoHyperlink"><span lang="EN-US"><a href="https://ddi-alliance.atlassian.net/browse/CDI-54">Data type name "SpecificationType" too generic
<b>CDI-54</b></a></span></span><o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo3"><span class="MsoHyperlink"><span lang="EN-US"><a href="https://ddi-alliance.atlassian.net/browse/CDI-58">Review names of enumerations and data types. Several have the suffix 'type'.
<b><span lang="DE">CDI-58</span></b></a></span></span><o:p></o:p></li></ol>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">The new files include everything below DDICDIModels. The abstraction stereotypes like trace are maintained. Diagrams get lost in this process.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">The new XMI files (<a href="https://www.dropbox.com/s/oizidnadhqeo1s7/DDI-CDI_2021-07-30.xmi?dl=0">DDI-CDI_2021-07-30.xmi</a>,
<a href="https://www.dropbox.com/s/sv3h4cof4i499xx/DDI-CDI_UniqueAssociationNames_2021-07-30.xmi?dl=0">
DDI-CDI_UniqueAssociationNames_2021-07-30.xmi</a>) are available for download.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Please review. There might be issues.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US">Achim</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="mso-fareast-language:DE"><o:p> </o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>DDI-SRG mailing list<o:p></o:p></pre>
<pre><a href="mailto:DDI-SRG@icpsr.umich.edu">DDI-SRG@icpsr.umich.edu</a><o:p></o:p></pre>
<pre><a href="http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg">http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg</a><o:p></o:p></pre>
</blockquote>
</blockquote>
</div>
</body>
</html>