Re: [VCARDDAV] [Technical Errata Reported] RFC6350 (3100)

[Simon Perreault <[e-mail]>]

On 2012-02-08 08:43, Javier Godoy wrote:
> On February 6, 2012 2:21 PM -0500 Cyrus Daboo wrote.
>
>> --On February 6, 2012 1:55:01 PM -0500 Simon Perreault
>> <[e-mail]> wrote:
>>
>>> There is no
>>> way we can change the ABNF so that the example becomes correct. The
>>> example is just wrong. We must fix it with one of these:
>>>
>>> TYPE=foo,bar
>>> TYPE=foo,TYPE=bar
>
> TYPE=foo;TYPE=bar

Right. *sigh*

>>> TYPE="foo","bar"
>
> I'm not sure about this one.
>
> On <http://www.ietf.org/mail-archive/web/vcarddav/current/msg02476.html>
> Simon
> said that "all parameters can be implicitly quoted", but the published
> text of
> RFC 6350 suggests that some parameters cannot be quoted, because the
> ABNF only
> allows gratuitous quotes in TZ, ALTID, LABEL, SORT-AS and any-param

Ok then I would consider that to be a bug in the ABNF. A parser should 
not need to know about specific parameters when parsing quotes.

>> And perhaps we should have an example of 'TYPE="foo,bar"' and explain
>> that
>> that represents a single parameter value of "foo,bar" just to
>> re-iterate the
>> point.
>
> Perhaps this clarification fits best for the SORT-AS param.
>
> For instance, the value of the SORT-AS parameter in
> N;SORT-AS="Mann,James":de Mann;Henry,James;;
> is a single param-value "Mann,James" that applies to the surname, and no
> sort-string is specified for the given name.
>
> On the other hand, the value of the SORT-AS parameter in
> N;SORT-AS="Mann","James":de Mann;Henry,James;;
> is a list of two param-values: the first one "Mann" applies to the surname,
> and the second one "James" applies to the given name.

Yes, this is a very good example.

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca