Re: CAP-12-e: CAP-VERSION Property

Doug replied on 11/04/2003 02:16:01 PM:
> > My appologies for not be more precise in the question.  I was 
> > referring to using a numeric values like VERSION (which actually is 
> > biparted):
> 
> Do you have a proposal? It does not look like it to me.

I clearly indicated that it was a question, not something that required a 
proposal to resolve. 

By your constant avoidance to the question Ill have to assume that you 
made the change arbitrarily without WG discussion or concensus by virtue 
of being the sole current editor.  If Im wrong then fine but I can find no 
WG discussion on the changes that Im asking about or the questionable ABNF 
I find.  As recent as April 2003 it was described one way and all of a 
sudden in June 2003 it was different.

Since you have said (in part but not out of context):

It is a multivalued field...

I think its fair to question the non-multivalued ABNF that is currently 
there.  In case you were not aware, the current ABNF does NOT indicate 
that CAP-VERSION is multivalued.  It is just:

   cap-version   = "CAP-VERSION" other-params ":" text CRLF

which means CAP-VERSION is single valued; a single 'text' value.  If you 
want to see an example of a multivalued ABNF then check out my provided 
ABNF or the one in Section 8.22 MULTIPART Property

   name = "MULTIPART" other-params ":" text *( "," text) CRLF

Bruce
===========================================================================
Bruce Kahn                                INet: 
[email protected]
Messaging & Collaboration                 Phone: 978.399.6496
IBM Software Group                         FAX: and nothing but the FAX...
Standard disclaimers apply, even where prohibited by law...