Changes between Version 15 and Version 16 of UUID


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

--

Legend:

Unmodified
Added
Removed
Modified
  • UUID

    v15 v16  
    2626Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
    2727
    28 == URNs instead of UUIDs ==
    29 
    30 Eden has just moved from UUIDs to [http://tools.ietf.org/html/rfc2141 URN]s in order to enhance interoperability in multi-application scenarios like Haiti or Pakistan.
    31 
    32 From experience we know that data exchange in the field can involve a variety of applications other than Eden, each implementing their own identifier schemes - and furthermore data sets which instead of application-specific IDs use officially assigned identifiers (e.g. PAHO IDs for health facilities in Haiti). Implementation of URNs will add support for both multiple different identifier schemes, as well as cross-application common namespaces and ID schemas (as favorable e.g. for geolocations or personal data).
    33 
    34 In practise, that means:
    35 
    36   - there should be a common namespace for sahana applications, at best "sahana"
    37   - uuid="eden.sahanafoundation.org/XXXX-YYYY" would become something like uuid="urn:sahana:eden.sahanafoundation.org/XXXX-YYYY"
    38   - Eden can support other namespaces, by making the namespace a configurable attribute of the "uuidstamp" reusable field
    39 
    40 
    4128== Mapping ==
    4229We 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]