canvas 2d context
Encrypted Media Extensions
HTML 5 spec
HTML 5: The Markup Language
HTML WG website
HTML5 differences from HTML4
HTML5 Spec - PR Blockers
Media Source Extensions
pre-LC1 alt techniques
pre-LC1 authoring guide
pre-LC1 HTML 5 spec
Erika Doyle Navara
Philippe Le Hégaret
Joshue O Connor
__This issue may depend on the resolution of ISSUE-16 (Is the offline application spec within scope?)__
Should the client-side database storage section of the specification clearly outline what SQL statements _must_ be supported by implementors?
If so what are the MUSTs vs. SHOULDs?
Raised by Mikko Honkala via email:
> The current spec only notes: "Note: A future version of this
> specification will probably define the exact SQL subset required in more
> This is not a good position, especially since implementations are
> starting to pop up. On a high level, we need requirements and further
> proposals for the subset that is going to get specified as a MUST level
> requirement in the spec.
Mikko Honkala suggested:
> My kick-off proposal would be to start with the number 3 : "The SQL
> subset supported by SQLite", combined with their support for full - text
> And making BEGIN/COMMIT/ROLLBACK no-ops, since transactions are
> built-in to the API.
Add notes (no markup allowed, URIs get automatically hyperlinked):
using RAISED to represent lower priority as discussed in http://lists.w3.org/Archives/Public/public-html-wg-issue-tracking/2008Aug/0005.html