W3C home > Mailing lists > Public > public-digipub-ig@w3.org > August 2016

Re: [Moderator Action] [dpub] 20160822 agenda

From: Charles LaPierre <charlesl@benetech.org>
Date: Fri, 26 Aug 2016 12:14:06 +0000
To: Leonard Rosenthol <lrosenth@adobe.com>
CC: "Cramer, Dave" <Dave.Cramer@hbgusa.com>, Boris Anthony <boris@rebus.foundation>, Ivan Herman <ivan@w3.org>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>
Message-ID: <6CA8F290-B330-4DD7-A678-C77CBFC38127@benetech.org>
But if we are able to build a new package on the fly to give to the user with assistive technologies a package with all the audio and video stripped out for example why couldn’t we build a new package with additional annotations that reference the items within which are unable to be modified?

Thanks
EOM

Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
E-mail: charlesl@benetech.org
Twitter: @CLaPierreA11Y
Skype: charles_lapierre
Phone: 650-600-3301



> On Aug 25, 2016, at 1:50 PM, Leonard Rosenthol <lrosenth@adobe.com> wrote:
> 
> If the annotations modify the “package”, and there are either technical or licensing reasons that prevent the modification of that “package” – yes.
> 
> Of course, that doesn’t mean that a given UA/RS couldn’t keep the annotations physically separate from the publication and “merge them on the fly”.
> 
> Leonard
> 
> On 8/25/16, 4:25 PM, "Cramer, Dave" <Dave.Cramer@hbgusa.com> wrote:
> 
>    On 8/25/16, 3:56 PM, "Leonard Rosenthol" <lrosenth@adobe.com> wrote:
> 
>> Because not all authors/publishers of PWPs will necessarily allow them to
>> be modified.
> 
> 
>    Most of what Boris mentioned sounded to me more like annotations than
>    modification of content. Are there use cases for preventing annotations of
>    a PWP?
> 
>    Dave
> 
>    This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.
> 
> 


Received on Friday, 26 August 2016 12:14:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:36:30 UTC