Wikidata:Property proposal/RDA value vocabularies ID
RDA value vocabularies ID[edit]
Originally proposed at Wikidata:Property proposal/Authority control
Motivation[edit]
RDA (Resource Description and Access) contains numerous controlled vocabularies used in cataloging. The vocabularies contain terms, definitions, and scope notes in English. There are also current and pending translations of the terms in Arabic, Catalan, Chinese, Danish, Dutch, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Norwegian, Portuguese, Slovak, Spanish, Swedish, Ukrainian, and Vietnamese. There are URIs available for linked data purposes for these vocabularies, and it would be beneficial to be able to link from Wikidata to them. UWashPrincipalCataloger (talk) 12:05, 22 December 2020 (UTC)
Discussion[edit]
- Support Always nice to correlate more standardized vocabularies with Wikidata items. ArthurPSmith (talk) 18:05, 22 December 2020 (UTC)
- Support. Having one prop for all these RDA and ONIX thesauri is the right way.
- The only downside is that the same item could have several IDs when it falls into several thesauri, as the flip chart (Q1428941) example above shows
- @UWashPrincipalCataloger: could you please make items for each of the code lists? So we can add info, eg for http://rdaregistry.info/termList/fontSize/: prefix is rdafs, RDF/XML link is http://rdaregistry.info/termList/fontSize.xml, JSON-LD link is http://www.rdaregistry.info/jsonld/termList/fontSize.jsonld ... Vladimir Alexiev (talk) 13:07, 23 December 2020 (UTC)
- Support completely agree with Vladimir Alexiev - it would be great to have an item for each vocabulary.
- Comment this proposal overlaps with RDA support type ID above. Simon Cobb (User:Sic19 ; talk page) 13:25, 23 December 2020 (UTC)
- There are items now for all but four of these vocabularies, and will finish the remaining ones today. UWashPrincipalCataloger (talk) 21:10, 29 December 2020 (UTC)
- Comment this proposal overlaps with RDA support type ID above. Simon Cobb (User:Sic19 ; talk page) 13:25, 23 December 2020 (UTC)
- @ArthurPSmith, Vladimir Alexiev, Sic19: Part of this proposal is changing about what external-id means in Wikidata (it's supposed to be a unique identifier). While I think that's a question worth discussing I don't believe it's a decision to be made implicitly. When the external-id datatype was first created we only moved those properties over that have single values. ChristianKl ❪✉❫ 16:51, 23 December 2020 (UTC)
- Ah yes, I didn't notice this problem here. I think the unique value constraint is more important than the single value one (for example some identifiers are case insensitive so they could have multiple entries with different uppercase/lowercase choices) but that does suggest it might be better to have a separate property for each of the vocabularies, at least where there's overlap. ArthurPSmith (talk) 18:26, 23 December 2020 (UTC)
- Some of these value vocabularies only have two entries, so I didn't think we would want separate properties for each of them. But yes, I could make items for each of the code lists if that would be beneficial. UWashPrincipalCataloger (talk) 19:25, 23 December 2020 (UTC)
- I've created one item so far: RDA aspect ratio designation (Q104442175). Would appreciate hearing back if this is what you'd like to see and if I've included all of the relevant properties. In particular, is what I put for property XML namespace URL (P7510) correct? UWashPrincipalCataloger (talk) 20:00, 23 December 2020 (UTC)
- Ah yes, I didn't notice this problem here. I think the unique value constraint is more important than the single value one (for example some identifiers are case insensitive so they could have multiple entries with different uppercase/lowercase choices) but that does suggest it might be better to have a separate property for each of the vocabularies, at least where there's overlap. ArthurPSmith (talk) 18:26, 23 December 2020 (UTC)
- @UWashPrincipalCataloger: Looks good to me. Simon Cobb (User:Sic19 ; talk page) 18:32, 29 December 2020 (UTC)
- @Sic19: Thank you. There are items now for all but four of these vocabularies, and will finish the remaining ones today. UWashPrincipalCataloger (talk) 21:09, 29 December 2020 (UTC)
- @UWashPrincipalCataloger: Looks good to me. Simon Cobb (User:Sic19 ; talk page) 18:32, 29 December 2020 (UTC)
- Question doesn't separator (P4155) enable us to set parameters that allow multiple values under a single value constraint if the specified qualifiers are added? Simon Cobb (User:Sic19 ; talk page) 20:31, 23 December 2020 (UTC)
- Support I agree, is a good idea to create this property to connect Wikidata items with standardized and multilingual vocabularies --LiaFla (talk) 08:13, 10 February 2021 (UTC)
@UWashPrincipalCataloger, Sic19: I checked and edited RDA aspect ratio designation (Q104442175):
- It's also a dataset
- "XML namespace" http://www.rdaregistry.info/xml/termList/AspectRatio.xml is wrong. That should be "URL" with qualifier "format: RDF". (Or "download link" instead of "URL", but that prop complains it should be used only in qualifiers, not sure why)
- The RDF namespace of this thesaurus is http://rdaregistry.info/termList/AspectRatio/ and the usual prefix is rdaar but I don't know how to express this in Wikidata. (In RDF there are props vann:preferredNamespacePrefix, vann:preferredNamespaceUri, used on owl:Ontology)
- @ChristianKl: For the love of God, we want a single prop for all these. Please! --Vladimir Alexiev (talk) 12:04, 18 February 2021 (UTC)
- @Vladimir Alexiev: Thank you. I've changed all of the other items to match what you did with RDA aspect ratio designation (Q104442175). UWashPrincipalCataloger (talk) 23:32, 22 February 2021 (UTC)