- From: David Singer <singer@apple.com>
- Date: Wed, 16 Feb 2011 15:01:11 +0800
- To: John Foliot <jfoliot@stanford.edu>
- Cc: 'Silvia Pfeiffer' <silviapfeiffer1@gmail.com>, 'Jonas Sicking' <jonas@sicking.cc>, 'Mark Watson' <watsonm@netflix.com>, 'Philip Jägenstedt' <philipj@opera.com>, 'public-html' <public-html@w3.org>
True. Happily, what I suggested does not preclude any of these possibilities. On Feb 16, 2011, at 14:31 , John Foliot wrote: > David Singer wrote: >> >> I think we should make normal things easy and complex things possible. >> >> If we set the rule that <source>s are alternatives (exclusive or) and >> tracks are additional (inclusive or, including the primary source) then >> the content author can indicate what 'works' from the point of view of >> his program. > > <Snip> > >> while it is technically true that the user-agent may be able to make >> all sorts of ingenious displays, it's not a great system design to >> assume that the UA and the user will have the time or skills to make >> the choices over lots of ingenious possibilities. > > While I understand what you are saying David, it is also important to > remember that what 'works' for the author may not work for some end users. > It strikes me that all supporting assets should be exposed to the end > user, so that they can choose what works for them. It's a balance we need > to keep in mind. > > JF > > David Singer Multimedia and Software Standards, Apple Inc.
Received on Wednesday, 16 February 2011 07:01:52 UTC