OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

security-services-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [security-services-comment] comments re sstc-saml-metadata-ui-v1.0-csprd01

On Mon, Oct 17, 2011 at 8:11 PM, Cantor, Scott <cantor.2@osu.edu> wrote:
> On 10/17/11 6:57 PM, "Tom Scavo" <trscavo@gmail.com> wrote:
>>The following are some preliminary comments regarding
>>sstc-saml-metadata-ui-v1.0-csprd01 (26 July 2011).
>>- Since the height and width XML attributes defined by type
>>mdui:LogoType are required, a link to a non-bitmapped image is
>>effectively precluded. Is this intentional? The fact that
>>non-bitmapped images (such as SVG images) are not supported very well
>>in current browsers is not sufficient reason to preclude such images
>>IMO. Future browsers and non-browser clients might very well leverage
>>non-bitmapped images.
> I don't see why specifying a size precludes SVG. Just because vector
> images in theory scale doesn't mean they really do. There are still
> expected sizes, and we know that even with bitmaps, people are scaling
> them. The point of the properties is to provide differentiation between
> icons of different general size categories.

What I'm saying is: width and height don't make sense for vectorized
graphics since the latter doesn't have an actual size. All images have
an inherent aspect ratio, however. That's the only quantity that makes
sense for a non-bitmapped image.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]