RE: [bpel-dev] BPEL and Semantic Web Services

[Bruno Wassermann <B.Wassermann@xxxxxxxxxxxx>]

Hi Ralf, 

My two cents: 

We have discussed such drag-and-drop features a while ago, which would be
really cool ('coz intuitive). 

In any case, for step 1, I would suggest investigating the built-in UDDI
browser and figuring out:
1. how to extend it to deal with semantic annotations
2. how to get drag-n-drop from UDDI browser into BPEL editor (currently,
user can import WSDL from UDDI browser into workspace, which is not too bad
either). 

Step 1 may be quick and painless. Google 'Grimoires'... that's a UDDI
implementation dealing with semantic WSs. The guys behind Grimoires
mentioned a while ago that they might be working on an integration into WTP
UDDI browser, so maybe it's there already somewhere.

HTH, 

-- Bruno

-----Original Message-----
From: bpel-dev-bounces@xxxxxxxxxxx [mailto:bpel-dev-bounces@xxxxxxxxxxx] On
Behalf Of Ralf Weinand
Sent: 06 August 2007 15:04
To: bpel-dev@xxxxxxxxxxx
Subject: [bpel-dev] BPEL and Semantic Web Services

Hello,

I´m writing a thesis about BPEL and Semantic Web Services,
which involves the development of a BPEL editor that can handle
Semantic Web Services
and takes advantage of the semantic annotations of input and output
parameters
to support the user in defining the data flow.

I was thinking of building this on top of the existing BPEL project.
I am quite new to EMF-based projects (I completed the EMF-tutorials though
:-))
and would like to know if you can tell me if it is reasonable to use
the BPEL-project
for my purpose, and where to start.

In the end the user should be able to
1. load Semantic Web Services (OWL-S files)
2. drag&drop service operations of Semantic Web Services into the editor
3. semi-automatically generated data flow constructs for each Semantic
Web Service,
    which involves some reasoning in the background and results in the
generation of a
    sequence of activities:
    1. Assign (which will do a xslt transformation from OWL to XSD)
    2. Invoke (to call the underlying WSDL Web service)
    3. Assign (to convert the result back to OWL)
4. export the process and all generated resources (like XSLT-files)
into an execution system (like ActiveBPEL engine)

Any comments very much appreciated! :-)

Thanks,

Ralf
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev