Changes between Version 12 and Version 13 of UUID


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

--

Legend:

Unmodified
Added
Removed
Modified
  • UUID

    v12 v13  
    44== General ==
    55
    6 All records in Sahana Eden which are to be shared with other applications must have a universally unique identifier (UUID).
     6All records in Sahana Eden which are to be shared with other applications must have a '''universally unique identifier''' (UUID).
    77
    88In Sahana Eden, record UUIDs must be ASCII strings.
    99
    10 Eden automatically generates a UUID for each record according to the specifications in RFC4122:
     10Eden automatically generates a '''UUID''' for each record according to the specifications in RFC4122:
    1111
    1212    http://www.faqs.org/rfcs/rfc4122.html
    1313
    14 All record UUIDs generated by Sahana Eden are strings in URN notation:
     14All record UUIDs generated by Sahana Eden are strings in '''URN''' notation:
    1515{{{
    1616urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
    1717}}}
    1818
    19 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.
     19If 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.
     20
     21Some data formats (e.g. PFIF) may require a '''domain prefix''' for a UUID, followed by a slash:
     22{{{
     23sahanafoundation.org/urn:uuid:a46c1b3b-35c0-44c6-9142-bbe3a013039a
     24}}}
     25
     26Where such a domain prefix is used and it matches the local domain of the importing Sahana instance, it will be removed during import.
    2027== Implementation Guideline ==
    2128