[DDI-SRG] [CDI] Questions about ControlledVocabularyEntry, PairedControlledVocabularyEntry and Reference
Flavio Rizzolo
flavio.rizzolo at gmail.com
Sun Aug 22 04:31:18 EDT 2021
This is Identifier with the right data types
On 2021-08-22 4:15 a.m., Flavio Rizzolo wrote:
>
> Ok.
>
> BTW, I think I will just drop the idea of NativeReference as a
> superclass of Reference, I don't think I can untangle Reference and
> ControlledVocabularyEntry in any meaningful way, this requires more
> thinking than the one it can be done before the release.
>
> I just want a simple mechanism to reference an object and its type.
> How about just using Identifier? It doesn't include the type, but it's
> not necessary in the particular case of the Process model since it can
> refer to any identifiable object. It will be something like this:
>
> At this point I think it's either this or the full-fledged Reference.
>
> Flavio
>
>
> On 2021-08-21 9:04 p.m., A. G. wrote:
>> Flavio:
>>
>> I agree with Larry on this one - that seems right to me.
>>
>> Cheers,
>>
>> Arofan
>>
>> On Sunday, August 22, 2021, 03:03:04 AM GMT+2, Hoyle, Larry
>> <larryhoyle at ku.edu> wrote:
>>
>>
>> I think you are on the right track with using Reference instead of
>> PairedControlledVocabularyEntry. Reference didn’t exist when Activity
>> was modeled.
>>
>> standardModelUsed with datatype Reference would have:
>>
>> vocabulary as a reference to GSBPM
>> (https://statswiki.unece.org/display/GSBPM/GSBPM+v5.1
>> <https://statswiki.unece.org/display/GSBPM/GSBPM+v5.1>)
>>
>> controlledVocabuaryName as “GSBPM”
>>
>> entryValue as the name of the sub step “1.1 Identify Needs”
>>
>> entryReference as a Reference to the sub step
>> (https://statswiki.unece.org/display/GSBPM/1.1+Identify+needs
>> <https://statswiki.unece.org/display/GSBPM/1.1+Identify+needs>)
>>
>> *From:* Flavio Rizzolo <flavio.rizzolo at gmail.com>
>> *Sent:* Saturday, August 21, 2021 5:46 PM
>> *To:* Hoyle, Larry <larryhoyle at ku.edu>; DDI Structural Reform Working
>> Group. <ddi-srg at icpsr.umich.edu>
>> *Subject:* Re: [DDI-SRG] [CDI] Questions about
>> ControlledVocabularyEntry, PairedControlledVocabularyEntry and Reference
>>
>> I saw the definition, it's just that it doesn't seem to align with
>> its use in Activity
>>
>> standardModelUsed is defined as
>>
>> /"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. *Enter the name of the model in "term" and the
>> step, sub-step, or specific portion of the model in "extent"*./
>>
>> 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...
>>
>> Flavio
>>
>> On 2021-08-21 6:09 p.m., Hoyle, Larry wrote:
>>
>> term is a ControlledVocabularyEntry
>>
>> extent is a degree of the term. It has the description:
>>
>> “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’.”
>>
>> In the example from the Credit taxonomy one could be credited as
>> being the “lead” conceptualizer, or “equal”, or “supporting”.
>>
>> http://credit.niso.org/implementing-credit/
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcredit.niso.org%2Fimplementing-credit%2F&data=04%7C01%7Clarryhoyle%40ku.edu%7C2cc65b45ad514c59087e08d964f583da%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651827913948113%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wkUlxIC%2Ffj%2FvcztAA3y5U76NBW4LV0C3AfWn6VY271E%3D&reserved=0>
>>
>> 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.
>>
>> Larry
>>
>> *From:* Flavio Rizzolo <flavio.rizzolo at gmail.com>
>> <mailto:flavio.rizzolo at gmail.com>
>> *Sent:* Saturday, August 21, 2021 4:59 PM
>> *To:* Hoyle, Larry <larryhoyle at ku.edu>
>> <mailto:larryhoyle at ku.edu>; DDI Structural Reform Working Group.
>> <ddi-srg at icpsr.umich.edu> <mailto:ddi-srg at icpsr.umich.edu>
>> *Subject:* Re: [DDI-SRG] [CDI] Questions about
>> ControlledVocabularyEntry, PairedControlledVocabularyEntry and
>> Reference
>>
>> Oh, I see what you mean. I'll fix that.
>>
>> Ok, so vocabulary is a "Reference", not a "String". I'll fix that
>> too.
>>
>> Back to my last question: how is the use of "entryReference" and
>> "entryValue" in the example different from "extent" and "term" in
>> PairedControlledVocabulary?
>>
>> Other questions:
>>
>> - 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?
>>
>> - 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
>>
>> On 2021-08-21 5:34 p.m., Hoyle, Larry wrote:
>>
>> 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.
>>
>> Here is an example.
>>
>> vocabulary is a reference to http://credit.niso.org/
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcredit.niso.org%2F&data=04%7C01%7Clarryhoyle%40ku.edu%7C2cc65b45ad514c59087e08d964f583da%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651827913948113%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=A5gBJdcJR7eESx4%2FokMdXNGAqiWHMvLhRaxHcNz2tcw%3D&reserved=0>
>> the Credit Taxonomy (via the uri of Reference)
>>
>> controlledVocabularyName is “the Credit Taxonomy”
>>
>> entryReference is
>> http://credit.niso.org/contributor-roles/conceptualization/
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcredit.niso.org%2Fcontributor-roles%2Fconceptualization%2F&data=04%7C01%7Clarryhoyle%40ku.edu%7C2cc65b45ad514c59087e08d964f583da%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651827913958099%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bbH%2Ffn7svFcrSJCnT3XkMQCSNScIp0hn5azxc8Q6gIM%3D&reserved=0>
>>
>>
>> entryValue is “Conceptualization”
>>
>> *From:* ddi-srg-bounces at icpsr.umich.edu
>> <mailto:ddi-srg-bounces at icpsr.umich.edu>
>> <ddi-srg-bounces at icpsr.umich.edu>
>> <mailto:ddi-srg-bounces at icpsr.umich.edu> *On Behalf Of
>> *Flavio Rizzolo
>> *Sent:* Saturday, August 21, 2021 4:15 PM
>> *To:* DDI Structural Reform Working Group.
>> <ddi-srg at icpsr.umich.edu> <mailto:ddi-srg at icpsr.umich.edu>
>> *Subject:* [DDI-SRG] [CDI] Questions about
>> ControlledVocabularyEntry, PairedControlledVocabularyEntry
>> and Reference
>>
>> Hi,
>>
>> These are the new Native classes, with the old classes as
>> extensions:
>>
>> 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.
>>
>> With that in mind:
>>
>> 1) shouldn't we then change the type of the attributes in
>> PairedControlledVocabulary to NativeControlledVocabularyEntry?
>>
>> 2) What's exactly "vocabulary" in ControlledVocabularyEntry?
>> How is it used?
>>
>> 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...
>>
>> Thanks,
>>
>> Flavio
>>
>> _______________________________________________
>> DDI-SRG mailing list
>> DDI-SRG at icpsr.umich.edu <mailto:DDI-SRG at icpsr.umich.edu>
>> http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg
>> <http://lists.icpsr.umich.edu/mailman/listinfo/ddi-srg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210822/85de38c9/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cncoaebnnonalbfo.png
Type: image/png
Size: 21738 bytes
Desc: not available
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210822/85de38c9/attachment-0002.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gmlbmolnmbfejfpn.png
Type: image/png
Size: 60272 bytes
Desc: not available
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210822/85de38c9/attachment-0003.png
More information about the DDI-SRG
mailing list