Changes between Version 11 and Version 12 of UUID


Ignore:
Timestamp:
08/31/12 18:18:05 (8 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UUID

    v11 v12  
    44== General ==
    55
    6 UUIDs (Universal Unique IDentifiers) in Eden follow the Python uuid implementation,
    7 which is specified in RFC4122:
     6All records in Sahana Eden which are to be shared with other applications must have a universally unique identifier (UUID).
     7
     8In Sahana Eden, record UUIDs must be ASCII strings.
     9
     10Eden automatically generates a UUID for each record according to the specifications in RFC4122:
    811
    912    http://www.faqs.org/rfcs/rfc4122.html
    1013
    11 However, other systems do not necessarily follow this convention (especially data sets
    12 outside of IT systems), but we still must be able to identify such data resources.
    13 
    14 Therefore, in every shared resource (XML+JSON), the UUID shall be prefixed by the domain
    15 name of the originating instance (authoritative domain) plus a slash ("/"), e.g.
    16 
     14All record UUIDs generated by Sahana Eden are strings in URN notation:
    1715{{{
    18     haiti.sahanafoundation.org/12345678-1234-5678-1234-567812345678
     16urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
    1917}}}
    2018
    21 Generally, a "domain name" here can be any arbitrary XML name except it must not contain
    22 any slashes. However, the domain name must be unique, of course - and therefore it is
    23 recommended to use the internet domain name of the current instance. This in turn requires
    24 that all applications which share that domain name and take part in the data exchange adhere
    25 to the same UUID convention (UUID's have to be unique at least within the same domain).
    26 
    27 This convention is adopted from the person_record_id convention of [http://zesty.ca/pfif/1.1/#person-records PFIF].
    28 
     19If a record is imported into Sahana Eden and it already has a UUID, then Eden will retain this UUID without syntax validation (no specific UUID schema is required). However, for consistency reasons, we recommend to use URNs.
    2920== Implementation Guideline ==
    3021