RE: [apis] A look at MSE - Gap analysis

Dear all,

Here are my results of the Indexed Database API (http://www.w3.org/TR/IndexedDB/ ) Gap analysis:

- The "Indexed Database API" is W3C Candidate Recommendation since 04 July 2013. 
- It provides APIs for a database of records holding simple values and hierarchical objects. 
- Each record consists of a key and some value. 
- Object store is the primary storage mechanism for storing data in a database.
- Supported types for Keys are: String, Number, Date and Array (only Array of primitive data types). 
- Supported types for values are: String, Date, Number, Object, Array, File, Blob and ImageData. Values are serializable following the "structured clone algorithm". 
- Supports transactions (three modes:  readonly, readwrite, versionchange).
- Supports Key generator. 
- Supports index which allows looking up records in an object store using properties of the values in the object stores records.
- Database Operations (asynchronous).
	- Object Store Storage
	- Object Store Retrieval
	- Index Referenced Value Retrieval
	- Index Value Retrieval
	- Object Store Deletion
	- Object Store Clear
	- Cursor Iteration

The  "Indexed Database API" is relevant for all requirements where offline storage on the device is needed. There are more simpler APIs for Storage like  W3C LocalStorage but with limited functionalities.
I also updated the spreadsheet https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=1 . I added the result as comment. 

I will join the call in 5 minutes.

Regards,
Louay Bassbouss

-----Original Message-----
From: Olivier Thereaux [mailto:Olivier.Thereaux@bbc.co.uk] 
Sent: Mittwoch, 30. Oktober 2013 11:46
To: public-web-and-tv IG
Subject: [apis] A look at MSE - Gap analysis

Hello,

This is a review of the Media Source Extensions as part of our gap analysis in the Media APIs TF.

Media Source Extensions is a specification developed by the HTML WG. It is currently at working draft stage and the WG is actively working on its features and scope. There should be room for us to influence the spec at this stage, if needed.

The specification "extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams."

https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html


This is a key specification for the implementation of our "Content Streaming" requirement, and it looks as though the current draft would satisfy our requirement.

MSE might be useful for our "Content Download" and "Content Recording while Watching" requirements. While the current specification would probably not make it possible, we could ask the WG to extend MSE to not only use media streams for playback in HTML5 media elements, but also to create media streams from media being played. There may be better ways. Worth discussing.

I have updated the spreadsheet over at:
https://docs.google.com/spreadsheet/ccc?key=0AvACjV6qSvmxdEctdjYwa2JOalZLOG10elE1LVRZNlE#gid=1

This review completes my action ACTION-155.

Best,
--
Olivier





-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-----------------------------

Received on Wednesday, 30 October 2013 12:56:19 UTC