W3C home > Mailing lists > Public > public-html-comments@w3.org > May 2010

Re: Can accessing the device microphone and camera be added to HTML5?

From: Jock Murphy <jockm@stufflabs.com>
Date: Sun, 2 May 2010 14:02:57 -0700
Message-ID: <s2u399de36d1005021402m485b5dd5qc2834c509ba26d6b@mail.gmail.com>
To: public-html-comments@w3.org
Well to my mind they are of the same scope as things like local storage,
canvas, and the like.  So that is why I said it in that context.

But that is a little tangential to my larger point.  Why is HTML5 still
open?  Why can't we just get this round done, and move on to the next.  And
the next, etc.

At this point as an observer it feels like we are in an odd limbo where the
spec is still open, but there feels like there is great resistance to adding
anything more to this spec.  So I would like to see a process that is based
on encouraging further progress.

On Sun, May 2, 2010 at 1:53 PM, Nathan <nathan@webr3.org> wrote:

> Jock Murphy wrote:
> > Honestly I am personally amazed that HTML5 is still open.  I mean I am
> just
> > a slightly more than average observer, but to me this long period of
> > standard forming is part of the problem.
> >
> > If I had my druthers, I would like to see the spec frozen to new
> additions,
> > spend a short but reasonable time resolving anything that needs to be
> > resolved, and then start work on HTML 5.1, or HTML 6, or HTML Codename
> Betty
> > and Veronica, or whatever it should be called next.  Get into a 12-18
> month
> > cycle for spec upgrades for a while, until we run out of major areas of
> > improvement, then things can slow down again.
> >
> > In a recent email to a friend I outlined things I would love to see
> > addressed, but didn't feel were likely until after HTML5 was done:
> >
> >
> >    - APIs for Capturing Audio, Video, and Stills
> >    - Support for non mouse input (accelerometers, gestures, etc)
> >    - The idea of a sandboxed file store, and the ability to work with
> files
> >    (I would love to be able to know the modification date of the file I
> may be
> >    uploading, or working with locally, as an example)
> >    - The ability to send and receive data over bluetooth obex, or other
> >    means
> >    - The ability to access nonfile like things (the address book for
> example
> >    - A more Java like sandbox that users can control what rights a webapp
> >    might have
> >
> > But unless one of the major browser vendors implement these things and
> then
> > get them retrospectively added to the spec, I don't personally think any
> of
> > these will get added any time soon.
> why do they needed to be added to the spec, surely if they warrant it
> then they can be worked on and standardized under different (perhaps not
> existing yet) working groups?
> Nathan

Jock Murphy
Received on Sunday, 2 May 2010 21:03:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:26:26 UTC