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

[Chad La Joie <lajoie@itumi.biz>]

The logo element provides information about a logo that is intended to
be displayed.  All displayed graphics have an height and width,
regardless of the various ways in which they are encoded.  That one
particular encoding mechanism happens to have better scaling
properties is orthogonal to the purpose of this element.

On Mon, Oct 24, 2011 at 09:49, Tom Scavo <trscavo@gmail.com> wrote:
> 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.
>
> Tom
>
> --
> This publicly archived list offers a means to provide input to the
> OASIS Security Services (SAML) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: security-services-comment-subscribe@lists.oasis-open.org
> Unsubscribe: security-services-comment-unsubscribe@lists.oasis-open.org
> List help: security-services-comment-help@lists.oasis-open.org
> List archive: http://lists.oasis-open.org/archives/security-services-comment/
> Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
> Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=security
> Join OASIS: http://www.oasis-open.org/join/
>
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered