Wikidata:Property proposal/screen (display) resolution, in pixels

Screen (display) resolution

Originally proposed at Wikidata:Property proposal/Generic

   Not done

Description	For example popular HD resolution is 1920x1080
Represents	Samsung Galaxy Grand Prime (Q24911258)
Data type	square integers X Y-invalid datatype (not in Module:i18n/datatype)
Template parameter	screen resolution
Domain	smartphone (Q22645)
Allowed values	from 1 to unlimited
Allowed units	unsigned integers
Example 1	1920×1080
Example 2	640×480
Example 3	1024×768
Example 4	5×10000
Source	w:en:Samsung Galaxy Grand Prime https://www.gsmarena.com/samsung_galaxy_grand_prime-6708.php
Planned use	just be fill sometimes, but this is so basic property for smartphones

Motivation

Screen resolution of a smartphone is one of the basic attributes. Vitaly Zdanevich (talk) 07:32, 24 July 2020 (UTC)

Discussion

Previous discussion: Wikidata:Property_proposal/resolution (2017), Wikidata:Property_proposal/Pixel_resolution (2018)--GZWDer (talk) 09:23, 24 July 2020 (UTC)

•  Strong oppose The problem here is that you are trying to reproduce a smartphone infobox in Wikidata, but usually a infobox field doesn't match with a Wikidata property. resolution, width, height are properties that describes a display, not a cellphone, so they should be stored on a screen item. The other way would require to create "screen width", "screen height", "screen resolution", and so on. This would be my proposal for storing this data:
  • The HTC Dream infobox on enwiki says 320 x 480 px, 3.2 in (81 mm), HVGA, 65,536 color TFT-LCD at 180 pixels per inch (ppi):
    • HTC Dream (Q727665)<display><HTC Dream display>
    • <HTC Dream display>instance of (P31)electronic visual display (Q6021804)
    • <HTC Dream display>width (P2049)320 pixel (Q355198)
    • <HTC Dream display>height (P2048)480 pixel (Q355198)
    • <HTC Dream display>length (P2043)3.2 inch (Q218593) (or a new property <diagonal size>)
    • <HTC Dream display>display technology (P5307)TFT LCD (Q1366737)
    • <HTC Dream display><pixel density>180 pixels per inch (Q7398951)
    • I don't know if there would be good creating a <depth color> property
  • The Moto G3 infobox on enwiki says 5.0" (129 mm) 1280 x 720 (294 ppi) 720p IPS panel with Corning Gorilla Glass 3:
    • Moto G (3rd generation) (Q21012827)<display><Moto G3 display>
    • <Moto G3 display>instance of (P31)electronic visual display (Q6021804)
    • <Moto G3 display>width (P2049)720 pixel (Q355198)
    • <Moto G3 display>height (P2048)1280 pixel (Q355198)
    • <Moto G3 display>length (P2043)5 inch (Q218593) (or a new property <diagonal size>)
    • <Moto G3 display>display technology (P5307)IPS panel (Q2634883)
    • <Moto G3 display>uses (P2283)<Gorilla Glass 3>(thereare item for Gorilla Glass (Q268706), but not for each version)
    • <Moto G3 display><pixel density>294 pixels per inch (Q7398951)
  • Why not I simply use these properties as qualifiers?
    • We cannot set qualifiers for qualifiers. Maybe we could want adding a end time (P582) for an specific property.
    • We mantain separated the data of an specific model, and the data of its components. It's possible that two or three models use the same display, so we avoid repeating data.
    • We do this already for other properties: CPU (P880), GPU (P2560), audio system (P7501).
    • This allows us to have fewer generic properties, instead of a lot of specialized properties: we have one clock frequency (P2149) (<clock frequency>), and not <microprocessor clock frequency>, <GPU clock frequency>, <RAM clock frequency>... I say this because "resolution" is a concept that can be applied for many phone components, not just screens.
  • --Tinker Bell ★ ♥ 07:59, 25 July 2020 (UTC)
•  Question Should this proposal be item datatype? Visite fortuitement prolongée (talk) 10:42, 26 July 2020 (UTC)
  • For the record Wide Ultra Extended Graphics Array+ (Q3124794) graphics display resolution (Q13365548) Visite fortuitement prolongée (talk) 13:26, 29 August 2020 (UTC)

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

• Please put complete examples, as in other proposals. Visite fortuitement prolongée (talk) 11:45, 26 July 2020 (UTC)
•  Oppose both @GZWDer: and @Tinker Bell: proposals, but I think @Tinker Bell:'s proposal is mostly on the right track.
  • width (P2049) and height (P2048) are physical quantities whereas pixel (Q355198) is just a logical addressing construct. I suggest instead that new properties be established similar to:
    • <Moto G3 display> has part(s) (P527) pixel (Q355198) (or a more specific subclass that characterises the sub-pixel orientation and layout) with qualifiers of:
      • <quantity along width (number of columns)> 720
      • <quantity along height (number of rows)> 1280
    • <Moto G3 display>width (P2049)70 millimetre (Q174789)
    • <Moto G3 display>height (P2048)180 millimetre (Q174789)}
  • made from material (P186) should be used instead of uses (P2283) when stating the material used for the screen display (Gorilla Glass etc):
    • <Moto G3 display>made from material (P186)<Gorilla Glass 3>
  • Modelling pixel density likely requires a new property (or properties) for either or both of linear density (Q516372) and areal quantity (Q67598689) (see volumetric number density (Q176449))
  • length (P2043) should probably not be used, in favour of a new property <hypotenuse length> (quality of hypotenuse (Q104962)) that more accurately describes the length being measured.
  • --Dhx1 (talk) 23:57, 27 July 2020 (UTC)

 Not done Same observation as previous contributors. To which I add: if the properties length, width, etc are already occupied, applies to part (P518) can be added. And the fields are completely mixed up and incomplete. In addition, is this only planned for Samsung? Replies are awaited since a long time. —Eihel (talk) 10:42, 28 August 2020 (UTC)