Re: RFC-2445: ABNF/prose mismatch on parameters

[Doug Royer <Doug.Royer@xxxxxxx>]

> Date: Thu, 22 Jul 1999 11:43:30 -0700 (PDT)
> From: rweiler@amplitude.com (Robert Weiler)
> 
> I just skimmed RFC2234 (ABNF), and don't think there is any implied ordering 
> in the iCal rules. The relevant section is 3.2 which describes alternatives. 
> The slash character '/', does not imply any order.

RFC2445:

     eventc     = "BEGIN" ":" "VEVENT" CRLF
          	        eventprop *alarmc
          	  "END" ":" "VEVENT" CRLF


	Must all alarmc's be after {event,todo} prop's?

	Can there be any {event,todo} prop's after a VALARM?
	
---

     attach     = "ATTACH" attparam ":" uri  CRLF

     attach     =/ "ATTACH" attparam ";" "ENCODING" "=" "BASE64"
                   ";" "VALUE" "=" "BINARY" ":" binary

     attparam   = *(

                ; the following is optional,
                ; but MUST NOT occur more than once

                (";" fmttypeparam) /


If ENCODING exists, why MUST it be after 'attparam'?
Why MUST VALUE=BINARY come last?


There are more ...


-Doug
-------------------------------------------------------------------
Doug.Royer@Sun.COM		http://playground.sun.com/~dougr
Pager:				Doug.Royer@Pager.Eng.Sun.com
801 W. El Camino #131		Work:   (650)786-7599
Mountain View, CA 94040		Ham Radio: N6AAW, Aviation: PP-ASEL