[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dist-obj] DOP & web-services & n-tier

Sundar Narasimhan:
>    To restate a point that apparently did not communicate to anyone,
>    I think that many conversational choreographies will be (are being)
>    stereotyped so that distributed objects can converse by using
>    a shared script of some kind.  Most of the current efforts (ebXML BPSS,
>    BPML, WSFL, XLang) use XML.
>
>    Yes, most of the early scripts will be business-oriented, like order-
>    delivery-payment.  But the principle applies to other domains:  don't
worry
>    so much about the particularities of the end points; have them follow a
>    shared scenario.  Think rules of a game.
>
> Hi, Bob: I don't want to push the choreography metaphor too much, but
> is there a notation with which we can write the songs and express what
> needs to be co-ordinated independent of the actual pieces of music
> that are presently coming out for particular standards bodies such as
> ebXML? (I think that would be one fruitful way of answering Adam
> Bosworth's concerns about specifying the order and temporal semantics
> of method calls).

ebXML, UN/CEFACT and RosettaNet (among others) use a stylized version
of UML Activity Graphs.  In the case of ebXML, they are meant to be
transformed into a particular XML notation using production rules as
described in this document:
http://www.ebxml.org/specs/ebBPSS.pdf

BPML goes direct to XML, but is tinkering with the ebXML-style
UML Activity Graphs, too.
http://www.bpmi.org/

For XLang, MSFT has a Visio-based "Orchestrator" product
using their own variation of flow charts.

Don't know much about WSFL.  It's an IBM thing.
http://xml.coverpages.org/wsfl.html

Apparently there will be some W3C activity to try to harmonize all this
stuff.

A personal note about ebXML:  it was a learning experience for me.