dret / HTML5-overview

Overview of HTML5 Standardization Activities.
The Unlicense
116 stars 7 forks source link

Remove the “Audio Processing API” document http://www.w3.org/TR/audioproc/ #22

Closed sideshowbarker closed 8 years ago

sideshowbarker commented 9 years ago

Despite the “Audio Processing API” title of the WD at http://www.w3.org/TR/audioproc/ that document does not actually itself define any API, nor does it normatively define anything at all. Instead it simply references two other documents:

Given all that and the fact that this overview already lists the Web Audio API, I think that listing of the Web Audio API is sufficient, and it’s not necessary or useful for this overview to also list the “Audio Processing API” document.

dret commented 8 years ago

surprisingly, this one is still an official W3C WD. would it address your issue to move it to the list of abandoned specs? https://github.com/dret/HTML5-overview/blob/master/MD/abandoned.md

sideshowbarker commented 8 years ago

surprisingly, this one is still an official W3C WD. would it address your issue to move it to the list of abandoned specs?

Yeah. I’m certain the WG doesn’t plan to do anything further with it. It’s an artifact of earlier disagreement in the group, and should probably have been published as a Note to begin with. Regardless, the group rightly should have since already moved it to a Note, and I wlll take the time to bring that up for discussion with the W3Cteam contacts for the group.

dret commented 8 years ago

great, thanks! i guess i'll just wait for this WD to officially change status, then.

dret commented 8 years ago

any chance this will actually happen, or is http://www.w3.org/TR/audioproc/ in eternal WD limbo?

sideshowbarker commented 8 years ago

Closing this as I don’t actually care enough to chase after the Audio WG about it.

dret commented 8 years ago

On 2016-08-23 18:48, Michael[tm] Smith wrote:

Closing this as I don’t actually care enough to chase after the Audio WG about it.

too bad but understood. too bad w3c doesn't have enough housekeeping in place to make sure the spec stream stays in a well-defined state.