Re: [epub32] updated deprecated text from Johnson, Rick on 2018-04-22 (public-epub3@w3.org from April 2018)

From: Johnson, Rick <Rick.Johnson@vitalsource.com>
Date: Sun, 22 Apr 2018 01:29:30 +0000
To: "public-epub3@w3.org" <public-epub3@w3.org>
CC: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
Message-ID: <747F2903-D253-4D4B-80DF-BC4CD079646B@ingramcontent.com>

As we keep debating this question, I’m wondering:  Is there any awareness of someone considering creating a new reading system in the period between now and when WP/PWP/EPUBx is finished that is not a part of the current conversations, and may be unaware of the cautionary approaches to take to these (once again) legacy features?

-Rick

From: <eb2mmrt@gmail.com> on behalf of MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
Date: Sunday, April 22, 2018 at 7:49 AM
To: "public-epub3@w3.org" <public-epub3@w3.org>
Subject: Re: [epub32] updated deprecated text
Resent-From: <public-epub3@w3.org>
Resent-Date: Sunday, April 22, 2018 at 7:47 AM

I strongly think that RSs conforming to 3.2 should be allowed to support legacy features.  RSs lacking such support will be rejected by the market, since they are not usable for existing EPUB publications.

Regards,
Makoto

Received on Sunday, 22 April 2018 01:30:02 UTC