This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Audio-ISSUE-25 (NamingInconsistency): Interface naming inconsistency [Web Audio API] http://www.w3.org/2011/audio/track/issues/25 Raised by: Marcus Geelnard On product: Web Audio API The naming of interfaces, such as different types of audio nodes, is quite inconsistent. For instance: * With or without Audio prefix? (e.g. AudioGainNode vs DelayNode) * With or without Node suffix? (e.g. AudioPannerNode vs AudioChannelSplitter)
Here is a suggested re-naming which is more consistent. Using this naming, "Audio" is still present in AudioBufferSourceNode because "AudioBuffer" is the name of the object used by this node. "Audio" is still present in MediaElementAudioSourceNode and MediaStreamAudioSourceNode because it's important to distinguish audio from video. AudioBufferSourceNode MediaElementAudioSourceNode MediaStreamAudioSourceNode JavaScriptAudioNode ------------> ScriptProcessorNode RealtimeAnalyserNode ------------> AnalyserNode AudioGainNode ------------> GainNode DelayNode BiquadFilterNode AudioPannerNode ------------> PannerNode ConvolverNode AudioChannelSplitter ------------> ChannelSplitterNode AudioChannelMerger ------------> ChannelMergerNode DynamicsCompressorNode Oscillator ------------> OscillatorNode
(In reply to comment #1) Sounds good to me.
Thanks Marcus, fixed: https://dvcs.w3.org/hg/audio/rev/1b846a5bcf3e
OP and editor happy with changes. No objection. Closing.