<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<p>I saw the definition, it's just that it doesn't seem to align
with its use in Activity</p>
<p><img src="cid:part1.1164E838.9785FDC9@gmail.com" alt=""
width="627" height="291"></p>
<p>standardModelUsed is defined as <br>
</p>
<p><i>"If a standard process model such as The Generic Statistical
Business Process Model (GSBPN), the Generic Longitudinal
Business Process Model (GLBPM), Open Archive Information System
model (OAIS), etc. has been related to this business process,
the model and step or sub-step is noted here using the Paired
External Controlled Vocabulary Entry. </i><i><b><font
color="#0080ff">Enter the name of the model in "term" and
the step, sub-step, or specific portion of the model in
"extent"</font></b></i><i>.</i><br>
</p>
<p>That seems to align better with Reference than with
PairedControlledVocabularyEntry, since we need to refer to a
schema, e.g. "GSBPM", and then to an element in the schema, e.g.
"edit & imputation". I don't see how to map "GSBPM" to term
and "edit & imputation" to extent...<br>
</p>
<p>Flavio<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2021-08-21 6:09 p.m., Hoyle, Larry
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CY4PR0101MB28887DBD8C6AC73E762E95E8BDC29@CY4PR0101MB2888.prod.exchangelabs.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}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">term is a ControlledVocabularyEntry<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">extent is a degree of the term. It has the
description:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“Describes the extent to which the parent
term applies for the specific case using an external
controlled vocabulary. When associated with a role from the
CASRAI Contributor Roles Taxonomy an appropriate vocabulary
should be specified as either ‘lead’, ‘equal’, or
‘supporting’.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the example from the Credit taxonomy one
could be credited as being the “lead” conceptualizer, or
“equal”, or “supporting”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a
href="http://credit.niso.org/implementing-credit/"
moz-do-not-send="true">http://credit.niso.org/implementing-credit/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This was done to disambiguate the use of
author order in citing contributors. In some disciplines the
first author is the lead. In others the head of a larger
project might be listed last.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Larry<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Flavio Rizzolo
<a class="moz-txt-link-rfc2396E" href="mailto:flavio.rizzolo@gmail.com"><flavio.rizzolo@gmail.com></a> <br>
<b>Sent:</b> Saturday, August 21, 2021 4:59 PM<br>
<b>To:</b> Hoyle, Larry <a class="moz-txt-link-rfc2396E" href="mailto:larryhoyle@ku.edu"><larryhoyle@ku.edu></a>; DDI
Structural Reform Working Group.
<a class="moz-txt-link-rfc2396E" href="mailto:ddi-srg@icpsr.umich.edu"><ddi-srg@icpsr.umich.edu></a><br>
<b>Subject:</b> Re: [DDI-SRG] [CDI] Questions about
ControlledVocabularyEntry, PairedControlledVocabularyEntry
and Reference<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Oh, I see what you mean. I'll fix that.<o:p></o:p></p>
<p>Ok, so vocabulary is a "Reference", not a "String". I'll fix
that too.<br>
<br>
Back to my last question: how is the use of "entryReference"
and "entryValue" in the example different from "extent" and
"term" in PairedControlledVocabulary?<br>
<br>
Other questions:<br>
<br>
- CatalogDetail: This structured data type has no definition,
no subclasses and no structure. What is it? How can it be used
in its current state?<o:p></o:p></p>
<p>- DataPoint: Why does it have now a catalogDetails attribute?
Why DataPoint and not DataSet or other classes in Data
Description? The use of CatalogDetails is unclear<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2021-08-21 5:34 p.m., Hoyle, Larry
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">ControlledVocabularyEntry should be able
to reference an entry outside of DDI. So that entryReference
should be Reference, not Native Reference. It would be
better to ditch the inheritance of ControlledVocabularyEntry
from NativeControlledVocabularyEntry and just have a
separate ControlledVocabularyEntry with all of the
properties it has below.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Here is an example.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">vocabulary is a reference to <a
href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcredit.niso.org%2F&data=04%7C01%7Clarryhoyle%40ku.edu%7Cb716aeec0aa24a86a36908d964eeec37%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651799597839594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a5QDrUmFeaEDtG1zXUWVYzKmt1g4gXekhLUombLCm9I%3D&reserved=0"
moz-do-not-send="true">
http://credit.niso.org/</a> the Credit Taxonomy (via the
uri of Reference)<o:p></o:p></p>
<p class="MsoNormal">controlledVocabularyName is “the Credit
Taxonomy”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">entryReference is <a
href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcredit.niso.org%2Fcontributor-roles%2Fconceptualization%2F&data=04%7C01%7Clarryhoyle%40ku.edu%7Cb716aeec0aa24a86a36908d964eeec37%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651799597849589%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YH6TLJ6RJWsLIObde%2FAtys3EoFxg6x8NQohnpZYv0qY%3D&reserved=0"
moz-do-not-send="true">
http://credit.niso.org/contributor-roles/conceptualization/</a> <o:p></o:p></p>
<p class="MsoNormal">entryValue is “Conceptualization”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> <a
href="mailto:ddi-srg-bounces@icpsr.umich.edu"
moz-do-not-send="true">
ddi-srg-bounces@icpsr.umich.edu</a> <a
href="mailto:ddi-srg-bounces@icpsr.umich.edu"
moz-do-not-send="true">
<ddi-srg-bounces@icpsr.umich.edu></a> <b>On
Behalf Of </b>Flavio Rizzolo<br>
<b>Sent:</b> Saturday, August 21, 2021 4:15 PM<br>
<b>To:</b> DDI Structural Reform Working Group. <a
href="mailto:ddi-srg@icpsr.umich.edu"
moz-do-not-send="true">
<ddi-srg@icpsr.umich.edu></a><br>
<b>Subject:</b> [DDI-SRG] [CDI] Questions about
ControlledVocabularyEntry,
PairedControlledVocabularyEntry and Reference<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p>Hi, <o:p></o:p></p>
<p>These are the new Native classes, with the old classes as
extensions:<o:p></o:p></p>
<p><img style="width:7.4791in;height:4.0138in"
id="Picture_x0020_1"
src="cid:part8.6641614D.7A45ABF9@gmail.com" class=""
width="718" height="385" border="0"><o:p></o:p></p>
<p>We can always define attributes of type
NativeControlledVocabularyEntry and NativeReference, which
will allow us to use the full-fledged list of attributes
from the sub-classes if necessary.
<o:p></o:p></p>
<p>With that in mind:<o:p></o:p></p>
<p>1) shouldn't we then change the type of the attributes in
PairedControlledVocabulary to
NativeControlledVocabularyEntry?<o:p></o:p></p>
<p><img style="width:3.7013in;height:1.8125in"
id="Picture_x0020_2"
src="cid:part9.4BE19637.9F49690A@gmail.com" class=""
width="355" height="174" border="0"><o:p></o:p></p>
<p>2) What's exactly "vocabulary" in
ControlledVocabularyEntry? How is it used?<o:p></o:p></p>
<p>3) Actually, how do we really use these things? I
understand how the Native classes work, but now it seems
Reference might be used to reference a term and an extent,
like PairedControlledVocabularyEntry, but in a different
way. I think there was an example somewhere that help people
made sense of all this, but I can't find it, and I fear we
are making a mistake somewhere... So many cross references
between classes are making me dizzy...<o:p></o:p></p>
<p>Thanks,<o:p></o:p></p>
<p>Flavio<o:p></o:p></p>
<p> <o:p></o:p></p>
</blockquote>
</div>
</blockquote>
</body>
</html>