RE: Name relationships in vCard 3.0

[Goh Siew Yong <SYGoh@xxxxxxxxx>]

Yes I guess you can. But you never know how the parser or receiving appl.
will interpret them. Though syntactically it will not cause any problem.
Just like you can enter anything say Jane in the field for first name,Tan
for family name for a form in the ab application. And then a completely
different thing say Peter Brown for full name field. 

As far as I know, N & FN should mean the same thing. 

As specified in RF2426:
N type requires the text to be in the  format following the semantics of
X.520 Common Name attribute.
While FN type need to be a structured text value. Each component can have
multiple values. The components in the structure has to be of the following
sequence : Family Name, Given Name, Additional Names, Honorific Prefix, and
Honorific suffixes. These components are separated by semi-colon. Individual
text can also includes multiple text separated by commas. This type is based
on the semantics of X.520 individual name attributes.

The example given in the RFC was 
FN:Mr. John Q. Public\, Esq.
N:Public;John;Qinlan;Mr.;Esq



-----Original Message-----
From: owner-imc-vcard@xxxxxxxxxxxx [mailto:owner-imc-vcard@xxxxxxxxxxxx] On
Behalf Of Misha Wolf
Sent: Thursday, September 09, 2004 6:19 PM
To: Germán M. Rivera; Jeff Parrish; imc-vcard@xxxxxxx
Subject: RE: Name relationships in vCard 3.0


No, it is not "assumed that the name of the object (a person) is unique".
This would clearly be a wrong assumption.  Has Michael Jackson made any hit
singles recently?  He has not.  I'm referring to the originator of Jackson
Structured Programming.  Whom did you think I meant?

FN and N should describe the same person, but I don't believe there is
anything in vCard that forces a textual equivalence between them.
If I wanted to, I could put "Dubya" in my FN type and something completely
different in the individual fields of my N type (eg "Bush" 
and "George" and "W").

Misha Wolf
Standards Manager
Product and Platform Architecture Group
Reuters


-----Original Message-----
From: owner-imc-vcard@xxxxxxxxxxxx [mailto:owner-imc-vcard@xxxxxxxxxxxx] On
Behalf Of Germán M. Rivera
Sent: 09 September 2004 09:01
To: 'Jeff Parrish'; imc-vcard@xxxxxxx
Subject: RE: Name relationships in vCard 3.0



Hi Jeff,

As you can see in the RFC, this is the FN type purpose:

"To specify the formatted text corresponding to the name of the object the
vCard represents"

and this is the N type purpose:

"To specify the components of the name of the object the vCard represents"

Of course, it is assumed that the name of the object (a person) is unique,
so these two types should describe the same content.

Hope this helps,
Germán
 

> -----Mensaje original-----
> De: owner-imc-vcard@xxxxxxxxxxxx [mailto:owner-imc-vcard@xxxxxxxxxxxx]
En
> nombre de Jeff Parrish
> Enviado el: jueves, 09 de septiembre de 2004 2:36
> Para: imc-vcard@xxxxxxx
> Asunto: Name relationships in vCard 3.0
> 
> 
> What is the relationship between the N: and FN: types. In particular, 
> there is nothing I can find in the RFC that explicitly requires the 
> contents of these types to match, and both fields are mandatory. Is 
> there a reason to allow them to mismatch? If not, the contents of FN:
> need to be generated from the contents of N:, or else the contents of 
> the two types may not match (see below)
> 
> 	FN:Mr. John Q. Public\, Esq.
> 	N:Putenesca;Fanny;Mae;Mrs
> 
> 
> 
> Jeff Parrish





--------------------------------------------------------------- -
        Visit our Internet site at http://www.reuters.com

Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging

Any views expressed in this message are those of  the  individual sender,
except  where  the sender specifically states them to be the views of
Reuters Ltd.