|Re: My vision for the collaboration between JWT and STP [message #26273 is a reply to message #26227]
||Sat, 20 October 2007 20:20
| Florian Lautenbacher
Registered: July 2009
Marc Dutoo wrote in answer to Etienne's post on the mailing list:|
Hi Etienne, All
Thanks for what I believe is a clear, quite accurate depiction of what
we're going to do in the following months.
Etienne, as I understand, your idea of pushing BPDM forward is as a
"deeper" way to integrate with STP and STP-IM. I've taken a better look at
BPDM and besides the fact it is not an approved standard yet it makes
sense. I'd like to share some thoughts about it, more about soon...
More focus on some other points of your mail :
Our goal is to have a first coverage of the two problematics : Process
Design by Business Analysts with BPMN, Process Implementation by
Developers. Integrating STP's BPMN Editor is a way to achieve that and at
the same time build some interesting ties between JWT and STP.
The STP Intermediate Metamodel (STP-IM) is an interesting utility whose
goals are similar to JWT's (though having a stronger orientation on
services rather than processes). Therefore it would be a hitback to both
STP-IM and JWT's metamodel if they were not integrated. It has appeared
quite recently, so nothing is planned yet, but I'd like to look to push
this forward somehow, talk with STP's Adrian Moss etc.
About the STP Intermediate Metamodel (STP-IM) :
This model is a tool for bridging between the various STP editors and
their models using transformations, and is able to hold information about
concepts like Services, Routing, Processes (simple processes consisting of
Step and Transition).
It has been initiated and pushed forth in STP by Adrian Moss of INRIA, who
found the need of such an intermediate (or "hybrid") metamodel while
working on correspondancies between SCA and JBI in the context of the
SCOrWare project. This idea gathered a big following among the pther STP
members. Things then went fast and a first version of STP-IM is now
In order to be put to good use, it has to be extended in order to add the
right tool / standard / runtime information (e.g. property, metadata,
annotation etc.). The catch is (it is my understanding )that this extended
information must stay consistent between all tools that integrates it in
order to make it useful, and that is not trivial.
Powered by FUDForum
. Page generated in 0.04915 seconds