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

[Flavio Rizzolo]

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/ 
> <http://credit.niso.org/> the Credit Taxonomy (via the uri of Reference)
>
> controlledVocabularyName is “the Credit Taxonomy”
>
> entryReference is 
> http://credit.niso.org/contributor-roles/conceptualization/ 
> <http://credit.niso.org/contributor-roles/conceptualization/>
>
> entryValue is “Conceptualization”
>
> *From:* ddi-srg-bounces at icpsr.umich.edu 
> <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>
> *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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/8652e492/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 250672 bytes
Desc: not available
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/8652e492/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 49964 bytes
Desc: not available
Url : http://lists.icpsr.umich.edu/pipermail/ddi-srg/attachments/20210821/8652e492/attachment-0003.png