Changes between Version 12 and Version 13 of UUID

Timestamp:

08/31/12 18:24:35 (12 years ago)

Author:

Dominic König

Comment:

--

UUID

@@ -4 +4 @@
 == General ==
 
-All records in Sahana Eden which are to be shared with other applications must have a universally unique identifier (UUID).
+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:
+Eden automatically generates a '''UUID''' for each record according to the specifications in RFC4122:
 
     http://www.faqs.org/rfcs/rfc4122.html
 
-All record UUIDs generated by Sahana Eden are strings in URN notation:
+All record UUIDs generated by Sahana Eden are strings in '''URN''' notation:
 {{{
 urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
 }}}
 
-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.
+If a record is imported into Sahana Eden and it already has a UUID, then Eden will retain this UUID as-is (exception: local domain prefix, see below) - without any syntax validation (i.e. no specific UUID schema is required). However, for consistency reasons, we recommend to use URNs.
+
+Some data formats (e.g. PFIF) may require a '''domain prefix''' for a UUID, followed by a slash:
+{{{
+sahanafoundation.org/urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
+}}}
+
+Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
 == Implementation Guideline ==