W3C home > Mailing lists > Public > public-ws-chor@w3.org > November 2004

RE: choreographyInstanceId - revised text

From: Martin Chapman <martin.chapman@oracle.com>
Date: Fri, 19 Nov 2004 16:58:59 -0000
To: "'Furniss, Peter'" <Peter.Furniss@choreology.com>, <public-ws-chor@w3.org>
Message-ID: <001b01c4ce59$10a6baf0$955fb98b@ie.oracle.com>

there are a few choreographyInstanceId that need the Id dropping.

>-----Original Message-----
>From: public-ws-chor-request@w3.org 
>[mailto:public-ws-chor-request@w3.org] On Behalf Of Furniss, Peter
>Sent: 18 November 2004 22:10
>To: public-ws-chor@w3.org
>Subject: choreographyInstanceId - revised text
>In 2.5.3, Composing Choreographies
>Change first line of perform syntax from 
>    <perform choreographyName="qname">
>    <perform choreographyName="qname" 
>Insert as second paragraph after the perform syntax
>The choreographyInstance attribute defines an identifier for 
>this performance of the Choreography identified by the 
>choreographyName attribute. If the performed Choreography can 
>only be performed once within the enclosing choreography, the 
>choreographyInstanceId attribute is optional. Otherwise, it is 
>required and the value MUST be different for performance. This 
>is a dynamic requirement - e.g. if a single <perform /> 
>element appears in a workunit that can repeat, each use of 
>perform must assign a different subChoreographyInstance identifier.
>In the schema, add to definition of tPerform, immediately 
>after the attribute defintion for choreographyName: <attribute 
>name="choreographyInstanceId" type="cdl:tXpath-expr" use="optional"/>
>Choreology Anti virus scan completed
Received on Friday, 19 November 2004 16:59:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:06 UTC