W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2012

Re: Specificity in the Web Audio API spec

From: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 1 Apr 2012 01:02:06 +1300
Message-ID: <CAOp6jLZno0JuaioY6dX3PsAS8BmfshoW5uANH1TKArnM+6aMxg@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>, "Wei, James" <james.wei@intel.com>, "public-audio@w3.org" <public-audio@w3.org>
It seems to me that the spec should define exactly what the ideal behavior
of each processing algorithm is, and ask implementations to approximate
that ideal as closely as they can. Then an implementation should be able to
implement features based solely on the spec, and get results very close to
the results of all other implementations, up to some small error.

Canvas-2d is pretty close to this. Where it isn't, it needs to be fixed.
(Font rasterization is a special case because available fonts, font
selection and font rasterization techniques intentionally vary across
platforms, partly due to different aesthetic choices on each platform. I
don't think we want platform-specific aesthetic choices creeping into our
audio APIs.)

“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]
Received on Saturday, 31 March 2012 12:02:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:58 UTC