On October 29, 2013 at 10:02:14 AM, Henri Sivonen (hsivo...@hsivonen.fi) wrote: > >On Tue, Oct 29, 2013 at 1:39 AM, Ralph Giles wrote: >> On 2013-10-28 2:11 PM, L. David Baron wrote: >>> API for Media Resources 1.0 >>> http://www.w3.org/TR/mediaont-api-1.0/ >... >> Thus I think we can be positive about this recommendation > >I would prefer to abstain or otherwise not endorse this specification >for the following reasons: >* It doesn't appear to integrate with HTML element interfaces and >media fetching algorithms. >* It seems unnecessary to standardize an API of this level of >abstraction for Web apps that access server-side metadata repositories >that are affiliated with the entity that serves the JavaScript >program. The JavaScript program might as well have >application-specific code. >* This API appears to have Java-oriented bits and doesn't embrace the >latest JS WebIDL API design thinking. >* The API has a synchronous version. >* There are RDF-style URI type identifiers. >* It's not clear that this API would suit our use cases e.g. in >Firefox OS gallery or music player. > >I would reply "abstain" and "don't plan to implement" for this API and >on the XML related specs in this batch.
FWIW, Mike Smith of the W3C told them pretty much the above on the AC list - and made them add the following to the status section: “Nethertheless this API is not expected to be implemented natively in the browser code.” Doesn’t help much - but the authors and the W3C are well aware that this spec has little or no implementer interest. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
