RE: Name relationships in vCard 3.0

=20
FN is an expression of how the person would "commonly" write their name w=
ithout structure; such as when addressing an envelope or printing the nam=
e on a business card.

N imposes a type of "universal" structure with notions such as "Family" o=
r "Given" etc. which may or may not map into an arbitrary cultural contex=
t. N is intended to "pre-structure" the name into fields which might be u=
seful for searching, sorting, etc. and eliminate the need for any heurist=
ic processing on the FN field to extract that information.

Without question the two attributes denote the same person :)




> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of Misha Wolf
> Sent: Thursday, September 09, 2004 6:44 AM
> To: Goh Siew Yong; Germ=E1n M. Rivera; Jeff Parrish; [email protected]
> Subject: RE: Name relationships in vCard 3.0
>=20
>=20
> > As far as I know, N & FN should mean the same thing.=20
>=20
> Indeed.  Now all we have to decide is what we mean by "mean".
>=20
> Misha
>=20
>=20
> -----Original Message-----
> From: [email protected]=20
> [mailto:[email protected]] On Behalf Of Goh Siew Yong
> Sent: 09 September 2004 13:00
> To: Misha Wolf; Germ=E1n M. Rivera; Jeff Parrish; [email protected]
> Subject: RE: Name relationships in vCard 3.0
>=20
>=20
>=20
> Yes I guess you can. But you never know how the parser or=20
> receiving appl.
> will interpret them. Though syntactically it will not cause=20
> any problem.
> Just like you can enter anything say Jane in the field for=20
> first name,Tan for family name for a form in the ab=20
> application. And then a completely different thing say Peter=20
> Brown for full name field.=20
>=20
> As far as I know, N & FN should mean the same thing.=20
>=20
> As specified in RF2426:
> N type requires the text to be in the  format following the=20
> semantics of X.520 Common Name attribute.
> While FN type need to be a structured text value. Each=20
> component can have multiple values. The components in the=20
> structure has to be of the following sequence : Family Name,=20
> Given Name, Additional Names, Honorific Prefix, and Honorific=20
> suffixes. These components are separated by semi-colon.=20
> Individual text can also includes multiple text separated by=20
> commas. This type is based on the semantics of X.520=20
> individual name attributes.
>=20
> The example given in the RFC was
> FN:Mr. John Q. Public\, Esq.
> N:Public;John;Qinlan;Mr.;Esq
>=20
>=20
>=20
>=20
> -------------------------------------------------------------- --
>         Visit our Internet site at http://www.reuters.com
>=20
> Get closer to the financial markets with Reuters Messaging - for more
> information and to register, visit http://www.reuters.com/messaging
>=20
> 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.
>=20
>=20
>=20