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://secure.wiley.com/email-disclaimers>
> ------------------------------
>