W3C home > Mailing lists > Public > public-ws-chor@w3.org > April 2003

Feedback on Glossary

From: Cummins, Fred A <fred.cummins@eds.com>
Date: Tue, 22 Apr 2003 20:59:00 -0500
Message-ID: <27C20ED5A6D3D511ADF30002A5D6464802C02CC4@USPLM214>
To: "Monica J. Martin" <monica.martin@sun.com>
Cc: public-ws-chor@w3.org


Feedback on the glossary,

Composition.  [This definition is becomeing much too complicated.  How
composition is addressed in choreography is to be defined by the final
specification.  What we mean 
by composition should be quite simple: creation of a unit or product from
components or parts.  There is an implication that the components or parts
may be used to compose a variety of units or products.  To extend this to
choreography, composition is the creation of a choreography from parts that
may be used to create a variety of choreographies.]

Correlation. [I don't know why we need a special definition for this.]

Global model.  A model which expresses the relationships between otherwise
seemingly independent exchanges.  It puts exchanges in broader, business

Orchestration. [this term may have a distinct meaning at some future point,
but for now it should be explicitly undefined in this discourse].

Process.  A process is a group of interrelated actions or activities that
are specified to achieve a defined objective and are complete when that
objective is achieved or abandoned.

Process instance. The execution of a process to achieve its defined
objective in a particular situation.

Role. An abstract designation for a participant in a choreography that is
bound to a particular participant URI when the choreography is performed.
In some choreographies, the same participant may be bound to multiple roles,
or a role may be bound to different participants at different times during
the execution of a choreography.

State.  An attribute value or set of values of attributes of an entity that
represent a condition of interest for that entity.  Typically, a number of
states of an entity are of interest, each will be named, and the events
which may cause transitions between these states will be defined for state
transitions.  The alternative states of an entity will typically be defined
in a particular context (an entity may have many states of interest in
different contexts), and suggests--by reference to state transitions--how
that entity will behave in the associated context.

Service type.  A service that conforms to a WSDL interface and conforms to a
defined choreography in a specified role.

Fred Cummins

> -----Original Message-----
> From: Monica J. Martin [mailto:monica.martin@sun.com]
> Sent: Tuesday, April 22, 2003 1:05 AM
> To: Steve Ross-Talbot
> Cc: public-ws-chor@w3.org
> Subject: WS[Chor 4/21/2003: Updated Cases Submitted and Choreography
> Terms to Consider
> As indicated, attached is the working glossary with the comments I 
> received from Assaf and Hugo. I also heard from Mike Brumbelow, who 
> wishes to assist on glossary. Mike, please do a pass over this for 
> tomorrow and once the discussion gets going, we'll do so as 
> well. Those 
> items in red in the document are changes made from comments received. 
> Comments / questions are also inserted in these sections, for team 
> discussion at the appropriate time.
> As well, as requested last week, I've added additional detail 
> to my two 
> cases for consideration with some potential areas to mine for 
> requirements. These scenarios were based on real world 
> requirements in 
> European and high technology/electronic component industries.
> Thanks.
> Monica J. Martin
> Sun Microsystems
> Monica J. Martin wrote:
> >
> > I have the glossary with questions for the group to address 
> and will 
> > distribute this afternoon (MT).
> > Thanks.
> > Steve Ross-Talbot wrote:
> >
> >>
> >> Any suggestions?
> >>
> >> I have until 8:00pm my time (UK) to firm this up and get it out.
> >> Cheers
> >>
> >> Steve T
> >>
> >> This email is confidential and may be protected by legal 
> privilege. 
> >> If you are not the intended recipient, please do not copy 
> or disclose 
> >> its content but delete the email and contact the sender 
> immediately. 
> >> Whilst we run antivirus software on all internet emails we are not 
> >> liable for any loss or damage. The recipient is advised to 
> run their 
> >> own antivirus software.
> >>
> >
> >
> >
Received on Tuesday, 22 April 2003 21:59:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:01 UTC