Changes between Version 17 and Version 18 of UUID


Ignore:
Timestamp:
08/31/12 18:32:38 (9 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UUID

    v17 v18  
    1919If 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.
    2020
     21== Domain Prefix ==
     22
    2123Some data formats (e.g. PFIF) may require a '''domain prefix''' for a UUID, followed by a slash:
    2224{{{
     
    2426}}}
    2527
    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.
    27 - in exports, the transformation stylesheets for formats which require a domain prefix will prepend the local domain to each un-prefixed UUID.
     28Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
     29
     30In exports, the transformation stylesheets for formats which require a domain prefix will prepend the local domain to each un-prefixed UUID.
    2831== Mapping ==
    2932We 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]