Property talk:P943

From Wikidata
Jump to navigation Jump to search

Documentation

programmer
the programmer that wrote the piece of software
Descriptioncoder for a piece of software or a digital creative work such as a video game
Representsprogrammer (Q5482740), software developer (Q183888)
Data typeItem
Template parameter"Programmer(s)" in en:Template:Infobox video game
Domain
According to this template: creative work
According to statements in the property:
work (Q386724)
When possible, data should only be stored as statements
Allowed valuesno specified whitelist/blacklist (note: this should be moved to the property statements)
Example
According to this template: In the page "Assassin's Creed III" (Q40166), as a statement: programmer => David Champagne
According to statements in the property:
Civilization IV (Q2377)Soren Johnson (Q9284930)
When possible, data should only be stored as statements
SourceWikipedia infobox or the credits section of the video game itself (note: this information should be moved to a property statement; use property source website for the property (P1896))
Tracking: usageCategory:Pages using Wikidata property P943 (Q28839446)
Lists
Proposal discussionProposal discussion
Current uses200
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Type “work (Q386724): element must contain property “instance of (P31)” with classes “work (Q386724)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P943#type Q386724, SPARQL, SPARQL (new)
Property “instance of (P31): human (Q5)” declared by target items of “programmer (P943): If [item A] has this property with value [item B], [item B] is required to have property “instance of (P31): human (Q5)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P943#Target required claim P31, SPARQL, SPARQL (new)
Property “sex or gender (P21)” declared by target items of “programmer (P943): If [item A] has this property with value [item B], [item B] is required to have property “sex or gender (P21)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P943#Target required claim P21, SPARQL, SPARQL (by value), SPARQL (new)

Rename to "software creator"[edit]

IMO programmer can be ambiguous because it can indicate the current maintainer of the software or simply someone who contributes to the software, not only the creator of the software. Shouldn't be better to rename it to "software creator"?--Malore (talk) 14:25, 6 May 2018 (UTC)

Other "creator" types do not require sex or gender[edit]

Neither creator (P170) nor other "see also" creator-types linked off of it require the person being specified to have a sex or gender declaration on their record. This is an unnecessary constraint for a programmer. There is nothing about a programmer which requires them to have a declared gender in order for them to be added to their works. I propose removing it. Ruthbrarian (talk)

+1. Seems like an oversight. Allanaaaaaaa (talk) 19:55, 30 August 2019 (UTC)
+1 as well. Regarding non-famous living person there is no necessity to add this information (and some people may not want to be categorized as such). Alexander Doria (talk) 20:06, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Dsalo (talk) 20:04, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Infopetal (talk) 20:06, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Emwille (talk) 20:09, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Thematthewmurray (talk) 20:13, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Mdellabitta (talk) 20:19, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Potentially sensitive or private personal information (which gender is for some people) should not be required fields for persons in a globally public database. JohnMarkOckerbloom (talk) 20:29, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Teedeem1 (talk) 20:32, 30 August 2019 (UTC)
  • Symbol support vote.svg Support "instance of: human" is a sufficient constraint (at least until non-human programmers are a thing) Dan scott (talk) 20:45, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Anarchivist (talk) 21:23, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Ryanwick (talk) 23:53, 30 August 2019 (UTC)
  • Symbol support vote.svg Support Uomovariabile (talk) 07:06, 31 August 2019 (UTC)
  • Symbol support vote.svg Support & we probably need to clean up other uses of mandatory gender constraints - most could reasonably be suggested if retained at all. Andrew Gray (talk) 12:24, 31 August 2019 (UTC)
  • Pictogram voting comment.svg Comment it's unclear what would be the downside of suggesting to people to add A, B or unknown. At least, if one is actually interested in contributing to Wikidata and has ever done. --- Jura 14:14, 31 August 2019 (UTC)
  • Symbol support vote.svg Support マイキ (talk) 20:15, 31 August 2019 (UTC)
  • Symbol support vote.svg Support M2Ys4U (talk) 00:01, 2 September 2019 (UTC)