- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Fri, 21 Jan 2011 15:01:24 +0100
- To: Thomas Steiner <tomac@google.com>
- Cc: Media Fragment <public-media-fragment@w3.org>
Hi Thomas, On Fri, Jan 21, 2011 at 2:51 PM, Thomas Steiner <tomac@google.com> wrote: > Hi Silvia, > >> Note that none of this actually applies cropping - the cropping is a >> natural effect of scaling and rotating in CSS. > Sure. Same goes for my region highlighting demo: > http://tomayac.com/mediafragments/ (check it in Safari, Chrome will > display the DIVs below the video). > >> I don't really see it >> being relevant to us other than to indicate that all of the spatial >> fragmentation that somebody may be after can already be done in CSS >> and does not need URIs. > Yepp, I think this was part of Ian's point, too. The thing maybe is: > if it /can/ be done in CSS (which also applies to spatial fragments of > images), isn't part of the WG's vision to encourage to enable it > server-side (for the cropping part)? I don't understand the connection. If it can be done in CSS, then it's a display mechanism. The URL linking mechanism is a very different use case, in particular for sharing and embedding etc. I don't really see why the availability of one should have any influence on the other. Can you explain? Cheers, Silvia. > Real question, not rhetoric > question. Quoting from the spec draft introduction "It is expected > that over time [...] Web servers [...] will be extended to adhere to > the full specification". > > Thanks, > Tom > > -- > Thomas Steiner, Research Scientist, Google Inc. > http://blog.tomayac.com, http://twitter.com/tomayac >
Received on Friday, 21 January 2011 14:02:11 UTC