Changes between Version 11 and Version 12 of UUID

Timestamp:

08/31/12 18:18:05 (13 years ago)

Author:

Dominic König

Comment:

--

UUID

@@ -4 +4 @@
 == General ==
 
-UUIDs (Universal Unique IDentifiers) in Eden follow the Python uuid implementation,
-which is specified in RFC4122:
+All records in Sahana Eden which are to be shared with other applications must have a universally unique identifier (UUID).
+
+In Sahana Eden, record UUIDs must be ASCII strings.
+
+Eden automatically generates a UUID for each record according to the specifications in RFC4122:
 
     http://www.faqs.org/rfcs/rfc4122.html
 
-However, other systems do not necessarily follow this convention (especially data sets
-outside of IT systems), but we still must be able to identify such data resources.
-
-Therefore, in every shared resource (XML+JSON), the UUID shall be prefixed by the domain
-name of the originating instance (authoritative domain) plus a slash ("/"), e.g.
-
+All record UUIDs generated by Sahana Eden are strings in URN notation:
 {{{
-    haiti.sahanafoundation.org/12345678-1234-5678-1234-567812345678
+urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
 }}}
 
-Generally, a "domain name" here can be any arbitrary XML name except it must not contain
-any slashes. However, the domain name must be unique, of course - and therefore it is
-recommended to use the internet domain name of the current instance. This in turn requires
-that all applications which share that domain name and take part in the data exchange adhere
-to the same UUID convention (UUID's have to be unique at least within the same domain).
-
-This convention is adopted from the person_record_id convention of [http://zesty.ca/pfif/1.1/#person-records PFIF].
-
+If 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.
 == Implementation Guideline ==