Issue 7766: Lack of clarity of  'globally unique' for ids                                                                                                                                                           (ras-ftf)
Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com)
Nature: Uncategorized Issue
Severity: 
Summary: Para 2 of 2.4.6 in RFC states that "the id attribute is expected to
contain a globally unique identifier": the meaning and scope of
'globally' should be clarified.
In particular, since later in the section when discussing the 'version'
attribute it is implied that 2 versions of the 'same' asset may have the
same id.
References to use of XMI for generating id are certainly not correct
since xmi:ids are unique only within the scope if a single XMI file, and
may differ for the same element in different files.

Resolution: 
Revised Text: Resolution:
Section 7.4.6 paragraph 2 should be updated with the following text:

The purpose of this attribute is to provide a globally unique identifier for an XML element. The values of this attribute should be globally unique strings optionally prefixed by the type of identifier. If you have access to the UUID assigned in MOF, you may put the MOF UUID in the xmi.uuid XML attribute when encoding the MOF data in XMI. The values of this attribute may be used in the href attribute in simple XLinks. XMI does not specify which UUID convention is chosen.
 
The form of the UUID (Universally Unique Identifier) is taken from a standard defined by the Open Group (formerly the Open Software Foundation).
When a UUID is placed in an XMI file, the form is "id namespace:uuid". The id namespace of UUIDs is not mandatory and can be omitted. An example is "2fac1234-31f8-11b4-a222-08002b34c003."
Section 7.4.13 Asset Identity should be changed with the following text:
The current text: "This specification however does not dictate how an asset id is constructed, and therefore there is no absolute guarantee that any two different assets will not have the same id, and it is therefore advised not to rely on ids being unique."
Should be updated as follows: "This specification declares that an asset id is constructed using the xmi.uuid structure as described in section 7.4.6."

Actions taken:
September 20, 2004: received issue
August 1, 2005: closed issue
Discussion: 

End of Annotations:=====
ck of clarity of  'globally unique' for ids
Para 2 of 2.4.6 in RFC states that "the id attribute is expected to
contain a globally unique identifier": the meaning and scope of
'globally' should be clarified.
In particular, since later in the section when discussing the 'version'
attribute it is implied that 2 versions of the 'same' asset may have the
same id.
References to use of XMI for generating id are certainly not correct
since xmi:ids are unique only within the scope if a single XMI file, and
may differ for the same element in different files.


Subject: Adaptive RAS FTF Issues 
Date: Mon, 28 Feb 2005 11:45:14 -0500 
X-MS-Has-Attach: yes 
X-MS-TNEF-Correlator: 
Thread-Topic: Adaptive RAS FTF Issues 
Thread-Index: AcUUZhEHnc3QCGOjSl2gE5pXdAMRfAJPbB3A 
From: "Nick Dowler" <nick.dowler@adaptive.com> 
To: <ras-ftf@omg.org> 
X-Virus-Scanned: by amavisd-new at sentraliant.com 


All,
 
Please find attached the proposed models to address issues 7759 and 7761.
 
For issue 7766, we suggest that the xmi.uuid is used for clarity of globally unique IDs.
 
Kind regards,
 
Nick.