Wikidata:Property proposal/output method

output method

Originally proposed at Wikidata:Property proposal/Creative work

Done: output device (P5196) (Talk and documentation)

Description	output method or device used to interact with a software product
Represents	output device (Q778637)
Data type	Item
Domain	software (Q7397) and video game console (Q8076)
Example	Adrift (Q18693102) → Oculus Rift (Q3274429)
See also	input device (P479)

Motivation

Needed to claim what software supports certain peripherals such as VR headsets (these are not always platforms). Danrok (talk) 14:03, 25 March 2018 (UTC)[reply]

Discussion

Notified participants of WikiProject Video games Danrok (talk) 14:06, 25 March 2018 (UTC)[reply]

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. Danrok (talk) 14:55, 25 March 2018 (UTC)[reply]

Question How do this property work with other devices. Force Feedback controls, Joystick, Wheels, iFeel Mice, Novint Falcon, flight sticks, and motion control platforms. Rumble motors. Light up keyboards, mice, and headphones. What about arcade games like Dance Dance Revolution with the lighting controls? What aspect of the Dreamcast's VMU or the Wii U's GamePad does this cover? Motion Tennis output to the Apple TV from the iPhone[1]. How about all apps with Chromecast support? Dispenser (talk) 14:46, 25 March 2018 (UTC)[reply]
I'd suggest that you would use either input device (P479) or this proposed property based on the primary function of the device, i.e. a haptic control pad is primarily an input device, whereas a printer is primarily an output device (even though most now have displays) Danrok (talk) 15:04, 25 March 2018 (UTC)[reply]
Grand Theft Auto V (Q17452) puts on a light show dependent on game state. On the other side, the Oculus Rift's 9DOF IMU is occasionally used as the controller method and there are some demos using the built-in microphone. Dispenser (talk) 18:30, 31 March 2018 (UTC)[reply]
I'm not totally sure this is really the best possible property to do this but I failed to come up with anything better, so maybe my feeling is wrong. Therefore Support as long no one has a better idea. -- MichaelSchoenitzer (talk) 15:39, 25 March 2018 (UTC)[reply]
Support David (talk) 17:14, 25 March 2018 (UTC)[reply]
@Danrok:_What difference do you make between a 3D game and a game that « supports » VR headset ? author TomT0m / talk page 19:50, 25 March 2018 (UTC)[reply]
@TomT0m: Some games (and software) specifically support VR headsets and their respective controllers, and some may not be playable without. This is because the user interface is designed to work with VR hardware instead of the usual keyboard/mouse. Some software is designed and coded from scratch for use with VR only, e.g. Rec Room. Other "standard" games have had VR support added on, e.g. Elite Dangerous. Some games have a specific VR release version, e.g. Fallout 4 VR Danrok (talk) 20:55, 25 March 2018 (UTC)[reply]
Comment Something like this does seem to be needed. However, given the above comments what about a more general "supported device" (and possibly "required device") property? ArthurPSmith (talk) 14:25, 26 March 2018 (UTC)[reply]
- Do "supported device" and "required device" already exist? My problem with "output method" is that the VR controllers are _input_ devices. SharkD Talk 19:30, 2 April 2018 (UTC)[reply]
  - No, those don't exist - but as the proposal noted, input device (P479) is there, so I suppose a matching output property makes sense... ArthurPSmith (talk) 15:12, 4 April 2018 (UTC)[reply]
Support Macrike (talk) 19:14, 18 May 2018 (UTC)[reply]