Issue 12182: reference representation of property                                                                                                                                                                    (bpdm-ftf)
Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov)
Nature: Revision
Severity: Significant
Summary: The reference representation of property should not provide the choice between attribute and element. This prevent from using a standard referencing scheme such as XLINK as XLINK cannot be managed as a single attribute. The lack of formal unification of reference representation of properties prevents interoperability between XMI specifications that uses multiple xml documents.

Resolution: Resolution:
1. Apply org.omg.xmi.elemt=true to the top package.
2. Use the LinkAttribs complex type as the XML type of elements representing references 

Revised Text: 
Actions taken:
January 16, 2008: received issue
July 18, 2008: closed issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 16 Jan 2008 13:20:37 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report



--------------------------------------------------------------------------------

Name: Conrad Bock
Company: NIST
mailFrom: conrad.bock@nist.gov
Notification: No
Specification: Business Process Definition MetaModel
Section: 
FormalNumber: dtc/07-12-05
Version: 
RevisionDate: 
Page: 
Nature: Revision
Severity: Significant
HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
Description
The reference representation of property should not provide the choice between attribute and element. This prevent from using a standard referencing scheme such as XLINK as XLINK cannot be managed as a single attribute. The lack of formal unification of reference representation of properties prevents interoperability between XMI specifications that uses multiple xml documents.