Re: Identifying Multi-valued items

Quoteing [email protected], on Sun, Feb 02, 2003 at 12:08:37PM +0100:
> >I'm not a vCard expert, but since this list seems to be dead except for
> >us...
> A few others are reading it sometimes as well, like me :-)
> 
> >Despite that quote, I guess you noticed RFC 2425 doesn't seem to really
> >say much about multiplicity of values.
> RFC 2425 is only a base specification, I guess you have to refer to
> actual profile specifications, like vCard 3.0 (RFC2426), that are based on
> MIME-DIR.

That was my guess, too!

RFC2425 says the profiles will describe the multiplicity. the only
profile I've seen, 2426, doesn't.

> >Some seem to obviously allow multiples (TEL), and SOURCE even says that
> >you can have it multiple times. But NOTE, for example, doesn't say that
> >it can be specified multiple times, but surely can. As, I would think,
> >would PHOTO (a gif and a png in a vcard would seem reasonable).
> >
> >Some things, like VERSION, would seem to only be allowed to be specified
> >once, though I don't see that stated.
> The problem with vCard in general is that is does not help much to
> consult the RFCs alone, but if you want to implement something
> interoperable, the actually existing implementations are equally
> important.

Uh-oh...

> For example, all implementations I've seen accept multiple TEL values,
> but none handles multiple NOTE values.

Really? Hmm.

> As a rule of thumb, I'd say that those values that can be further qualified
> with a TYPE parameter are likely to occur multiple times (such as
> TEL;TYPE=WORK:253265 and TEL;TYPE=CELL:216561256)

> >On the decoding side, if you see multiple values, I guess its
> >multi-valued....
> Obviously :-)
> 
> Regards,

Cheers,
Sam