1f762d2b-03c4-4a83-9a03-75ff658a6eee
Seen in rfc6350

Seen in rfc6350

Seen in RFC 6350
Counts : rfc6350:3
Seen 3 times in more than 1 page, showing only the first.
RFC 6350                          vCard                      August 2011


     BEGIN:VCARD
     VERSION:4.0
     UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
     FN;PID=1.1:J. Doe
     N:Doe;J.;;;
     EMAIL;PID=1.1:jdoe@example.com
     EMAIL;PID=2.1:boss@example.com
     TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
     TEL;PID=2.1;VALUE=uri:tel:+1-666-666-6666
     CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
     END:VCARD

     BEGIN:VCARD
     VERSION:4.0
     UID:urn:uuid:4fbe8971-0bc3-424c-9c26-36c3e1eff6b1
     FN;PID=1.1:J. Doe
     N:Doe;J.;;;
     EMAIL;PID=1.1:jdoe@example.com
     EMAIL;PID=2.2:ceo@example.com
     TEL;PID=1.1;VALUE=uri:tel:+1-555-555-5555
     TEL;PID=2.2;VALUE=uri:tel:+1-666-666-6666
     CLIENTPIDMAP:1;urn:uuid:53e374d9-337e-4727-8803-a1e9c14e0556
     CLIENTPIDMAP:2;urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee
     END:VCARD

   On the first device, the same PID source identifier (1) is reused for
   the new EMAIL and TEL properties.  On the second device, a new source
   identifier (2) is generated, and a corresponding CLIENTPIDMAP
   property is created.  It contains the second device's identifier,
   "urn:uuid:1f762d2b-03c4-4a83-9a03-75ff658a6eee".

   The new EMAIL properties are unmatched on both sides since the PID
   global value is new in both cases.  The sync thus results in a copy
   on both sides.

   Although the situation appears to be the same for the TEL properties,
   in this case, the synchronization engine is particularly smart and
   matches the two new TEL properties even though their PID global
   values are different.  Note that in this case, the rules of
   Section 7.1.2 state that two properties MAY be matched at the
   discretion of the synchronization engine.  Therefore, the two
   properties are merged.

   All this results in the following vCard, which is stored on both
   devices:






Perreault                    Standards Track                   [Page 55]
-1 RFC regex push