- From: Zheng Xu <zxu@wysebee.com>
- Date: Thu, 11 Aug 2022 17:12:32 -0400
- To: "Cholfin, Bryan" <bryan_cholfin@harvard.edu>, Paul Belfanti <pbelfanti@gmail.com>, "Siegman, Tzviya" <tsiegman@wiley.com>
- Cc: Colin Pittendrigh <sandy.pittendrigh@gmail.com>, Neustudio <susan@neustudio.com>, Leonard Rosenthol <lrosenth@adobe.com>, "public-publishingcg@w3.org" <public-publishingcg@w3.org>, "public-epub3@w3.org" <public-epub3@w3.org>, "Teixeira, Mateus" <mteixeira@wwnorton.com>, "Schindler Wolfgang Dr." <w.schindler@pons.de>
- Message-ID: <96c776d5-266b-be96-0ec1-7670a4c4f9da@wysebee.com>
I think this can be solved by retailer store if they could support as long as retailer store has list of all the resources. Or it could be possible that publisher also host some of server if the external links are pointing to their server. Some interesting things about external resources (outside of epub file) to me are: 1. how to let user know the external links are whitelisted (verified by retailer) vs suspicious links 2. how to let user still be able to navigate back to available pages if some of the chapter is from outside and broken (think about a11y as well). I kinda feel how to define certain external resource as a good citizen might be interested in spec discovery? Another thing about splitting epub file to smaller chunk is can we define a way to let reader retrieve part of the book? Think about even Android started to let user partially download part of application and started to enforce app creator to package in that way. https://developer.android.com/guide/app-bundle Cheers, Zheng On 2022-08-11 4:59 p.m., Cholfin, Bryan wrote: > > And in addition, your external links will be subject to link rot over > time. URLs will change, servers will go offline. You, the publisher, > will have the responsibility of maintaining that. > > --Bryan > > vard University Press <http://www.hup.harvard.edu/> > > *Bryan Cholfin* > Harvard University Press > 617.496.9116 > 79 Garden Street | Cambridge, MA 02138-1400 > www.hup.harvard.edu <http://www.hup.harvard.edu/> > > *From: *Paul Belfanti <pbelfanti@gmail.com> > *Date: *Thursday, August 11, 2022 at 4:48 PM > *To: *Siegman, Tzviya <tsiegman@wiley.com> > *Cc: *Colin Pittendrigh <sandy.pittendrigh@gmail.com>, Neustudio > <susan@neustudio.com>, Leonard Rosenthol <lrosenth@adobe.com>, Zheng > Xu <zxu@wysebee.com>, public-publishingcg@w3.org > <public-publishingcg@w3.org>, public-epub3@w3.org > <public-epub3@w3.org>, Teixeira, Mateus <mteixeira@wwnorton.com>, > Schindler Wolfgang Dr. <w.schindler@pons.de> > *Subject: *Re: [Minutes] Publishing Community Group Meeting - Aug 10, 2022 > > Fair. > > *Paul* > > On Thu, Aug 11, 2022 at 4:28 PM Siegman, Tzviya <tsiegman@wiley.com> > wrote: > > Universal connectivity is not something this group can solve though. > > *Tzviya Siegman* > > Information Standards Principal > > Wiley > > 201-748-6884 > > tsiegman@wiley.com > > *From:* Paul Belfanti <pbelfanti@gmail.com> > *Sent:* Thursday, August 11, 2022 3:38 PM > *To:* Colin Pittendrigh <sandy.pittendrigh@gmail.com> > *Cc:* Neustudio <susan@neustudio.com>; Leonard Rosenthol > <lrosenth@adobe.com>; Zheng Xu <zxu@wysebee.com>; > public-publishingcg@w3.org; public-epub3@w3.org; Teixeira, Mateus > <mteixeira@wwnorton.com>; Schindler Wolfgang Dr. <w.schindler@pons.de> > *Subject:* Re: [Minutes] Publishing Community Group Meeting - Aug > 10, 2022 > > ⛔ > > > > This is an external email. > > +1 on universal/rural connectivity - that's affordable > > Best, > > *Paul* > > On Thu, Aug 11, 2022 at 10:11 AM Colin Pittendrigh > <sandy.pittendrigh@gmail.com> wrote: > > The solution to no connectivity is to make rural connectivity > > On Thu, Aug 11, 2022 at 8:10 AM Colin Pittendrigh > <sandy.pittendrigh@gmail.com> wrote: > > I spent five years developing an online curriculum in > elementary computer programming on the Crow Indian > Reservation in Montana.. That curriculum failed because > none of the kids had internet connectivity at home. > > On Thu, Aug 11, 2022 at 7:31 AM Neustudio > <susan@neustudio.com> wrote: > > I work in children’s publishing, and I suspect relying > on external links would be a problem for families with > no or low-quality internet connectivity. Though I”m > intrigued by the idea of a use case where external > links would allow more exploring/customizing a book > when the setting supports data transfer. > > Since this is already allowed in the spec, what is the > role of the work group? —Susan > > On Aug 11, 2022, at 8:36 AM, Leonard Rosenthol > <lrosenth@adobe.com> wrote: > > At the end of the day it’s up to the producer of > the EPUB. > > If they want something fully self-contained, the > standard will let them do that. If they want > something that use links to external content, the > standard will let them do that. > > Of course, whether a given EPUB distribution > system will support/allow external content or > whether a given reading system will support it, is > another question. But all of that is outside the > scope of the standard. > > Leonard > > *From: *Colin Pittendrigh > <sandy.pittendrigh@gmail.com> > *Date: *Wednesday, August 10, 2022 at 7:32 PM > *To: *Zheng Xu <zxu@wysebee.com> > *Cc: > *public-publishingcg@w3.org <public-publishingcg@w3.org>, > public-epub3@w3.org <public-epub3@w3.org>, > Teixeira, Mateus <mteixeira@wwnorton.com>, > Schindler Wolfgang Dr. <w.schindler@pons.de> > *Subject: *Re: [Minutes] Publishing Community > Group Meeting - Aug 10, 2022 > > *EXTERNAL: Use caution when clicking on links or > opening attachments.* > > RE> 750mb file size limit. Bear with me. I'm a > retired database guy. > > Why can't epubs be text only, with resource URLs > to streamed images and video on remote servers? > > When I ask this question I'm invariably told "It > won't work without a wifi connection!" > > My answer is "So what?" I'm almost never away > from wifi unless I'm driving. And in that case I > shouldn't be reading anyway. Are you on a camping > trip? Read now, view video later. Video is too > big to store on a phone. Video should be > streamed. No matter what. > > On Wed, Aug 10, 2022 at 12:54 PM Zheng Xu > <zxu@wysebee.com> wrote: > > Hi all > > Thanks for attending today's meeting. > > Here is today's meeting minutes. > > https://github.com/w3c/publishingcg/blob/master/Meetings/Minutes/2022-08-10-publishingcg.md > <https://urldefense.com/v3/__https:/nam04.safelinks.protection.outlook.com/?url=https*3A*2F*2Fgithub.com*2Fw3c*2Fpublishingcg*2Fblob*2Fmaster*2FMeetings*2FMinutes*2F2022-08-10-publishingcg.md&data=05*7C01*7Clrosenth*40adobe.com*7Ccaccf28d837c427cdd5b08da7b2899b0*7Cfa7b1b5a7b34438794aed2c178decee1*7C0*7C0*7C637957711557175407*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=Y0*2F0T8ghPwgSzbrFovfx8Rn9ik59XOdjEDpj77Yh2IQ*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!N11eV2iwtfs!pB9Lbm_qmvrDT3jbymDVf2LoRtbvdbpkQWzmdc5veYHnGiHy3oE2Qsu7Kom_Ox0__PLI3T9WR-WF_p-n$> > > Please feel free to let us know if any > questions or feedback. > > > Cheers, > > Mateus, Wolfgang and Zheng > > > -- > > /* Colin (Sandy) Pittendrigh >--oO0> */ > > > -- > > /* Colin (Sandy) Pittendrigh >--oO0> */ > > > -- > > /* Colin (Sandy) Pittendrigh >--oO0> */ > > ------------------------------------------------------------------------ > > The contents of this email and any attachments are confidential > and intended only for the person or entity to whom it is > addressed. If you are not the intended recipient, any use, review, > distribution, reproduction or any action taken in reliance upon > this message is strictly prohibited. If you received this message > in error, please immediately notify the sender and permanently > delete all copies of the email and any attachments. > Click here for translations of this disclaimer. > <https://urldefense.proofpoint.com/v2/url?u=https-3A__secure.wiley.com_email-2Ddisclaimers&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=C4uQXgUAXNtbbQkRcZb0vaWguMqZEgRZCutfoNwnQQw&m=3xAbV1znkioGZl7BamYry5Lkl37R32N-RYPuKEXxBmSWcjRvMYT_obU3kBDHe47c&s=_OHkD_xy9iYVSEQofRSfoyQHAyY5x9fVSfAFMsQJY7s&e=> > > > ------------------------------------------------------------------------ >
Received on Thursday, 11 August 2022 21:12:55 UTC