[DDI-SRG] [CDI] Questions about ControlledVocabularyEntry, PairedControlledVocabularyEntry and Reference

Hoyle, Larry larryhoyle at ku.edu
Sat Aug 21 18:09:55 EDT 2021


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/

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>
Sent: Saturday, August 21, 2021 4:59 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


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%7Cb716aeec0aa24a86a36908d964eeec37%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651799597839594%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a5QDrUmFeaEDtG1zXUWVYzKmt1g4gXekhLUombLCm9I%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%7Cb716aeec0aa24a86a36908d964eeec37%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C637651799597849589%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YH6TLJ6RJWsLIObde%2FAtys3EoFxg6x8NQohnpZYv0qY%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:

[cid:image002.png at 01D796AF.5B3C4A40]

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?

[cid:image004.png at 01D796AF.5B3C4A40]

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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/6c054eb7/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 251346 bytes
Desc: image002.png
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/6c054eb7/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 50004 bytes
Desc: image004.png
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/6c054eb7/attachment-0003.png 


More information about the DDI-SRG mailing list