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

[Frank_Dawson@xxxxxxxxx]

Agree with Bruce's comment that we need to address the fact that the ABNF
is more restrictive (BUT CORRECT!) than the prose.
In SGML there was a "&" occurrence indicator that said that (e.g.,
"(a&b&c)") the content particles in a set can be in any order. If this was
in RFC2234 ABNF, it would make our assignment alot easier. As it is, Bruce
is correct, the obligatory ABNF for "any order" of properties will be nasty
for the more complex calendar component specifications.

Bruce's example of using the "eventc" ABNF is a representative one. I will
give this ABNF some more thought.

-- Frank