Property talk:P412

From Wikidata
Jump to navigation Jump to search

Documentation

voice type
person's voice type. expected values: soprano, mezzo-soprano, contralto, countertenor, tenor, baritone, bass (and derivatives)
Representsvoice type (Q1063547)
Data typeItem
Domainhuman (Q5), fictional character (Q95074) or role (Q1707847)
Allowed values
ExampleEnrico Caruso (Q170726)tenor (Q27914)
Sarah Brightman (Q151814)soprano (Q30903)
Tracking: sameCategory:Wikidata - Value comparison: Match: Voice type (Q42533358)
Tracking: usageCategory:Pages using Wikidata property P412 (Q21084918)
See alsoFach vocal classification (P1731)
Lists
Proposal discussionProposal discussion
Current uses
Total37,391
Main statement36,25197% of uses
Qualifier1,1313% of uses
Reference9<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “voice type (Q1063547): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value voice type (Q1063547) (or a subclass thereof). (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/P412#Value type Q1063547, 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/P412#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P412#Scope, SPARQL
Without date of birth and sex or gender data
(Help)
Violations query: SELECT ?item { ?item wdt:P412 []. FILTER NOT EXISTS { ?item wdt:P569 [] } FILTER NOT EXISTS { ?item wdt:P21 [] } ?item wdt:P31 wd:Q5. }
List of this constraint violations: Database reports/Complex constraint violations/P412#Without date of birth and sex or gender data

single value[edit]

i removed the single value constraint. persons can have multiple voice types. --Akkakk 12:18, 4 June 2013 (UTC)[reply]

occupation singer[edit]

obviously all persons with this property must be singers and have occupation (P106) with singer (Q177220). – The preceding unsigned comment was added by Giftzwerg 88 (talk • contribs).

I´d like to change it to P106 with singer (Q177220) or any subclass like opera singer (Q2865819) --Giftzwerg 88 (talk) 21:00, 25 September 2014 (UTC)[reply]

Fach[edit]

How can one insert the Fach of a person? e.g. Violetta Villas (Q217750) Fach coloratura soprano (Q58192) -- – The preceding unsigned comment was added by Pasleim (talk • contribs).

You can´t do it the right way. Some people have done it by using voice type (P412), instance of (P31), or occupation (P106) but this is not right. occupation (P106) of Violetta Villas (Q217750) ist not coloratura soprano (Q58192), occupation is "singer" or in other cases it might be opera singer (Q2865819). voice type (P412) of Violetta Villas (Q217750) is not coloratura soprano (Q58192), this value is determined by tessitura (Q12298060). So a female singer might have the range of a soprano, mezzosoprano, or alto. There is a proposal out there at https://www.wikidata.org/wiki/Wikidata:Property_proposal/Person#Stimmfach_.28Q1748957.29 to create a new property to connect "fach" to a person. --Giftzwerg 88 (talk) 18:51, 30 January 2015 (UTC)[reply]
Done: Fach vocal classification (P1731). --UV (talk) 20:49, 1 March 2015 (UTC)[reply]

Opera Characters[edit]

This property is also used to describe the voice type of opera characters, e.g. in Anhilte (Q20826317) or Papageno (Q2455222). Is this okay or should we clean it up? --Pasleim (talk) 14:55, 1 February 2016 (UTC)[reply]

This seems the right property to me, but if possible the 'occupation' constraint should not apply if the 'instance of' constraint matched 'fictional/historical character'. I do not know how to do this, but someone might. Arlo Barnes (talk) 22:38, 11 November 2019 (UTC)[reply]
The way the property is defined it seems limited to humans and not roles or characters. That said operatic character (Q50386450) states this as one of the appropriate properties to use with that concept. Modifying the constraints for this property would get rid of all those warnings, but that might go against the intent. Alternately we could maybe decide to propose a new property, something like "voice type specified," to set apart the concept of a human's vocal characteristics from a creator's statement of a voice type needed to perform a role or part. I think we'd need to be broader than operatic characters--musicals, e.g.--in scoping such a property. But there's the inertia of almost 13,000 usages of voice type (P412) with operatic character (Q50386450). Tough one.--Jsoenyun (talk) 15:55, 5 November 2020 (UTC)[reply]