Re: [auth48] [AD] AUTH48: RFC-to-be 9554 <draft-ietf-calext-vcard-jscontact-extensions-10> for your review

[Orie Steele <[e-mail]>]

Thanks Bron :)

To be clear are you saying the original example is correct and should
remain as is?

OS


On Mon, Apr 8, 2024, 7:53 PM Bron Gondwana <[e-mail]> wrote:

> On Tue, Apr 9, 2024, at 05:06, Orie Steele wrote:
>
> > Removing the ALTID parameter from GRAMGENDER:
> > We removed the ALTID parameter because it isn't necessary. There can
> only be one grammatical gender per contact and language anyway.
> >
> > Updated examples:
> > We updated the examples to clarify both the changes that I just outlined.
>
>
> This example is now confusing:
>
>   Example(s):
>       GRAMGENDER;LANGUAGE=de:masculine
>       GRAMGENDER:LANGUAGE=en:neuter
>
> especially given your comment regarding ALTID, I suggest a single example
> (and double check ":" vs ";")
>
> I suggest:
>
> Example:
>       GRAMGENDER:LANGUAGE=de:inanimate
>
>
> No, using colon for both is incorrect syntax.  The VCARD format is
> something like this:
>
> key [ ";" param=paramvalue ";" param2=pval2 ... ] ":" value
>
>
> There are further "value" fields which also are separated by ";" or by ","
> or structured in other awful ways, even with ":".  It's really REALLY
> bad, which is why jscontact, based on a structured data format, is so much
> better.
>
> For example, my rather incomplete (and incorrect about the email's role)
> contact book entry for Karen is:
>
> BEGIN:VCARD
> VERSION:3.0
> FN:Karen Moore
> N:Moore;Karen;;;
> NICKNAME:
> ORG:;
> TITLE:
> EMAIL;TYPE=home;TYPE=pref:[e-mail]:
> PRODID:-//CyrusIMAP.org//Cyrus 3.1.6-736-gdfb8e44-fmstable-20190718v2//EN
> REV:20190720T090159Z
> UID:[...]
> END:VCARD
>
>
> You can see the value components separated by semicolon in the "N"
> structured name field, and the TYPE parameters on the "EMAIL" field.
>
> LANGUAGE is a parameter on the GRAMGENDER field above.
>
> Cheers,
>
> Bron.
>
> --
>   Bron Gondwana, CEO, Fastmail Pty Ltd
>   [e-mail]
>
>
>