W3C home > Mailing lists > Public > www-forms@w3.org > August 2002

RE: Naming: select1 vs. singleSelect

From: Klotz, Leigh <Leigh.Klotz@pahv.xerox.com>
Date: Mon, 26 Aug 2002 10:57:16 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE0FF57972@mercury.ADOC.xerox.com>
To: "'Piroumian Konstantin'" <KPiroumian@protek.com>, "'www-forms@w3.org'" <www-forms@w3.org>

Hello.

A strong goal of XForms integration with XHTML 2.0, and the XHTML Working
Group asked that we avoid hyphens and use only lowercase letters for element
and attribute names, which rules out both "selectOne" and "select-one".  

The all lower-case "selectone" is difficult to read in English, as it would
be pronounced "selec-tone", and is indeed used as such in at least one
trademark (http://www.com-spec.com/selectone/).

I don't think that trailing numerals in element names are unusual; see HTML
<h1>, <h2>, etc.

Thank you,
Leigh L. Klotz, Jr.

-----Original Message-----
From: Piroumian Konstantin [mailto:KPiroumian@protek.com] 
Sent: Monday, August 26, 2002 12:21 AM
To: 'www-forms@w3.org'
Subject: Naming: select1 vs. singleSelect



Hi!

What is the reason of using a name like 'select1' for single choice
selection element?
Don't you think that this kind of name is absolutely unusual in XML, XSL,
XHTML or HTML worlds? What's wrong with 'selectOne' or
'singleSelect'/'multiSelect' names? Or maybe 'select-one' (using XSLT naming
convensions)?

Regards,
  Konstantin Piroumian 
  Ivelin Ivanov
--
  Apache Cocoon: http://xml.apache.org/cocoon
  kpiroumian@apache.org
  ivelin@apache.org
Received on Monday, 26 August 2002 13:57:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:51 GMT