Property talk:P443

From Wikidata
Jump to navigation Jump to search

Documentation

pronunciation audio
audio file with pronunciation
Descriptionname of a file on Commons with pronunciation (Q184377). Use qualifiers to identify language of work or name (P407) (and possibly voice type (P412)).
Representspronunciation (Q184377)
Data typeCommons media file
Domainany (note: this should be moved to the property statements)
Allowed values
According to this template: any existing audio file with pronunciation on Commons
According to statements in the property:
.+\.(ogg|oga|flac|wav|mp3)
When possible, data should only be stored as statements
Example
According to this template: Lviv => File:Lviv.ogg -- Qualifiers: language of work or name (P407): Polish, voice type (P412): baritone
When possible, data should only be stored as statements
Formatter URLhttps://commons.wikimedia.org/wiki/File:$1
Embed URLhttps://commons.wikimedia.org/wiki/File:$1
Tracking: usageno label (Q61035497)
See alsoIPA transcription (P898), audio (P51), spoken text audio (P989), audio recording of the subject's spoken voice (P990), pronunciation (P7243)
Lists
Proposal discussionProposal discussion
Current uses
Total278,297
Main statement227,94081.9% of uses
Qualifier50,35518.1% of uses
Reference2<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
Link to Commons namespace “File”: this property should contain a well-formed link to an existing page on Wikimedia Commons. (Help)
List of violations of this constraint: Database reports/Constraint violations/P443#Commons link, hourly updated report
Format “(?i).+\.(ogg|oga|flac|wav|opus|mp3)”: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P443#Format, hourly updated report, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase form (Q54285143): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P443#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P443#Scope, hourly updated report, SPARQL
Required qualifier “language of work or name (P407)”: this property should be used with the listed qualifier. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P443#mandatory qualifier, SPARQL
Qualifier P407 missing
add qualifier (Help)
Violations query: SELECT ?item ?file { ?item wdt:P443 ?value . MINUS { ?item p:P443 [ pq:P407 [] ] } MINUS { ?item rdf:type [] } BIND(replace(wikibase:decodeUri(SUBSTR(STR(?value), 52)),"_"," ") AS ?file) FILTER ( !REGEX( ?file, "^LL-.+$") ) FILTER ( !REGEX( ?file, "^[A-Z][a-z]-.+$") ) } LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P443#Qualifier P407 missing
Qualifier P407 missing (filename starts with code)
add qualifier (simple) (Help)
Violations query: SELECT ?item ?file { ?item wdt:P443 ?value . MINUS { ?item p:P443 [ pq:P407 [] ] } MINUS { ?item rdf:type [] } BIND(replace(wikibase:decodeUri(SUBSTR(STR(?value), 52)),"_"," ") AS ?file) FILTER ( REGEX( ?file, "^[A-Z][a-z]-.+$") ) } LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P443#Qualifier P407 missing (filename starts with code)
Qualifier P407 missing (LL filename)
add qualifier (easy) (Help)
Violations query: SELECT ?item ?itemLabel ?file ?lang { ?item wdt:P443 ?value . MINUS { ?item p:P443 [ pq:P407 [] ] } MINUS { ?item rdf:type [] } BIND(replace(wikibase:decodeUri(SUBSTR(STR(?value), 52)),"_"," ") AS ?file) FILTER ( REGEX( ?file, "^LL-.+$") ) BIND( replace( ?file, "^LL-(Q\\d+) .+$", "$1") as ?lang) } LIMIT 100
List of this constraint violations: Database reports/Complex constraint violations/P443#Qualifier P407 missing (LL filename)
Languages with categories available at Commons, but no item with audio file
if applicable, add P443 to an item (e.g. place name pronunciation audio to an item for the place). Based on Property_talk:P7084#Use for pronunciation file categories (Commons) (Help)
Violations query: SELECT ?item ?comcat WHERE { ?item p:P7084 [ ps:P7084 ?r ; pq:P642 wd:Q184377 ] MINUS { ?a p:P443/pq:P407 ?item . FILTER NOT EXISTS { ?a wikibase:lemma [] } FILTER NOT EXISTS { ?a rdf:type <http://www.w3.org/ns/lemon/ontolex#Form> } } [] schema:about ?r ; schema:isPartOf <https://commons.wikimedia.org/> ; schema:name ?com . BIND(CONCAT("[[c:", ?com, "\u007C", strafter(?com, ":"), "]]" ) as ?comcat) } ORDER BY ?comcat LIMIT 500
List of this constraint violations: Database reports/Complex constraint violations/P443#Languages with categories available at Commons, but no item with audio file
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Lists[edit]

Discussion[edit]

Deprecate for Q-items?[edit]

Shouldn't we start deprecating this property for Q-items and move them to Lexeme items under forms? To me it confuses the notion of concept and the notion of representation. The concept might also have multiple representation, e.g., dictionary (Q23622) may be "wordbook" and "dictionary" as English representations, — and these are definitely pronounced differently. — Finn Årup Nielsen (fnielsen) (talk) 12:35, 24 November 2019 (UTC)[reply]

I  Support, we should deprecate it.--So9q (talk) 10:19, 26 November 2020 (UTC)[reply]
  • I  Support removing it's usage for items starting by changing the constraints. ChristianKl ❪✉❫ 19:30, 22 December 2020 (UTC)[reply]
  • What alternative is suggested? --- Jura 07:05, 23 December 2020 (UTC)[reply]
  • I agree with Jura's comment from 03:45, 26 November 2019 (UTC). For entities with proper names (people, places, companies, etc.), there is usually (but not always) only one "official" pronunciation (i.e. in the native language), and creating a lexeme for each just to put a link to the media file there seems to be overkill. --Matěj Suchánek (talk) 10:26, 23 December 2020 (UTC)[reply]
  • I agree with Jura/Matěj/Vahurzpu - some kind of constraint in principle that we should only use this for "proper nouns" would be good. Pronunciation can differ for names - I am pretty confident that Colin Powell (Q150851) and Colin Powell (Q5145485) would have different pronunciations, for example, despite having the same family name (P734)/given name (P735) claims and identical item labels. I can't see how a lexeme-based solution would work there. So  Oppose deprecation in general, but no objection to cleaning up its use on generic items like dictionary (Q23622). Andrew Gray (talk) 21:43, 23 December 2020 (UTC)[reply]
  • I'd like to see some more detail as to what it would entail in practice. Lexemes are intended for Wiktionary's use cases, but I fear we might end up with a level of complexity that's over-the-top for most Wikipedians (and Wikisourcerors, Wikivoyagers etc.) to really grasp—they, after all, have to buy into the point of Wikidata for the project to flourish. The idea that, say, we're going to have a Q object called "Bill Clinton" (the president), then a Lexeme object called "Bill Clinton" that contains a link to the audio file of the pronunciation of the word, seems needlessly convoluted. Or perhaps "Bill Clinton" (the president) could then link to a lexeme object or "Bill" and "Clinton", with the latter shared with, say, Hillary Clinton, and George Clinton (the funk musician), and the many other Clintons in the world. That might be preferable after all. The issues presented by Andrew Gray seem worth answering, and it'd be worth spelling out how this works in practice so your average workaday Wikidata user can grasp what exactly they have to do in order to, say, manage the Wikidata object for the subject of a Wikipedia article they wrote without needing a linguistics degree. —Tom Morris (talk) 09:15, 24 December 2020 (UTC)[reply]
Thanks for the overview @Vahurzpu:. As I just wrote in the lexicographic telegram channel: "[In reply to Jan Ainali] Yes, but as is noted in the discussion the links from the Q-namespace to the L-namespace are weak or nonexistent at the moment. We need to fix that in some way so the ordinary editor can easily discover lexeme(s) related to a qitem".
This is a UI problem and a how to link most intelligently to avoid redundancy and maximize utility-problem. I  Support Jura's proposal for now because ChristianKl's proposal will cause a lot of bloat proper name lexemes which does not seem valuable to me. Jura's proposal may require more work to keep tidy in case it cannot be adequately constrained. In that case we could have a bot help us, so that will sort itself someway or another.--So9q (talk) 11:37, 25 December 2020 (UTC)[reply]

Problem with "language of work"-constraint when used on lexeme forms[edit]

The constraint is triggered on lexemes also and leads to confusion. I suggest we create a new property for use on lexeme forms if this cannot be fixed easily.--So9q (talk) 10:25, 26 November 2020 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P443&oldid=2130848272"