- From: Peter Krautzberger <peter@krautzource.com>
- Date: Thu, 3 Aug 2017 10:44:38 +0200
- To: W3C Publishing Working Group <public-publ-wg@w3.org>
- Message-ID: <CABOtQmHus==tU=b86L3HOwNpZkkV7mCNuLo6P-f13XTgeeHsgA@mail.gmail.com>
Hi, Splitting this one off the thread "Web Publications via HTML Imports" so the group can be notified if people add links. I've added a link to "17776" (What Football Will Look Like in the Future) to https://github.com/w3c/publ-wg/wiki/Hackable-Publications. It does not fit the page's title since it's not "hackable" so perhaps it should be listed elsewhere. i added it because all examples so far have equivalent print versions and this one likely won't. I realize it might be too extreme to be covered by whatever web publications turn out to be; I personally hope I'm wrong. In any case it would be a useful edge case to consider. Best, Peter. 2017-07-31 21:28 GMT+02:00 Benjamin Young <byoung@bigbluehat.com>: > Great idea on the Wiki page, Ivan: > > https://github.com/w3c/publ-wg/wiki/Hackable-Publications > > > Added some of the books mentioned here. > > > Hugh, I'd be curious to know what a Pressbook would look like "on disk" > (outside of the WordPress MySQL storage). > > > Constructing publications via a CMS will certainly be common (I'd reckon), > but I'm currently trying to see the trees for the forests. ;) > > Feel free to add any books I've missed! > > Benjamin > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > ------------------------------ > *From:* Ivan Herman <ivan@w3.org> > *Sent:* Monday, July 31, 2017 5:20:54 AM > *To:* Romain > *Cc:* W3C Publishing Working Group; Benjamin Young; Hugh McGuire; Daniel > Weck > > *Subject:* Re: Web Publications via HTML Imports > > > On 30 Jul 2017, at 14:00, Romain <rdeltour@gmail.com> wrote: > > And Resilient Web Design (implemented as a PWA, offlinable, with an app > manifest): > > https://resilientwebdesign.com/ > > It could be worth gathering all these links on a wiki page somewhere? > > > +1. The WG Wiki is at our disposal: > > https://github.com/w3c/publ-wg/wiki > > Ivan > > > Romain. > > > On 29 Jul 2017, at 08:21, Daniel Weck <daniel.weck@gmail.com> wrote: > > Lest not forget > https://serviceworke.rs > :) > > (also open-source @ Github) > > /Daniel > > On 28 Jul 2017 8:58 pm, "Benjamin Young" <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/ (CC BY 3.0) >> >> 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] >> *Sent:* Friday, July 28, 2017 3:19 PM >> *To:* Garth Conboy <garth@google.com> >> *Cc:* Dave Cramer <dauwhe@gmail.com>; Laurent Le Meur < >> laurent.lemeur@edrlab.org>; W3C Publishing Working Group < >> 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 >> >> >> >> 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> 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> wrote: >> >> On Mon, Jul 24, 2017 at 5:56 AM, Laurent Le Meur < >> 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 >> >> +1.514.464.2047 <+1%20514-464-2047> >> > > > > ---- > Ivan Herman, W3C > Publishing@W3C Technical Lead > Home: http://www.w3.org/People/Ivan/ > mobile: +31-641044153 <+31%206%2041044153> > ORCID ID: http://orcid.org/0000-0003-0782-2704 > >
Received on Thursday, 3 August 2017 08:45:26 UTC