W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: Note on terminology: Attribute types

From: Dão Gottwald <dao@design-noir.de>
Date: Sun, 01 Jul 2007 22:08:43 +0200
Message-ID: <468809CB.7040705@design-noir.de>
To: "Michael A. Puls II" <shadow2531@gmail.com>, "public-html@w3.org" <public-html@w3.org>

I think "DOM attributes" could be confused with attribute nodes. The
term may be accurate, but that's not necessarily relevant for random web
authors reading the spec. Rhetorical question: getAttribute surely is a
DOM method, so why shouldn't it return a "DOM attribute"?
To my experience, "property" is the most commonly used term; I don't see
a good reason against adopting it.

Dao

Michael A. Puls II schrieb:
> 
> On 6/12/07, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>>
>> Henrik Dvergsdal wrote:
>> > I think we will gain precision by using consistent, spec-wide
>> > terminology to distinguish between DOM attributes
>>
>> I've usually seen these called "properties", precisely to distinguish 
>> them
>> from
>> element attributes...  Of course they're "attributes" in the IDL... :(
> 
> Not too big of a deal to me, but to me:
> 
> <div test="me">
> test is an attribute.
> 
> div.test = "me";
> 
> test is a property
> 
> div {
>    test: "me";
> }
> 
> test is a css property.
> 
> When DOM is mentioned, the first language I associate with it is
> ECMAScript/Javascript.
> 
> Because of that, despite the IDL use of  "attribute" and other
> languages, I personally would rather refer to DOM attributes as
> properties and refer to Element attributes as attributes.
> 
> However, I don't think that'll fly with everyone, so using DOM
> attribute and Element attribute  could clear things up.  (I understand
> what a content attribute is referring to, but Element attribute sounds
> much better.)
Received on Monday, 2 July 2007 15:51:25 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:46 UTC