[Devel] UID

[David MENTRE <david.mentre AT gmail.com>]

Thomas,

Le 19/09/05, Thomas Petazzoni<thomas.petazzoni AT enix.org> a écrit :
> J'avais
> aussi lu dans la RFC une histoire d'UID, mais je n'ai pas compris quel
> format devait avoir ce champ. 

Apparement, l'UID est unique par VEVENT, VTODO, etc. De ma lecture de
la RFC, tu dois en mettre un différent pour chaque événement du
calendrier. Et c'est obligatoire (MUST).

C'est un identifiant unique. Ils conseillent un truc du style :
   20050706T190000-12 AT agendadulibre.org
   date-incrément@nom-de-domaine

4.8.4.7 Unique Identifier

   Property Name: UID

   Purpose: This property defines the persistent, globally unique
   identifier for the calendar component.

   Value Type: TEXT

   Property Parameters: Non-standard property parameters can be
   specified on this property.

   Conformance: The property MUST be specified in the "VEVENT", "VTODO",
   "VJOURNAL" or "VFREEBUSY" calendar components.

   Description: The UID itself MUST be a globally unique identifier. The
   generator of the identifier MUST guarantee that the identifier is
   unique. There are several algorithms that can be used to accomplish
   this. The identifier is RECOMMENDED to be the identical syntax to the
   [RFC 822] addr-spec. A good method to assure uniqueness is to put the
   domain name or a domain literal IP address of the host on which the
   identifier was created on the right hand side of the "@", and on the
   left hand side, put a combination of the current calendar date and
   time of day (i.e., formatted in as a DATE-TIME value) along with some
   other currently unique (perhaps sequential) identifier available on
   the system (for example, a process id number). Using a date/time
   value on the left hand side and a domain name or domain literal on
   the right hand side makes it possible to guarantee uniqueness since
   no two hosts should be using the same domain name or IP address at
   the same time. Though other algorithms will work, it is RECOMMENDED
   that the right hand side contain some domain identifier (either of
   the host itself or otherwise) such that the generator of the message
   identifier can guarantee the uniqueness of the left hand side within
   the scope of that domain.

Leur exemple :

    UID:19960401T080045Z-4000F192713-0052 AT host1.com


Amicalement,
d.