AW: [mdt-bpmn2.dev] Expression and Auditing

["Hille-Doering, Reiner" <reiner.hille-doering@xxxxxxx>]

I need to think about this and also consult Ivana. I don’t want to move away from the original CMOF metamodel if not absolutely needed. But we might need to add e.g. some more metamodel attributes that have special handling in our Resource implementation to be compliant with both, XMI and XML.

 

Von: mdt-bpmn2.dev-bounces@xxxxxxxxxxx [mailto:mdt-bpmn2.dev-bounces@xxxxxxxxxxx] Im Auftrag von Antoine Toulme
Gesendet: Freitag, 16. Juli 2010 00:59
An: Henning Heitkötter
Cc: BPMN2 Developers Mailing List
Betreff: Re: [mdt-bpmn2.dev] _expression_ and Auditing

 

Thanks Henning! Yes, I'm worried we will need to work on that.

 

Reiner, it looks like getDocumentation() could be changed to getDocumentations(), what do you think ? Unless it should not be multivalued ?

 

Thanks,

 

Antoine

On Thu, Jul 15, 2010 at 12:45, Henning Heitkötter <hheitkoetter@xxxxxxxxxxxxxx> wrote:

Hi Antoine,

both are rather "special" (or surprising) cases:
The BPMN specification for Expressions reads as follows: "The natural language text is captured using the documentation attribute, inherited from BaseElement." (see chapter 8.3.6).
In case of Auditing, it is intended to "leverage the BPMN extensibility mechanism" (see chapter 10.9).

We do, however, will need to find a mechanism to handle the cases where something is to be stored as a XML text node according to the XSD and differently with XMI (for example, Documentation.text).

Regards,
Henning

Am 15.07.2010 21:22, schrieb Antoine Toulme:

Do we have a problem with those objects ?

 

I can't seem to be able to set the content of the condition _expression_ of a sequence flow for example, since the _expression_ class doesn't have a way to set its own text node.

 

I may be missing something.

 

Thanks,

 

Antoine

_______________________________________________

mdt-bpmn2.dev mailing list

mdt-bpmn2.dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev