Changes between Version 17 and Version 18 of UUID

Timestamp:

08/31/12 18:32:38 (12 years ago)

Author:

Dominic König

Comment:

--

UUID

@@ -19 +19 @@
 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.
 
+== Domain Prefix ==
+
 Some data formats (e.g. PFIF) may require a '''domain prefix''' for a UUID, followed by a slash:
 {{{
@@ -24 +26 @@
 }}}
 
-- where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
-- in exports, the transformation stylesheets for formats which require a domain prefix will prepend the local domain to each un-prefixed UUID.
+Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
+
+In exports, the transformation stylesheets for formats which require a domain prefix will prepend the local domain to each un-prefixed UUID.
 == Mapping ==
 We need an agreed set of UUIDs for GIS Data so that we can share data more easily across systems, such as the [PakistanUnionCouncils current Pakistan data]