Property talk:P2012
Jump to navigation
Jump to search
Documentation
cuisine
type of food served by a restaurant or restaurant chain or national food culture
type of food served by a restaurant or restaurant chain or national food culture
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “cuisine (Q1778821)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value cuisine (Q1778821) (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/P2012#Value type Q1778821, SPARQL
Scope is as main value (Q54828448): 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/P2012#Scope, 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/P2012#Entity types
Type “restaurant (Q11707), restaurant chain (Q18534542), dish (Q746549), restaurant (Q11666766), restaurant district (Q40553563), condiment (Q2596997), grocery store (Q1295201), supermarket chain (Q18043413), human food (Q8195619), online food ordering service (Q98660409)”: item must contain property “instance of (P31), subclass of (P279)” with classes “restaurant (Q11707), restaurant chain (Q18534542), dish (Q746549), restaurant (Q11666766), restaurant district (Q40553563), condiment (Q2596997), grocery store (Q1295201), supermarket chain (Q18043413), human food (Q8195619), online food ordering service (Q98660409)” or their subclasses (defined using subclass of (P279)). (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/P2012#Type Q11707, Q18534542, Q746549, Q11666766, Q40553563, Q2596997, Q1295201, Q18043413, Q8195619, Q98660409, SPARQL
Property “culture (P2596)” declared by target items of “cuisine (P2012)”: If [item A] has this property with value [item B], [item B] is required to have property “culture (P2596)”. (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/P2012#Target required claim P2596, SPARQL, SPARQL (by value)
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||
Use this property for dishes?
[edit]The property was intended to be used for restaurants. However, it seems that many have used it on food/dish items (e.g. pizza (Q177)cuisine (P2012)Italian cuisine (Q192786)), and actually some Wikipedias have already used it on food infoboxs (e.g. ky:Калып:Тамак). Should we extend the scope of this property? --Stevenliuyi (talk) 22:08, 28 April 2021 (UTC)
Notified participants of WikiProject Food --Stevenliuyi (talk) 22:09, 28 April 2021 (UTC)
- Comment Another note: the constraints on culture (P2596) have already been prompting people to use this property for food dishes instead of that one for a while. Middle river exports (talk) 13:58, 5 September 2022 (UTC)
- I would suggest part of (P361) (or a subclass thereof) would be the better model for what cuisine a food item/dish belongs to. cuisine (P2012) is currently a subproperty of field of work (P101) and therefore has a very different purpose/meaning. --Dhx1 (talk) 01:18, 29 April 2021 (UTC)
- Perhaps we can rename the property to "serves cuisine" to make it more clear? --Stevenliuyi (talk) 01:35, 29 April 2021 (UTC)
- IMHO "Cuisine" fits the bill perfectly. And I think it should not be subclass of "field of work". "Cooking" (what chefs do) is a field of work, but "Cuisine" is also practiced by folks who won't consider it their field of work. "Part of" is not appropriate at all: you would use it to express the ingredients of a dish. --Vladimir Alexiev (talk) 11:27, 18 May 2021 (UTC)
Support using for dishes. So there seem to be consensus (at least 3-against-1) for this. --Infovarius (talk) 19:55, 30 June 2021 (UTC)- Uh no, there is not yet a consensus. Ideally I would want to split the property between "serves cuisine" and "is part of cuisine". If not, then officialize that it is used for both. I am against using just part of (P361) for the same reason as Vladimir Alexiev. --GrandEscogriffe (talk) 20:05, 27 July 2022 (UTC)
- Support I would support using this for dishes. We do have culture (P2596), but this does not quite fit either because a cuisine can be a product of multiple cultures or even be something defined by types/groups of food more than cultures. --Middle river exports (talk) 22:07, 3 September 2022 (UTC)
- Support It seems like the cuisine can be part of the culture and the dish can be part of a cuisine. Both restaurants and dishes would seem to have a common property of the cuisine they are associated with. As the property implies it is a part of cuisine, it would seem to make it unnecessary to model the parts of each as it would be duplicating the information provided by the property value. It seems that that inverse would be "cuisine of" AHIOH (talk) 04:18, 11 August 2024 (UTC)