Re: [stp-dev] About BPMN metamodel

["Alex Boisvert" <boisvert@xxxxxxxxxxx>]

I'll complement Hugues' answer, by saying type of the task can be inferred from the diagram or from
more specific subclasses.   

Second, I consider TaskType to be restrictive in that it unduly constrains the extensibility of the model by using an attribute to model behavioral character.  This is something that can be better achieved by specialization (inheritance) to avoid overloading the meaning/ semantic of base attributes in the Task class.  At first glance, it might seem like this makes it harder for M2M
transformation, although my guess is that you'll probably need to walk the
graph for any kind of comprehensive transformation process.  
If you'd like to match against specific types, it's possible to
introduce new classes to the model, starting with Task itself (with or without the TaskType attribute).

cheers,
alex

On 7/17/07, Hugues Malphettes <hmalphettes@xxxxxxxxxxx> wrote:

Hi Juan,

The BPMN metamodel is made to support the BPMN notation for a BPMN modeler.
It is does not natively support all the type of extra properties
defined in the BPMN specification.

However the model can be attached any number of properties by using
EMF annotations.

So in the case you mention the approach we recommend is to define an
annotation to set on the org.eclipse.stp.Activity class.

An Activity is a BPMN Task when its ActivityType is Task.

This tutorial describes how to expose such annotation in the properties view:
http://wiki.eclipse.org/index.php/STP_BPMN_Presentation_Hands_on_tutorial#Extending_the_modeler:_defining_a_custom_property

Hugues



On 7/17/07, JUAN JOSE CADAVID GOMEZ < jcadav10@xxxxxxxxxxxx> wrote:
> Hello,
>
> Some time ago I wrote about a college project currently in progress about extending the STP BPMN modeler for M2M transformations. I have checked the bpmn.ecore metamodel against the BPMN specification and noticed that in the specification there are two Activity subtypes declared, Task and Sub-Process. However, I can't seem to find these two subtypes in the STP BPMN schema.
>
> My concern is that in the specification, the Task element has an attribute called TaskType, with possible values (Service | Receive | Send | User | Script | Abstract | Manual | Reference | None) which I need to capture for the transformation rules I'm writing. However, I don't see how to obtain it with the current metamodel, since the Task element doesn't exist. Can somebody help me here?
>
> I appreciate your attention.
>
> -Juan
>
> _______________________________________________
> stp-dev mailing list
> stp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/stp-dev
>
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev