Property talk:P178
Jump to navigation
Jump to search
Documentation
developer
organization or person that developed the item
organization or person that developed the item
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “process (Q3249551), technical standard (Q317623), system (Q58778), model (Q1979154), guideline (Q1630279), group of video games (Q116741534), concept (Q151885), software project (Q63437139), product model (Q10929058), identifier (Q853614), computing platform (Q241317), user interface (Q47146), artificial object (Q16686448), cultivar (Q4886), mobile app (Q620615), technical specification (Q20819677), group of artificial physical objects (Q66661745)”: item must contain property “instance of (P31), subclass of (P279)” with classes “process (Q3249551), technical standard (Q317623), system (Q58778), model (Q1979154), guideline (Q1630279), group of video games (Q116741534), concept (Q151885), software project (Q63437139), product model (Q10929058), identifier (Q853614), computing platform (Q241317), user interface (Q47146), artificial object (Q16686448), cultivar (Q4886), mobile app (Q620615), technical specification (Q20819677), group of artificial physical objects (Q66661745)” 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/P178#Type Q3249551, Q317623, Q58778, Q1979154, Q1630279, Q116741534, Q151885, Q63437139, Q10929058, Q853614, Q241317, Q47146, Q16686448, Q4886, Q620615, Q20819677, Q66661745, SPARQL
Value type “human (Q5), organization (Q43229), community (Q177634)”: 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 human (Q5), organization (Q43229), community (Q177634) (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/P178#Value type Q5, Q43229, Q177634, SPARQL
Contemporaries:
if [item A] has this property (developer (P178)) 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 (developer (P178)) 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/P178#Contemporary, 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/P178#Entity types
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/P178#Scope, SPARQL
|
If property value equals to TigerQiuQiu (Q116175936) then claim copyright license (P275) = proprietary license (Q3238057) will be created automatically. Testing: TODO list |
|
|
If property value equals to TigerQiuQiu (Q116175936) then claim copyright status (P6216) = copyrighted (Q50423863) will be created automatically. 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.) |
Also other items
[edit]I believe "product" is too commercial a term. Can one not develop or invent things which are not sold as "products"? I've changed it to the neutral term "item," accordingly. Shawn in Montreal (talk) 22:51, 3 March 2013 (UTC)
- I can see no issue with using this to specify the developer in any situation. Danrok (talk) 16:03, 29 August 2013 (UTC)
- Depends on one's interpretation of developer. Do you have examples where you would need it outside the domain of products? LaddΩ chat ;) 22:38, 23 March 2014 (UTC)
building developer?
[edit]This property seems to be used for building developers, construction client (Q15587490)? See, e.g., One World Trade Center (Q11245). — Finn Årup Nielsen (fnielsen) (talk) 22:36, 6 January 2014 (UTC)
- For building and structures, rather use architect (P84) or structural engineer (P631). LaddΩ chat ;) 22:38, 23 March 2014 (UTC)
- Eh, Wot!? architect (P84) or structural engineer (P631) is something entirely different than a construction client (Q15587490). There are presently no name for construction client (Q15587490) in English. French has "Maîtrise d'ouvrage" and German "Bauherr" (like Danish "Bygherre"). At least "Bygherre" is not at all architect (P84) or structural engineer (P631). — Finn Årup Nielsen (fnielsen) (talk) 12:48, 24 March 2014 (UTC)
- Are there any other concerns against the use of this property? --MB-one (talk) 22:22, 26 November 2018 (UTC)
- Owner builder is a fundamentally different idea. A software developer is a person or group actually making a software product, while owner is (as far as I understand) someone who just organizes the building process. So yes, I have concerns against mixing the two concepts. —Tacsipacsi (talk) 21:16, 30 November 2018 (UTC)
- @Tacsipacsi: I will propose a new property, then. Thank you. --MB-one (talk) 14:15, 3 December 2018 (UTC)
- Owner builder is a fundamentally different idea. A software developer is a person or group actually making a software product, while owner is (as far as I understand) someone who just organizes the building process. So yes, I have concerns against mixing the two concepts. —Tacsipacsi (talk) 21:16, 30 November 2018 (UTC)
- Are there any other concerns against the use of this property? --MB-one (talk) 22:22, 26 November 2018 (UTC)
- Eh, Wot!? architect (P84) or structural engineer (P631) is something entirely different than a construction client (Q15587490). There are presently no name for construction client (Q15587490) in English. French has "Maîtrise d'ouvrage" and German "Bauherr" (like Danish "Bygherre"). At least "Bygherre" is not at all architect (P84) or structural engineer (P631). — Finn Årup Nielsen (fnielsen) (talk) 12:48, 24 March 2014 (UTC)
Developer for a product or structure
[edit]I noticed in Polish this property is translated as "deweloper", which is strictly a building developer. Should we change that to "producent", more in things sense, than building? Holek (talk) 16:04, 5 December 2014 (UTC)
Multiple developers
[edit]E.g. Q1686799 was developed by one company and is now developed by an organization. How would you define that?
Software done from scratch by someone and then developed by someone else
[edit]The property "Developer" should be matched with the starting developer or there is another more suitable property in a case such this?--Malore (talk) 19:09, 7 February 2017 (UTC)
Subject item
[edit]@Mike Novikoff: Regarding Special:Diff/1017286711, video game developer (Q210167) is distinct from video game developer (Q58287519), isn’t it? Jean-Fred (talk) 23:27, 21 September 2019 (UTC)
- It is. I've reverted my edit. — Mike Novikoff 23:57, 21 September 2019 (UTC)
French label
[edit]Following this request for comments, the French label now includes the male and the female form. PAC2 (talk) 04:34, 15 June 2022 (UTC)