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

Re: aria-describedat - Elsevier

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Wed, 19 Aug 2015 14:11:13 +0000
To: "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, "White, Jason J" <jjwhite@ets.org>, Richard Schwerdtfeger <schwer@us.ibm.com>
CC: "Gies, Edward M. (ELS-DAY)" <Ted.Gies@elsevier.com>, PF <public-pfwg@w3.org>, "DPUB mailing list (public-digipub-ig@w3.org)" <public-digipub-ig@w3.org>
Message-ID: <8345E159-7EB5-40CB-A9C2-B5FEF809FBD4@adobe.com>
I think we need to be very careful about mixing RS capabilities and MQ’s. In fact, if you look at the changes between MQ3 and MQ4, you will see that the committee itself has moved away from such a direction and instead is focusing on MQ in its purest form and not about the UA itself.

That said, I think that idea of some form of UA/RS capability mechanism that can be connected to either CSS and/or JS would be a useful feature for a variety of things - not just this one.

Leonard




On 8/19/15, 9:30 AM, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com> wrote:

>I've added the DPUB IG to this discussion so the group can chime in.
>
>In last week's meeting we discussed a strong preference for avoiding reliance on scripting. This is because many reading systems will not accept files that contain scripts. See point 8 in requirements document [1].
>
>[1] http://www.w3.org/dpub/IG/wiki/Publisher_requirements_for_extended_descriptions 
>
>Tzviya Siegman
>Digital Book Standards & Capabilities Lead
>Wiley
>201-748-6884
>tsiegman@wiley.com 
>
>
>-----Original Message-----
>From: White, Jason J [mailto:jjwhite@ets.org] 
>Sent: Wednesday, August 19, 2015 9:20 AM
>To: Richard Schwerdtfeger
>Cc: Gies, Edward M. (ELS-DAY); PF
>Subject: Re: aria-describedat - Elsevier
>
>
>> On Aug 18, 2015, at 17:37, Richard Schwerdtfeger <schwer@us.ibm.com> wrote:
>>
>>  we have talked about using CSS media quiries to hide the content 
>> unless the user turns on a feature in the host OS platform that would 
>> trigger a media query attribute which would turn on the visibility of 
>> the details element in the book.
>
>I would strongly support further development of the media query proposal, which would continue the good work accomplished by the IndieUI working group in this area.
>
>The capability hinted at in section 10.1 of the Media Queries Level 4 editors’ draft, if specified and implemented, would enable organizations such as the DAISY Consortium or the IMS Global Learning Consortium to design more elaborate media features than those which might be provided for in a W3C specification.
>
>See “Scripted custom media queries”: https://drafts.csswg.org/mediaqueries-4/ 
>and note discussion of tis topic earlier in the year by the IndieUI working group.
>
>In the EPUB context, a reading system implemented as a Web application could define custom media features in JavaScript according to conventions developed for example by one of the organizations noted above. These features could then be used in media queries within book content to select from among the available alternatives to an image, table or other construct. The user interface for specifying the user’s needs could be provided by the reading system or externally.
>
>This is entirely compatible with the existence of system or user agent-level preferences reflected in media features; the idea is that custom media queries would enable more elaborate user needs/preferences to be defined and used in specific contexts.
>
>
>________________________________
>
>This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
>
>
>Thank you for your compliance.
>
>________________________________
Received on Wednesday, 19 August 2015 14:11:46 UTC

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