W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2003

Re: regex for media types

From: Amy Lewis <alewis@tibco.com>
Date: Mon, 4 Aug 2003 11:11:57 -0400
To: Mark Nottingham <mark.nottingham@bea.com>
Cc: xml-dist-app@w3.org
Message-Id: <20030804111157.4de64a28.alewis@tibco.com>

On Tue, 29 Jul 2003 15:25:48 -0700
Mark Nottingham <mark.nottingham@bea.com> wrote:

> 
> I took an action item to double-check what a regex for a media type 
> should look like.

[snip]

> Given that the type rule is extensible by IANA, it seems most sensible
> 
> to NOT enumerate the current types. This leaves us with:
> 
>     [a-zA-Z0-9!#$%^&\*_-\+{}\|'.`~]+/[a-zA-Z0-9!#$%^&\*_-\+{}\|'.`~]+

Unless the working group/task force has reason to believe that the IANA
is going to change its long-standing policy of conservatism in the
approval of new types, this statement is not quite correct.

One new type has been added since the publication of the four MIME RFCs
("model").  There is good reason to suggest that an enumeration of types
is preferable to an open content model: what are you going to do with a
type you don't recognize?  The reluctance of IANA to approve new types
is another factor, as is the reasoning behind it: new types are avoided
because they require changes to deployed software.

So, I would think that it would be better to enumerate, with an escape
to vendor-defined or random types.  But the enumeration is valuable,
signalling the set of types that processors should (in some fashion)
support.

Amy!
-- 
Amelia A. Lewis
Architect, TIBCO/Extensibility, Inc.
alewis@tibco.com
Received on Monday, 4 August 2003 11:11:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:14 GMT