W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > February 2011

[Bug 11958] New: Rather than use the USB/rs232 keywords, I would recommend going with the keyword "peripheral" for any device attached to the computer. This way it would not matter if the device in question is USB, 1394, or something platform exclusive. This will future p

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Feb 2011 12:37:40 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-11958-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11958

           Summary: Rather than use the USB/rs232 keywords, I would
                    recommend going with the keyword "peripheral" for any
                    device attached to the computer. This way it would not
                    matter if the device in question is USB, 1394, or
                    something platform exclusive. This will future p
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#dev
                    ices
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: other Hixie drafts (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org


Specification:
http://www.whatwg.org/specs/web-apps/current-work/complete/commands.html
Section:
http://www.whatwg.org/specs/web-apps/current-work/complete.html#devices

Comment:
Rather than use the USB/rs232 keywords, I would recommend going with the
keyword "peripheral" for any device attached to the computer. This way it
would not matter if the device in question is USB, 1394, or something platform
exclusive. This will future proof the input as well, since it is the data
being fetched is what is important, not the connection method. Data being
fetched should be broken down into what it is. For example, audio, video (just
a video stream), fs, media (comprised of several media streams, such as audio,
video, location, text, etc), text, image, location (GPS device), spacial
(anything returning spacial data, rangefinder, radar, lidar, etc). I would
also recommend using multiple types when specifying a device. For a webcam, do
type="media audio video" to ensure that even if the camera does not support
audio, the device chooser will then also let you choose a microphone. For
playing a media file such as a music file do type="audio image text", this
would allow the device to expect an audio file with cover art and lyrics. That
is all I have to ramble about. I hope this is of some help. ~Trevor Downs

Posted from: 71.198.1.49

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 2 February 2011 12:37:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 February 2011 12:37:42 GMT