Property talk:P176
Latest comment: 1 year ago by Thadguidry in topic Instances of Currency should be allowed
Documentation
manufacturer
(main or final) manufacturer or producer of this product
(main or final) manufacturer or producer of this product
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “organization (Q43229), human (Q5), fictional character (Q95074), group of fictional characters (Q14514600), artisan (Q1294787), profession (Q28640), animal (Q729), industry (Q268592), factory (Q83405)”: 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 organization (Q43229), human (Q5), fictional character (Q95074), group of fictional characters (Q14514600), artisan (Q1294787), profession (Q28640), animal (Q729), industry (Q268592), factory (Q83405) (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/P176#Value type Q43229, Q5, Q95074, Q14514600, Q1294787, Q28640, Q729, Q268592, Q83405, SPARQL
Contemporaries:
if [item A] has this property (manufacturer (P176)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (manufacturer (P176)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P176#Contemporary, SPARQL
Conflicts with “instance of (P31): rose cultivar (Q26817508)”: 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/P176#Conflicts with P31, search, 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/P176#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/P176#Scope, SPARQL
Type “concrete object (Q4406616), product model (Q10929058), model series (Q811701), software (Q7397), physical object (Q223557), fictional product model (Q116680403)”: item must contain property “instance of (P31), subclass of (P279)” with classes “concrete object (Q4406616), product model (Q10929058), model series (Q811701), software (Q7397), physical object (Q223557), fictional product model (Q116680403)” 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/P176#Type Q4406616, Q10929058, Q811701, Q7397, Q223557, Q116680403, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Contemporaries:
if [item A] has this property (P176) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (P176) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
List of violations of this constraint: Database reports/Constraint violations/P176#Contemporary, SPARQL
| ||||||||||||||||||||||||||||||||||
PFD
editPlease comment at Wikidata:Properties_for_deletion#manufacturer_.28P176.29_and_main_building_contractor_.28P193.29. --Izno (talk) 11:24, 5 May 2016 (UTC)
Property constraint values
editI think that the allowed values for "property constraint" > "type constraint" should not include only Q112276019 and Q10929058 but also Q811701, because also model series can have a manufacturer (for an example, see Q3978395 and Q6475). Danysan1 (talk) 15:57, 15 October 2022 (UTC)
Instances of Currency should be allowed
editFor instances of currency (Q8142) I think it makes sense to add them as an exception to the constraint. One way to do this would be perhaps allow instances that are a subclass of government agency (Q327333). This would allow using manufacturer (P176) on currency (Q8142) instances to state which government entity manufactures a currency (I.E. prints the money). And not only the central bank/issuer (P562). See for example the violation currently on: United States dollar (Q4917) and renminbi (Q39099) Thadguidry (talk) 05:36, 14 June 2023 (UTC)