[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-bpmn2.dev] ItemDefinition's Import is transient ?
|
OK I'll change the model to use a qname for now. Thanks for confirming.
On Wed, Sep 15, 2010 at 09:03, Henning Heitkötter
<hheitkoetter@xxxxxxxxxxxxxx> wrote:
Yes, judging from the "BPMN 2.0 by Example" document, chapter 11, that's how it's supposed to work: structureRef as a QName with a NS prefix pointing indirectly to the import element.
2010/9/15 Antoine Toulme
<antoine@xxxxxxxxxxxxxxx>
The spec has a serious problem on this: the import attribute is not in the schema, but it shows in the table of the attributes of Item Definition.
Our code uses StructureRef on Item Definition as an object, while the spec mentions it should be a qname, and casts it as an EObject.
I think we should leave import as it is, set structureRef as a qname, and later on the getImport method should be rewired to get the right Import object that matches the qname's prefix of the StructureRef attribute.
WDYT ?
On Wed, Sep 15, 2010 at 08:50, Henning Heitkötter
<hheitkoetter@xxxxxxxxxxxxxx> wrote:
Hi Antoine,
I guess it's transient because this attribute is not supported by the XSD.
Apparently the specification does not mention a replacement - at least I couldn't find anything. Note that a normal reference by ID is not possible in XSD, because Import elements do not have an ID.
Regards,
Henning