Property talk:P51
Latest comment: 3 years ago by Ehn in topic Uses on items for places
Documentation
audio
relevant sound. If available, use a more specific property. Samples: "spoken text audio" (P989), "pronunciation audio" (P443)
relevant sound. If available, use a more specific property. Samples: "spoken text audio" (P989), "pronunciation audio" (P443)
[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/P51#Commons link, hourly updated report
Format “
List of violations of this constraint: Database reports/Constraint violations/P51#Format, hourly updated report, SPARQL(?i).+\.(oga|ogg|mp3|flac|mid|midi|wav|opus|webm)”: value must be formatted using this pattern (PCRE syntax). (Help)
Qualifiers “performer (P175), language of work or name (P407), series ordinal (P1545), media legend (P2096), reason for deprecated rank (P2241), reason for preferred rank (P7452), main subject (P921), file format (P2701), object has role (P3831), depicts (P180), applies to part (P518)”: this property should be used only with the listed qualifiers. (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/P51#allowed qualifiers, SPARQL
Conflicts with “instance of (P31): poem (Q5185279), literary work (Q7725634)”: this property must not be used with the listed properties and values. (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/P51#Conflicts with P31, SPARQL
Conflicts with “instance of (P31): village (Q532), municipality of the Netherlands (Q2039348)”: this property must not be used with the listed properties and values. (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/P51#Conflicts with P31, SPARQL
Conflicts with “coordinate location (P625)”: this property must not be used with the listed properties and values. (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/P51#Conflicts with P625, SPARQL
Allowed entity types are Wikibase item (Q29934200): 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/P51#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449), as reference (Q54828450): the property must be used by specified way only (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/P51#Scope, SPARQL
|
Pattern ^((?i).+\.(webm|ogv))$ will be automatically replaced to \1 and moved to video (P10) property. Testing: TODO list |
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Samples and constraints updated edit
Following a discussion with @Hsarrazin: on Topic:V8mgkji0bhf932u0, we updated the samples/constraints and moved some values to the various related properties created later. More cleanup is still needed. Constraint reports should detail it. --- Jura 22:02, 5 October 2019 (UTC)
Uses on items for people (P31=Q5) edit
It seems that there are the following uses:
- pronunciation of the name of the person:
this should use pronunciation audio (P443) instead - reading of a Wikipedia article about the person:
this should use spoken text audio (P989) instead - words pronounced by the person:
this should use audio recording of the subject's spoken voice (P990) instead - recording of a work by the person (composition, literary work)
- recording of the person signing
- recording of the person playing an instrument
The last two seem fine. Maybe #4 should go on the item for a notable work. --- Jura 12:23, 6 October 2019 (UTC)
Uses on items for places edit
It seems that there are the following uses:
- pronunciation of the name of the place:
this should use pronunciation audio (P443) instead - reading of a Wikipedia article about the place:
this should use spoken text audio (P989) instead
Accordingly, I added constraints that should prevent addition of P51. --- Jura 12:41, 6 October 2019 (UTC)
- Is this the constraint you added: P51#P51$DC65F8F7-4D24-4BB3-C619-12F6D9246E4D (P51#P51$dc65f8f7-4d24-4bb3-c619-12f6d9246e4d), ie conflicts with coordinate location (P625)? I understand the intention, but this solution creates other problems, eg in the recent 2020 Beirut explosions (Q98073118) item, an industrial disaster that has a location and an audio recording. (The currently included audio recording is a video file, but that could be fixed and is irrelevant to this issue.) In general, there are many locations that have characteristic sounds where use of this property would make sense. Ehn (talk) 03:07, 7 August 2020 (UTC)
- Agree. It doesn't work well with statements for church bell recordings either. --- Jura 16:34, 15 August 2020 (UTC)
- So what's the best course of action here? Removing or relaxing the constraint? I'm new to Wikidata. :) Ehn (talk) 03:53, 21 August 2020 (UTC)
- I relaxed it a bit and added a clarification [1]. I hesistate to remove it entirely: I'm not quite sure how many audio files I had to fix when I wrote the above. 05:12, 21 August 2020 (UTC)
- It's still showing a "conflicts-with constraint: An entity should not have statements for both audio and coordinate location." warning/error message on 2020 Beirut explosions (Q98073118). I'm new to Wikidata. Perhaps it's normal not to address such warnings/errors in cases where the intention of the constraint doesn't apply? Ehn (talk) 09:24, 31 August 2020 (UTC)
- I relaxed it a bit and added a clarification [1]. I hesistate to remove it entirely: I'm not quite sure how many audio files I had to fix when I wrote the above. 05:12, 21 August 2020 (UTC)
- So what's the best course of action here? Removing or relaxing the constraint? I'm new to Wikidata. :) Ehn (talk) 03:53, 21 August 2020 (UTC)
- Agree. It doesn't work well with statements for church bell recordings either. --- Jura 16:34, 15 August 2020 (UTC)