Property talk:P5196

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

output device
output device used to interact with a software or video game console

Description	output method or device used to interact with a software product
Represents	output device (Q778637), user interface (Q47146)
Data type	Item
Domain	According to this template: software (Q7397) and video game console (Q8076) According to statements in the property: software (Q7397), video game console (Q8076) or video game (Q7889) When possible, data should only be stored as statements
Example	Adrift (Q18693102) → Oculus Rift (Q3274429) Gran Turismo Sport (Q21563294) → PlayStation VR (Q16011703) Half-Life: Alyx (Q75653574) → Valve Index (Q63847959) Beat Saber (Q53998035) → Oculus Quest (Q63777286) Doom VFR (Q55662651) → HTC Vive (Q19414112) The Elder Scrolls V: Skyrim VR (Q56065911) → Windows Mixed Reality (Q18844946)
See also	input device (P479), writable file format (P1073), sets environment variable (P4809), protocol (P2700)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P5196 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 492 Main statement 480 97.6% of uses Qualifier 12 2.4% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “software (Q7397), video game console (Q8076), video game (Q7889)”: item must contain property “instance of (P31)” with classes “software (Q7397), video game console (Q8076), video game (Q7889)” 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/P5196#Type Q7397, Q8076, Q7889, 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/P5196#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/P5196#Scope, SPARQL

Value type “output device (Q778637)”: 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 output device (Q778637) (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/P5196#Value type Q778637, SPARQL

Value domain

This property, output device (P5196), currently has no constraint on allowed values. Still, it was created after a discussion mainly about VR headsets. Is it ok to use this property also for non-hardware interfaces, providing values such as text (Q234460), music (Q638), map (Q4006), table (Q496946), chart (Q28923) or animation (Q11425)?

I found current statements with values such as computer file (Q82753) and standard output (Q56303789); they don't necessarily involve hardware, but really aren't user interfaces either. Things like computer monitor (Q5290) and DisplayPort (Q753452) do imply visualization hardware, but aren't very descriptive as to what the displays show. Finally, desktop environment (Q205020) is a generic user interface which says nothing about the hardware used, although there is most likely some hardware involved.

For the property to be generally useful with most applications, I would suggest accepting both non-user interfaces (such as data streams or signals intended for further processing before being presented to the user) and non-hardware ones (describing the abstract elements perceived by the user rather than the physical interaction with the human senses) as long as they describe some form of output produced by the application.

Would this be in line with the original purpose of the property? Are there other properties that already serve parts of the intended usage here? I have seen no "output form" which would have been my preferred label, and I'd rather not spend time differentiating between "forms" and "methods". VR is clearly a form of interaction to me. It's also a method.

I would also suggest some (optional) qualifiers to further specify properties of the output, such as language of work or name (P407), encoding (P3294), writable file format (P1073), protocol (P2700) and connector (P2935) (the last one obviously for hardware devices only).

An item which would make good use of the property as described above is Wikidata Query GUI (Q114902143), which currently instead depends on has use (P366) in a somewhat non-intuitive way. SM5POR (talk) 18:55, 7 November 2022 (UTC)

I disagree with this scope widening making sense for the WDQS GUI as per my comment Special:Diff/1767224993. --Push-f (talk) 09:06, 8 November 2022 (UTC)