W3C home > Mailing lists > Public > public-respimg@w3.org > October 2013

Re: [respimg] a perfect responsive solution should not tamper the HTML syntax with too much repeating information

From: Aaron Gustafson <aaron@easy-designs.net>
Date: Thu, 24 Oct 2013 22:15:06 -0400
To: Carsten Berggreen <carsten@monolith.dk>
Cc: darrel.opry@spry-group.com, public-respimg@w3.org
Message-ID: <7FA159D935684937980482BF01C423F0@easy-designs.net>
On Thursday, October 24, 2013 at 9:06 PM, Carsten Berggreen wrote:
<snip>

> Html stands for Hyper Text Markup Language... a syntax for adding markup on content. The original idea was to format the content, so headlines were seperated from paragraphs etc. All the fancy stuff with graphics etc. came later and these should be kept out of the html itself as much as possible.
> If we dont want a serverside solution for selecting the right image for the placeholder, I would strongly recommend that we somehow fix it with external CSS instead as they are reuseable and cacheable.
> 


The thing is, we are talking about _content_ not _design_.

HTML was invented to add semantic meaning to content. The images we are dealing with _are_ content. The choice of image belongs in the page because it is content (not presentation, which belongs in the CSS).

I fully understand your issue with verbosity, but markup-wise it's become relatively trivial under srcN (and becomes even more so when GZIPing). And as far as cache-ability goes, my assumption would be that browsers would cache the chosen image and you could certainly store each image option in a CDN.

Barring the introduction (and quick adoption) of a new bitmap image format that gives us the ability to deliver alternate media based on a set of conditions (as SVG does), I think we've actually gotten to a pretty sensible place.

Cheers,

Aaron

----
Aaron Gustafson
Easy Designs
@aarongustafson
Received on Friday, 25 October 2013 02:15:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:40 UTC