W3C home > Mailing lists > Public > www-archive@w3.org > December 2003

Re: Proposed XHTML Module: XForms Basic

From: B. Johannessen <bob@db.org>
Date: Sat, 06 Dec 2003 09:29:50 -0500
To: Ian Hickson <ian@hixie.ch>
Cc: www-archive@w3.org
Message-Id: <1070720989.17792.21.camel@babe.h.db.org>

On Sat, 2003-12-06 at 08:50, Ian Hickson wrote:
> > Second; please don't force client and server programmers to parse
> > the horrible syntax of an RFC 2822 "mailbox". If it's unclear why
> > this is a bad idea, I can come up with a few examples of valid
> > RFC 2822 "mailbox"-es to show how bad it can get. Or you can just
> > believe me when i say it's a disaster :-)
> 
> Would you rather require that every form author write a parser instead?

Nope, the idea of having a type="email" attribute for input elements 
is a good one. What I don't like is that the value of this element is
defined to be a RFC 2822 "mailbox"

The following is a valid RFC 2822 "mailbox":
-----[Start RFC 2822 mailbox]-----
Bob
	(You wouldn't think\)
 Smith "at home)"Johannessen"
	<bob
 @
	(amazing)db.
 (isn't it)org>
-----[End RFC 2822 mailbox]-----

If you're looking for a field to only accept the address, without the
display name (bob@db.org, not "Bob Johannessen" <bob@db.org>), I'd
suggest you specify RFC 2822 "addr-spec" *without* FWS and CFWS. If 
you want to include the display name in the field, use RFC 2822 mailbox
*without* FWS and CFWS.

I'd prefer the former (limited/modified RFC 2822 addr-spec), as I see 
no reason why the display name can't be expressed in another input
element.


	Bob

-- 
--=[ B. Johannessen | bob@db.org | http://db.org/ | +4797152009 ]=--
---=[ uptime: 26 days, 16:01 | load: 0.12 | inbox: 22 messages ]=---
------------=[xmms: Frank Sinatra - New York, New York]=------------
Received on Saturday, 6 December 2003 09:29:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 November 2012 14:17:37 GMT