reading systems or user agents? On Mon, Jan 12, 2015 at 4:55 PM, Liza Daly <liza@safaribooksonline.com> wrote: > The example in the first section is of a book application! :) > > It's definitely relevant, in the sense that anyone implementing a > sophisticated webapp (especially with a goal of being a substitute for a > native app) will need persistent, offline storage of data using a more > sophisticated interface than simple caching. On the other hand, it's not > particularly publishing-specific in the way that styling, layout, or > presentational specifications can be. That said, the lack of a > well-implemented, cross-platform web database API has definitely stifled > innovation in the open web, so I'm glad to see this work moving forward > after some damaging false starts [1]. > > Liza > > [1] > https://hacks.mozilla.org/2010/06/beyond-html5-database-apis-and-the-road-to-indexeddb/ > > > > > > > On Mon, Jan 12, 2015 at 1:53 AM, Ivan Herman <ivan@w3.org> wrote: > >> Hi guys? >> >> I was wondering whether this new recommendation is of interest for this >> group (essentially for reading systems) and I am not sure. But, well, it >> may just be a few wasted bits. So, for your information: >> >> Indexed Database API is a W3C Recommendation >> http://www.w3.org/blog/news/archives/4298 >> >> Cheers >> >> Ivan >> >> >> ---- >> Ivan Herman, W3C >> Digital Publishing Activity Lead >> Home: http://www.w3.org/People/Ivan/ >> mobile: +31-641044153 >> ORCID ID: http://orcid.org/0000-0003-0782-2704 >> >> >> >> >> >
Received on Monday, 12 January 2015 17:14:16 UTC