-----Original Message----- >From: Aaron Boodman <[EMAIL PROTECTED]> >Sent: May 3, 2008 2:33 PM > >On Sat, May 3, 2008 at 8:13 AM, fantasai <[EMAIL PROTECTED]> wrote: >> Maciej Stachowiak wrote: >>> >>> By contrast, I do not know of any actual need to determine the aspect >>> ratio of an SVG icon or the duration of a sound icon. I do not know of cases >>> where HI guidelines for particular platforms would recommend different >>> choices of icon aspect ratio or sound icon duration. Thus, I suggest we >>> limit ourselves to adding only the info that is actually known to be needed >>> at this time. If UI innovation creates a need for more info, we can add it >>> to the spec then. >> >> That's fine, but we shouldn't pick a solution here that requires adding >> attributes every time we have a similar problem. > >Why? To me it seems much preferable to separate the attributes of an >object into separate name/value pairs then trying to mash them all >together into one value.
Perhaps, but it means adding attributes to <link> elements that will only be needed for a single link type. If the use case for these attributes is strong enough to add special purpose attributes for use with only <link rel=icon> then I dare say that it is strong enough to have a special purpose <icon> element so as to keep user agents from having to deal with nonsense such as <link rel=stylesheet height=32 width=32>
