| | 40 | == Proposal (nursix): URNs instead of UUIDs == |
| | 41 | |
| | 42 | In the near future, Eden should move from UUIDs to [http://tools.ietf.org/html/rfc2141 URN]s in order to enhance interoperability in multi-application scenarios like Haiti or Pakistan. |
| | 43 | |
| | 44 | 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). |
| | 45 | |
| | 46 | In practise, that means: |
| | 47 | |
| | 48 | - there should be a common namespace for sahana applications, at best "sahana" |
| | 49 | - uuid="eden.sahanafoundation.org/XXXX-YYYY" would become something like uuid="urn:sahana:eden.sahanafoundation.org/XXXX-YYYY" |
| | 50 | - Eden can support other namespaces, by making the namespace a configurable attribute of the "uuidstamp" reusable field |
| | 51 | |
| | 52 | |
