- From: Romain <rdeltour@gmail.com>
- Date: Sun, 30 Jul 2017 14:00:35 +0200
- To: W3C Publishing Working Group <public-publ-wg@w3.org>
- Cc: Benjamin Young <byoung@bigbluehat.com>, Hugh McGuire <hugh@rebus.foundation>, Daniel Weck <daniel.weck@gmail.com>
- Message-Id: <464E32A3-C298-4B56-887F-3879BEA1740B@gmail.com>
And Resilient Web Design (implemented as a PWA, offlinable, with an app manifest): https://resilientwebdesign.com/ <https://resilientwebdesign.com/> It could be worth gathering all these links on a wiki page somewhere? Romain. > On 29 Jul 2017, at 08:21, Daniel Weck <daniel.weck@gmail.com <mailto:daniel.weck@gmail.com>> wrote: > > Lest not forget > https://serviceworke.rs <https://serviceworke.rs/> > :) > > (also open-source @ Github) > > /Daniel > > On 28 Jul 2017 8:58 pm, "Benjamin Young" <byoung@bigbluehat.com <mailto:byoung@bigbluehat.com>> wrote: > Hey Hugh, > > > > I like the approach of using actual books already published on the Web as potential “proof case” examples for various implementations options—especially when measured from their current instantiations to whatever-it-is-we’re-trying-to-experiment-on. :) > > > > I’m guessing that you have access to the source content for that book, so you’d be the point person on knowing the distance between it and any proposed solution. > > > > I’ve been occasionally referencing (in my own off-list…so far…exploration) the following openly licensed texts: > > http://guide.couchdb.org/ <http://guide.couchdb.org/> (CC BY 3.0) > > http://eloquentjavascript.net/ <http://eloquentjavascript.net/> (CC BY-NC 3.0) > > > > It would be great to have many more such examples—especially of less linear, more internally (and externally!) referential texts. > > > > Forking some of these existing books and iterating toward what we want, might be a helpful path forward and minimize the “meta” weeds we keep wandering into. :) > > > > Cheers! > > Benjamin > > <> > From: Hugh McGuire [mailto:hugh@rebus.foundation <mailto:hugh@rebus.foundation>] > Sent: Friday, July 28, 2017 3:19 PM > To: Garth Conboy <garth@google.com <mailto:garth@google.com>> > Cc: Dave Cramer <dauwhe@gmail.com <mailto:dauwhe@gmail.com>>; Laurent Le Meur <laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org>>; W3C Publishing Working Group <public-publ-wg@w3.org <mailto:public-publ-wg@w3.org>> > Subject: Re: Web Publications via HTML Imports > > > > Dave, > > > > Here is a live “Web Publication” awaiting direction from this group on how to implement itself correctly to meet a WP specification: > > https://book.pressbooks.com <https://book.pressbooks.com/> > > > > Would getting the above to do what you have suggested be easy or hard? (That is a real question …) > > > > On Mon, Jul 24, 2017 at 11:03 AM, Garth Conboy <garth@google.com <mailto:garth@google.com>> wrote: > > Very interesting Dave! > > > > Doesn't obviate a manifest; maybe points in the "in HTML" direction for the rest of the manifest stuff (e.g., list of other resources) [but certainly could be linked too], and is a quite possible approach to the spine. > > > > Best, > > Garth > > > > On Mon, Jul 24, 2017 at 10:44 AM, Dave Cramer <dauwhe@gmail.com <mailto:dauwhe@gmail.com>> wrote: > > On Mon, Jul 24, 2017 at 5:56 AM, Laurent Le Meur <laurent.lemeur@edrlab.org <mailto:laurent.lemeur@edrlab.org>> wrote: > > > > - this import mechanism, when supported by a browser, fetches the complete set of imported resources. This is not really the need expressed (-> to list the resources and enable selective fetch). > > > > > > My little example happened to show fetching all the imports, but it would be very easy to fetch a subset, one at a time, etc. It's completely controlled by script. > > > > Best regards, > > > > Dave > > > > > > > > > > > > > -- > > -- > > Hugh McGuire > > https://rebus.community <https://rebus.community/> > +1.514.464.2047 <tel:+1%20514-464-2047>
Received on Sunday, 30 July 2017 12:01:03 UTC