= Header Field Types =

(for brainstorming around issue [http://trac.tools.ietf.org/wg/httpbis/trac/ticket/266 ticket #266])

== Base ABNF rules ==

{{{
   BWS           = <HTTPbis P1 BWS>
   OWS           = <HTTPbis P1 OWS>

   token         = <HTTPbis P1 token>
   quoted-string = <HTTPbis P1 quoted-string>

   word          = token / quoted-string

   param         = token BWS "=" BWS word
}}}

== Categories ==

=== Parametrized String (PS) ===
{{{
   thing         = <TO BE DONE based on our use cases>

   PS            = thing *( OWS ";" OWS param )
}}}

==== Examples for "thing" ====

Accept, Content-Type: subset of token plus "/"
{{{
   text/html
}}}

Accept-Charset:
{{{
   iso-8859-1
}}}

Content-Disposition: token
{{{
   attachment
   inline
}}}

Link: URI characters (superset of token including ";" but not DQUOTE)
{{{
   </uri;bar>
}}}

=== List of Parametrized Strings (LoPS) ===
{{{
   LoPS           = #PS
}}}


== Categorization of existing fields ==

 Accept::
 LoPS (''where accept extensions are allowed to use a single token form'')

 Accept-Charset::
 LoPS (''do charset names need characters outside token?'')

 Accept-Encoding::
 LoPS (''do language tags need characters outside token?'')

 Accept-Language::
 LoPS

 Content-Type::
 PS (but note the special case in [http://greenbytes.de/tech/webdav/rfc2397.html#rfc.section.3 RFC2397, Section 3 ("data" URI)]

 Content-Disposition::
 PS

 Link::
 LoPS