Re: Aiding early implementations of the web audio API

On Thu, May 17, 2012 at 6:23 AM, Alistair MacDonald <al@signedon.com> wrote:

> We want to get a good idea of any major issues that may block/prevent
> vendors from implementing the spec.
>
> Naturally everyone has different ideals and preferences on various
> details of the spec, which we will continue to work together to unify
> as we go forward.
>
> This thread however is specifically to take a higher-level look at
> things that could potentially be show-stoppers, or serious
> pressure-points with regards the implementation.
>

I've got nothing to add over the issues that have already been raised.

If I was to call out a high-level issue, it would be that the current
document is mainly developer documentation and doesn't contain the
information that distinguishes a spec from developer documentation, such as
the details needed to create and test interoperable implementations.
(Although this problem was identified a long time ago, I guess the progress
to date has mainly been adding and refining features.) There's no short-cut
to fixing this other than working through the specific issues that have
already been raised, and the sooner that happens the better.

To understand the priority of specific issues, we can divide them into
those that affect the underlying architecture and those that don't, the
latter being less important than the former. The latter includes the
details of specific processing algorithms and details of syntax. The former
includes almost everything else.

Rob
-- 
“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]