This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22969 - Clarify influence/reference to OpenAL, IPR considerations
Summary: Clarify influence/reference to OpenAL, IPR considerations
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-15 08:39 UTC by Olivier Thereaux
Modified: 2014-10-28 17:17 UTC (History)
0 users

See Also:


Attachments

Description Olivier Thereaux 2013-08-15 08:39:43 UTC
The Web Audio API makes several references (mostly in informational text) about OpenAL and the spec editor has often mentioned it as one of the inspirations for the architecture of the API.

OpenAL was “ done in spirit of open source and implementations distributed in LGPL“ but the licensing/IPR is not clear - and most of the people involved with OpenAL have since moved on.

The Audio WG should review the current spec and assess whether:

* Whether the web audio API is significantly inspired by Open AL
* Whether OpenAL should be formally referred to in the specification
* Depending on the above, whether there are any IPR concerns in the architectural lineage between OpenAL and WebAudioAPI
Comment 1 Olivier Thereaux 2013-08-27 10:25:50 UTC
With the help of the W3C Legal counsel, I have done an analysis of the situation based on a recent version of OpenAL-soft (open source fork of OpenAL - OpenAL itself seems to be completely AWOL).


The four parts of the web audio API where OpenAL is mentioned are:

(in 4.15. The AudioListener Interface)
>   // same as OpenAL (default 1)
>   attribute float dopplerFactor;

> My analysis: the name dopplerFactor is indeed the same as in the OpenAL library. That said, Doppler Factor is a well-known mathematical variable, and I don't think that there is significant IP or indeed any copyright concern in naming a variable after the mathematical variable it represents. I would remove the "same as OpenAL" which seems to be neither useful nor necessary.


(in 11. Spatialization / Panning)
> A common feature requirement for modern 3D games is the ability to dynamically spatialize and move multiple audio sources in 3D space. Game audio engines such as OpenAL, FMOD, Creative's EAX, Microsoft's XACT Audio, etc. have this ability.


My analysis: I don't know if this section is useful, but it is a non-issue as far as IPR/copyright is concerned.

(in 12. Linear Effects using Convolution)
> A key feature of many game audio engines (OpenAL, FMOD, Creative's EAX, Microsoft's XACT Audio, etc.) is a reverberation effect for simulating the sound of being in an acoustic space.

Ditto above.

(In Changelog)
> date:        Mon Feb 06 16:52:39 2012 -0800
> * Add distance model constants for PannerNode according to the OpenAL spec


The changeset mentioned here is:
       https://dvcs.w3.org/hg/audio/rev/7a158cdbb064

The relevant changes in the source of the spec were:
https://dvcs.w3.org/hg/audio/rev/7a158cdbb064#l1.74
(up to line 88)

This part of the spec has since been deprecated and are now only present in the (non normative) deprecation note.

The change set mentioned above also happens to be the only one ever mentioning OpenAL.


Based on the above, my conclusion would be that there is no significant borrowing/influence from OpenAL in the web audio API, other than similarities which would occur naturally since the concepts and mathematical basis for the two are the same. This conclusion was deemed reasonable by the W3C legal team.
Comment 2 Olivier Thereaux 2013-08-27 10:27:11 UTC
(In reply to comment #1)

> Based on the above, my conclusion would be that there is no significant
> borrowing/influence from OpenAL in the web audio API, other than
> similarities which would occur naturally since the concepts and mathematical
> basis for the two are the same. This conclusion was deemed reasonable by the
> W3C legal team.

As a next step, I would suggest:

* We remove the mention "same as OpenAL (default 1)" from section 4.15
* We review whether the two mentions of OpenAL (and other engines) in informative text are needed and useful for the comprehension of the spec.
Comment 3 Olivier Thereaux 2014-10-28 17:14:18 UTC
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 4 Olivier Thereaux 2014-10-28 17:17:11 UTC
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.