W3C home > Mailing lists > Public > public-respimg@w3.org > December 2016

Re: aspect ratio as an attribute

From: <steve@steveclaflin.com>
Date: Fri, 16 Dec 2016 15:01:09 -0600
To: Adam van den Hoven <adam@littlefyr.com>
Cc: Simon Pieters <simonp@opera.com>, Alex Bell <alex@bellandwhistle.net>, public-respimg@w3.org, Paul Deschamps <pdescham49@gmail.com>, Yoav Weiss <yoav@yoav.ws>, Jason Grigsby <jason@cloudfour.com>, Tommy Hodgins <tomhodgins@gmail.com>, Jonathan Kingston <jonathan@jooped.co.uk>, "Hall, Charles (DET-MRM)" <Charles.Hall@mrm-mccann.com>, Greg Whitworth <gwhit@microsoft.com>
Message-ID: <c56b5eb6a4a9c6e32a9d1519557b0bf6@steveclaflin.com>
Sorry I opened this can of worms.  I wasn't aware of the desire to 
reserve hyphenation for namespacing, although that makes a lot of sense. 
  I would venture meta- as a possibility, except that many tag attributes 
could be viewed as being meta-data.

My main thought was to avoid having the same term used in multiple 
places for different purposes.  I'd be happy with a non-hyphenated (or 
should that be nonhypenated?) attribute. I just can't think of too many 
at the moment that aren't rather long, like nativeaspect or 
naturalaspect, or something totally different, like proportions, or 
cryptic like wtoh.

On 2016-12-16 13:24, Adam van den Hoven wrote:
> And so we fall into the never resolved discussion of what constitutes
> a new namespace. Get out the knives! ;)
> actually I'm ok with this. Did I mention that I don't like hyphens in
> attributes? Mixed case too. I only meant that if we want to
> distinguish something as being a browser hint that might be a reason
> to introduce one. But if there is only one then I'll reserve the
> argument in favour for the third time we have this sort of discussion.
> On Dec 16, 2016 11:17 AM, "Simon Pieters" <simonp@opera.com> wrote:
>> On Fri, 16 Dec 2016 19:27:05 +0100, Adam van den Hoven
>> <adam@littlefyr.com> wrote:
>>> Yoav's right. I think I had slipped a gear and was thinking art
>>> direction
>>> variations, which is handled by the <source> element.
>>> Developer confusion is something that we should avoid and I'm OK
>>> with
>>> making things clear although I'm not a huge fan of hyphenated
>>> attribute
>>> names without reason. Perhaps, however, following in the
>>> footsteps of
>>> data-, we might have hint-aspect on the assumption that at some
>>> future date
>>> we might add other hinting attributes for external resources. I
>>> can't see
>>> what that might be but my lack of foresight doesn't mean it won't
>>> happen.
>>> data- is basically a less verbose namespace, and I think we might
>>> want to
>>> resuse that notion.
>> No, attribute names should be without hyphens *unless* it is really
>> a namespace, like data-* or aria-*.
>> Saying "well we might add something similar in the future" is not a
>> good ground for claiming a single new attribute should have its own
>> new namespace. :-)
>> --
>> Simon Pieters
>> Opera Software
Received on Friday, 16 December 2016 21:01:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:20 UTC