- 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>
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"> >to > <perform choreographyName="qname" >choreographyInstance="XPath-expression"> > >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