Issue 12181: spec doesn't provide a unified way to specify and represent link references                                                                                                                             (bpdm-ftf)
Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@nist.gov)
Nature: Revision
Severity: Significant
Summary: The specification doesn't provide a unified way to specify and represent link references. It is currently possible to use either IDREF or href. Furthermore, no standard URI representation is made mandatory. The lack of mandatory reference scheme prevents to ensure interoperability when xmi models are organized in multiple xml files. 

Resolution: Resolution:
A new xmi_infra.xsd schema is created to host the XML attributes to provide validation of reference in the context of XML schemas.
The LinkAttribs complex type allows either for id/IDREF references and id/href references.

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xmi="http://schema.omg.org/spec/XMI/2.1"
  targetNamespace="http://schema.omg.org/spec/XMI/2.1"
>

  <xsd:include schemaLocation="../../../XMI/20071213/xmi.xsd"/>

  <xsd:attribute name="idref" type="xsd:IDREF"/>
  <xsd:attribute name="label" type="xsd:string"/>
  <xsd:attribute name="referenceTypeID" type="xsd:QName"/>

  <xsd:complexType name="LinkAttribs">
    <xsd:attribute ref="xmi:label" use="optional"/>
    <xsd:attribute ref="xmi:idref" use="optional"/>
    <xsd:attribute name="href" type="xsd:string" use="optional"/>
    <xsd:attribute ref="xmi:referenceTypeID" use="optional"/>
  </xsd:complexType>

</xsd:schema>

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:19:52 -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 specification doesn't provide a unified way to specify and represent link references. It is currently possible to use either IDREF or href. Furthermore, no standard URI representation is made mandatory. The lack of mandatory reference scheme prevents to ensure interoperability when xmi models are organized in multiple xml files.